BethM
Member
Attempting to upgrade from 1.3.1 to 1.6 and am using WP 2.3.3.
Deactivated the plugin, deleted the directory from the server. Uploaded the new files and when I clicked on "activate" I received the following..
"Plugin could not be activated because it triggered a fatal error."
Saw a post about this from 4 months back but it refers to older versions.
Wassup had some major code and structural changes since 1.3.1. Perhaps you need to do a step upgrade instead of a single jump from 1.3.1 to 1.6. Try upgrading to 1.4.8 first. Then, if that works successfully, upgrade to 1.6. Good luck.
BethM
Member
Thanks for the suggestion. I downloaded and installed 1.4.8 and ended up with the same error but I noticed that there was a Wassup tab available and the Wassup item in the Plugins section said "activated". I could move around in the tab and see information, but noticed no new information was recording. I think looked at my front page (which showed as a Http 500 Internal Server Error). I deactivated 1.4.8 and tried reloading things again.. made sure that .js, .css, etc were transfered as ASCII (thinking that might have been a problem), but got the same error.
One possible hint with this..
when I have it activated (although it told me it couldn't) in the options section all that I see under "Manage Files & Databases" is
------
Temporary files location folder
"Save path" directory for storing temporary files used to track visitor activity:
-------
There is nothing below that at all.
Also if I click on Uninstall, I get no change to the page at all.
When I deactivate.. the 500 error goes away.
I delete the 1.4.8 files and reinstalled 1.3.1 and it works again.
My server admin has things on my box pretty tight. I'm wondering if there's something that isn't getting set up automatically (a database perhaps) and I need to have him set up a database or 'loosen' the settings for me a bit.
Sorry a step upgrade to 1.4.8 didn't help. The reason the upgrade to 1.4.8 failed (safe mode?) is likely different from why 1.6 failed (wrong database structure?). When you activated 1.4.8 it may have successfully updated Wassup's database, in spite of the errors. This may be all that is needed to make 1.6 work. "Safe mode" should not affect 1.6 and hopefully you have full ownership permission (read/write/create/alter) on your Wordpress MySQL database so that Wassup can create and update tables. If you have the time, why don't you try upgrading to 1.6 again to see if the step upgrade made any difference? Good luck.
BethM
Member
Well, I reloaded 1.4.8, activated, same fatal error message, this time it took a bit before the blog page disappeared. Then I deactivated, deleted the files and loaded 1.6. The blog page is still there, but Wassup isn't showing new visits. The Visitors detail section shows the graph (from historical data), but no details below (it shows numbers for pages of data I think, but no data). It does load the Top Ten information.
Again, one thing I've noticed is in the Options.. the "manage files & database" section doesn't load correctly. All I see is "Temporary files location folder
Current "Save path" directory for storing temporary files used to track visitor activity:" And nothing below that.
Sorry to be such a pest, I'd just love to be able to update to a newer version than 1.3.1.
BethM
Member
A bit more info
getting this error..
[18-Jun-2008 16:48:51] PHP Fatal error: Call to undefined function
session_save_path() in
/www/xxx.xxx.com/webpage/wp-content/plugins/wassup/wassup.php on
line 1843
which does have to do with the save path
$sessionpath = session_save_path();
Thanks for providing the error details. It looks like PHP on your web server was compiled without "sessions" or you don't have permission to access to "session" functions, thus the "save path" error. Wassup 1.6 should work without it even with the error.
Try to manually enable statistics recording in Wassup 1.6. Go to Wassup==>Options==>[Statistics Recording] and check "Enable/disable recording" to start recording new visits. Everything should work except the [Manage Files & Database] option tab. That will likely be fixed in Wassup's next update. Good Luck.
BethM
Member
Thought I'd let you know 1.6 is working now.
Removed everything, parsed the database, reloaded and then commented out the tag to do with
#if ($withcharset && $wpdb->supports_collation() ) {
and all is well in the Wassup world..
Until I try to install the next update :)
You must log in to post.
