helened

Try reset-to-default in Wassup >>Options.

If that doesn’t restart data collection, try “uninstall” (go to Wassup >>Options >>uninstall and check the uninstall box then deactivate wassup), and reinstall wassup. Note that this option will purge all wassup data.

If both above doesn’t work, then Wassup may have been blocked by your ISP. Free hosts will often do this when an application exceeds their tiny Mysql quota. Other ISPs may also do this when the site is on a shared host. If your host is blocking Wassup from working, then you have to contact them directly to unblock it.

Note that Wassup accumulates a lot of data and it’s table size can get very large. You should monitor the table when using Wassup on a shared host. You can do this in Wassup >>Options >>[Manage File & Database] tab.

Either the Top stats script or Thickbox could be the problem here.
To check if top stats script is the problem, try running top stats with a single stat, then with 2 stats, then 3, and so on…until you find the stats that is failing. If you find a stat that won’t output data, then there is corrupt data in one of the records, perhaps caused by a hack attempt.

If you have CPANEL access, also try check your host error log for wassup errors. Just open the error log cpanel item in your browser and do a find for the word “wassup” or “top stats”.

Try click [Reset-to-Default] button in Wassup >>Options.
If that doesn’t fix it, please report back your “storage engine” and “delayed queue size” settings from Wassup >>Options >>Manage File & Database tab

The API service is working, so the API server is rejecting the request from your host server only. This could mean that the request limit has been exceeded for your host server, or a spammer may have used your same shared host in the past, or some internal configuration issue is causing WordPress’ wp_remote_get command to fail inside Wassup.

I don’t know how to fix the latter without full access to your server. Instead, you could try this temporary fix to remove wp_remote_get from Wassup’s code:

Use WordPress’ plugin editor to comment-out the following if-end-if block of code inside the plugin function wFetchAPIData() on lines 2068-2078 of the file, wassup/lib/main.php:

//try WordPress WP 2.7+ function 'wp_remote_get' for api results
	if (function_exists('wp_remote_get')) {
		$opts = array('user-agent'=>"$wassup_agent");
		$api_remote=wp_remote_get($api_url,$opts);
		if (!empty($api_remote['body'])) {
			$apidata = $api_remote['body'];
		} elseif (!empty($api_remote['response'])) {
			$apidata = "no data";
		}
		$api_method='wp_remote_get';	//debug
	}

These lines are located near the very bottom of wassup/lib/main.php. To comment them out, just insert a new line with  /*  before the first line of code block, then append a new line with  */  after the last line of code block, and update.

Duplicate posting.
See: post-5622354

Yep. Reinstalling Wassup and then deactivating the plugin (with “uninstall” checked in Wassup-options) will delete the wp_wassup table. After deactivation, you should also delete the plugin files by clicking “delete” link under the plugin name in WordPress’ Plugins menu.

You should know that when you re-install WassUp, if your ‘wp_wassup’ table is excessively large, the reinstall could be very slow and your browser may timeout prematurely (blank screen). If this happens, reload the Plugins page after a few minutes, until you see that WassUp is activated.

If you got a blank page with the word “Done” (or similar) after activation, then your browser timed out waiting for Wassup to finish upgrading its tables. This can happen if your database is very large and your server is very slow or very busy. Don’t worry. Your site is still running and your admin area is still accessible.

Try enter your “admin” url directly in your browser location bar: ex:
www.mywebsite.com/wp-admin/plugins.php.
and you will see the list of plugins with Wassup activated. Since a few days has passed since you posted this, you may also be prompted for login.

If you can’t access your admin area even with the direct URL. Then you have to remove “wassup” folder from wordpress’ plugins folder. You can do this by logging into your host server account and use the “File Manager” in your host C-panel.

Good luck.

UR awesome!
I’m close to pinpointing the problem, but there yet. One possibility is that your host server treats ‘whash’ is a special request that interferes with the URL.

Try test this by adding the top ten ‘whash’ parameter to a couple URLs that you know works on your site. Ex:
in WordPress: www. ...../wp-admin/plugins.php?whash=....
with an image: www. ...../photos/mypicture.png?whash=....

Also, try a couple more tests like above, but with a different value for ‘whash’ (like whash=123456abcdef), in case the value of ‘whash’ is the problem, not ‘whash’ parameter name.