Sep 19th, 2011, 10:49 PM
So... I'm still not sure about the cause.
Did you notice any problems with initially installing the module, or did you encounter the error after selecting it?
My working theory is that the problems with the website today (which is still broken for me now), prevented the database tables being created properly during installation. It's just a hunch, but I think it may be right.
I know of three places that the modules been installed, all of which work properly - and I haven't heard of any problems reported from anyone else.
The handle_error() error message you noticed *is* a problem - just not the root cause. It should be calling ft_handle_error(), which would output a more elegant error. But I don't want to release a separate release just for that minor fix until I can figure out the root cause.
I've contacted my host to get them to re-resolve the sessions issue. Once that's fixed, I'll re-test things locally and see if I can get to the bottom of it.
Sorry about this, Ted! Speak tomorrow -
Ben
Did you notice any problems with initially installing the module, or did you encounter the error after selecting it?
My working theory is that the problems with the website today (which is still broken for me now), prevented the database tables being created properly during installation. It's just a hunch, but I think it may be right.
I know of three places that the modules been installed, all of which work properly - and I haven't heard of any problems reported from anyone else.
The handle_error() error message you noticed *is* a problem - just not the root cause. It should be calling ft_handle_error(), which would output a more elegant error. But I don't want to release a separate release just for that minor fix until I can figure out the root cause.
I've contacted my host to get them to re-resolve the sessions issue. Once that's fixed, I'll re-test things locally and see if I can get to the bottom of it.
Sorry about this, Ted! Speak tomorrow -
Ben