helened

Glad to be of help.
Please close this topic if you have no more questions related to this issue.

Thanks for using WassUp!

Your host server may be blocking the top ten URL from running. Try entering the top ten URL with NO parameters (http://www ........../wp-content/plugins/wassup/lib/action.php) in a new window/tab.

If the script runs, you should see an error message in the browser window. Then try the URL with the 1st parameter (http://www ........../wp-content/plugins/wassup/lib/action.php?action=topten), then with the 1st and 2nd parameters, and so on, until you find the parameter that triggers a blank page and 500 error in your console.

Hmm…the last query parameter “&random=1396283538653” shouldn’t be there. Another application or plugin must have added that to the URL.

Try click “Show Top Stats” again, then copy the top ten URL from your browser console directly into your browser location field with/without the “random” parameter and let us know what happens. Thanks.

Helene.

There is no way to disable WassUp cookie right now. You can try hacking the plugin code, but I don’t recommend it because the cookie is an integral part of WassUp and any change will likely cause problems.

It looks like there is a problem in your WordPress setup where a visitor’s browser is automatically redirected to the url with the slash appended. Wassup tracks both urls because the browser visits both.

Try fixing your permalink structure (WordPress>>Settings>>Permalinks) to include the trailing slash; or deactivate any plugin that is enforcing the trailing slash in the URL (Ex: WordPress SEO plugin?); or edit your .htaccess server configuration file; or do a combination.

Please check if you have a plugin that does “compatibility checks” installed on your site. If you do, deactivate that plugin and the errors should stop.

Or, you may have “WP_DEBUG” set in your WordPress configuration file, “wp_config.php”. That line should be “commented out”, if it is there.

Wassup is compatible with the latest version of WordPress. But it is not compatible with “compatility checking” functions and plugins because it has backward-compatible code built into it.

Thank you for using Wassup. Unfortunately, at this time, WassUp doesn’t support offsite hosting of wassup data. We are exploring this option in the next generation of Wassup, but that is a long way off.

Currently the only way to get Wassup data into a second install of WP on another server is to manually export and import the data. You can use a tool like “phpMyAdmin” or any WordPress backup utility that lets you export (and import) in SQL format. This import/export method isn’t hard, but can be time-consuming because you may have to break up the export data into smaller subsets, if your wassup data is very large. Once done, though, you can look at historic wassup data on the second server without worrying about it impacting your website performance and you can speed up the original Wassup by deleting the old data that was exported.

There are some extra steps to be aware of with this kind of duplicate Wassup setup on a second WordPress server:

• Wassup “recording” must be disabled on the duplicate;
• The table to export from and import to is “wp_wassup” (or customprefix_wassup).
  NO need to export from or import to “wp_wassup_tmp” or “wp_wassup_meta”.
• The duplicate wassup table (wp_wassup) must be empty prior to the first import of wassup data;
• You should write down the record ID of the last exported wassup record to avoid “duplicate record” errors in the next import;
• To view “Wassup Top Stats” on the second server, you need to add your website hostname to the list of excluded referrers;
• To view “Top stats: Top article”, you need to import “wp_posts” and “wp_post_meta” data from your website into the second WordPress;
• To view WassUp chart, SPY map, and all Wassup-Options items, the second server must be connected to the internet to access Google APIs.