helened

Delete failure could be caused by a number of things, including a table lock (in use), or user permission was insufficient, or a javascript (ajax) error. Try reloading WassUp’s visitor detail screen and click “delete” again. If that doesn’t work, try logging out of WordPress, then log back in (as an administrator), and delete again. If neither of these work and you get an error message in Wassup, please paste it here.

ps: your doggie is adorable!

Sorry the previous fix didn’t work.

There is another fix that you can try that completely bypasses the upgrade script to update WassUp’s tables. Since WordPress 3.0, the ‘dbDelta’ function sometimes chokes on WassUp’s large table structure and that can also cause activation failure due to a MySql ‘ALTER table’ error. You’ve already upgraded WassUp’s table, so there is no need to do it again.

To bypass, go to WordPress plugin editor, select “wassup.php” and comment out line #116: $success = wassup_tableInstaller(); inside the “wassup_install()” function, i.e, prepend the characters, // to the beginning of the line.

Good luck.

This is a known issue in WassUp 1.8.1 that affects some users whose PHP configuration allows warning messages to display to screen.
There is a simple fix: disable referrer spam checking in Wassup settings:
Go to WassUp >> Options >> [Statistics Recording] tab, then uncheck “Record referrer spam attempts”, and click [Save Settings].

Similar thing happened to me with Firefox 4 and all plugins deactivated.

Zip download file on www.ads-software.com is corrupt. Hangs automatic install and cannot unzip with manual download. Use the tar.gz download instead.

It appears that the ‘wassup_meta’ table does not exist in your copy of WassUp, yet WassUp is attempting to write data to it.
To fix, go to WassUp ==> Options ==> [Manage Files & Database] Tab and disable the “Cache Storage Option”, i.e. UNcheck “Enable cache for storing some remote API services”, then [Save Settings]

If you go to Wassup ==> Options ==> [Manage Files & Database] tab, you will see that there are already several ways to control WassUp’s table growth, including an automatic delete option and an option to be notified by email when the table reaches a certain size limit.

There is a subtle typo in Wassup 1.8.1 install script that could have triggered this error. To fix, go to WordPress plugins menu, click on Editor submenu, select plugin to edit:“WassUp” in the drop-down box at right, find line #145: “remove_option(‘wassup_settings’);” in the “wassup_install()” function, it is below the final “else” statement in the function, just below the comment ‘//main table not created – exit with error’. Replace “remove_option” with “delete_option”, and click [Update File] to save. Then try activating WassUp in Plugins. Good luck!

This error is caused by a name conflict between a local WassUp array variable and a global NextGen object variable. A fix will be included in the next update of WassUp.

See my response here: https://www.ads-software.com/support/topic/username-or-userid-tracking?replies=2#post-1876814

The WishList Members plugin apparently does not plug into WordPress’ ‘get_currentuserinfo’ command to populate WordPress’ global ‘$current_user’ variable with user data. Wassup cannot track users by username without this. Since this plugin is proprietary, we cannot adapt Wassup’s code for compatibility. The plugin authors have to fix their own code to better meet WordPress standards. You need to notify them about this, yourself.

Go to Wassup >> Options, under [General] tab there is an option: Set Minimum User Level... Select “Editor” from the drop down list and click [Save Settings]

@shakhawat: Sorry. It turns out I missed a couple regex bugs in the 'wGetSpamRef' function. Another bugfix update is coming very soon.

Until then, an easy fix is to uncheck ‘Record referrer spam attempts’ in WassUp >> Options >> [Statistics Recording] tab, as this problem is isolated to the referrer spam function.

Not caused by WassUp! Wassup uses its own internal tables. It does not change any WordPress database table except for ‘wp_options” and then, only to store initial WassUp settings or edit settings when WassUp-Options are changed manually. WassUp does not affect posts at all.

Please update all your cached pages as your site probably still has the old copy of WassUp in memory.

The WassUp download file was fixed yesterday. Your browser or proxy server must have cached the bad link. Try refresh your browser cache and reload the plugins page, then try to upgrade WassUp again.

FYI. There is a precautionary notice about upgrading in the newest installation instructions. Please read it before upgrading.