helened

This isn’t a WassUp issue. It is caused by the security policy set by the W3C.

FYI. There is a workaround that a ‘https’ site admin can use to pass referrer information (sometimes) from their site to a direct external link with a ‘http’ domain on their site (like in a blogroll) via a header ‘<meta>’ tag: here

Thanks for reporting this.

I will look for a fix.

Hi ABrown95,

Thanks for reporting this problem!

Fortunately, the fix is an easy one that you can do yourself if you are comfortable working with code: in WordPress plugin editor, edit the file “lib/settings.php” and replace the ‘esc_url’ with ‘esc_attr’ and that’s it.

You can view this fix on Github here

I’m afraid WassUp is designed to do the opposite..that is, track everything except for some pages(urls) listed in Options->Filters & Exclusions >> Exclude by URL request.

That said, theoretically you could do it with a hack of your WordPress theme footer.php file. If you are familiar with coding, here’s how:

• disable statistics recording in Wassup >>Options >>General Setup tab and save
• edit your themes footer.php file and add this code near the bottom:

  <?php
  	  if( function_exists('wassupAppend') ){ //Wassup is installed
  	  	global $wassup_options;
  	  	$current_page_id = get_queried_object_id();
  		if( in_array($current_page_id, array(101,102,103,104)) ){
  	  		$wassup_options->wassup_active=1; //enable tracking
  			wassupAppend();
  	  		$wassup_options->wassup_active=0; //disable tracking
  		}
  	  }
  ?>

  Replace the array numbers shown with the post_ids of the pages/posts you want Wassup to track. You can add more post-ids, but make sure that there is a comma between each number.

Be warned, though, this hack might not work and editing code risks breaking your site.

That’s good!

If you are comfortable with coding, you can start using your own API in WassUp by doing the following:

1. Login to your host server, go to the CPANEL database section, and start phpMyAdmin or another MySQL tool
2. select your site’s WordPress database if you have multiple databases
3. click on SQL tab and enter the following statement in the input area:
   UPDATE wp_wassup_meta SET meta_value='your_ipstack_key' WHERE meta_key='_geoip_apikey';
4. click “Go” and that’s it.

Nope, its not you.

As of Friday 2020-02-28, Wassup has exceeded the maximum quota of geoip requests allowed by IpStack free API. You should start seeing pins again in March. I am working on a solution where you can sign up for your own API key instead of using Wassup’s shared key. This will be in the next revision of WassUp.

Thanks for using WassUp!

Thanks for reporting this!
The hyphen(-) in the temporary table name is triggering a syntax error in your MariaDb setup. I will fix this in the next revision of WassUp.

If you are familiar with PHP and want to fix it yourself, you can revise the plugin file “lib/main.php” in WordPress plugin editor and change this line near the bottom of the file (line#1648):

		//use a temporary table for large datasets 
		$tmptable='_wassup_'.$current_user->user_login.rand();

to:

		//use a temporary table for large datasets 
		$tmptable='_wassup_'.rand();

Thanks for testing and for your feedback!

v1.9.4.5 is almost ready. We will officially release it when we fix an issue of false positive spam with cyrillic-language urls.

If anyone else wants to test v1.9.4.5-RC, it is available on Github at https://github.com/michelem09/wassup/

• This reply was modified 5 years, 1 month ago by helened. Reason: added link to v1.9.4.5

Thanks for sharing your solution to this issue.

Thanks for reporting this.
Please tell us about your server software (Win/Linux version, MySQL/MariaDB version, PHP version, etc) so we can try duplicate this and find a fix.

Thank you for reporting this. We will investigate this error and try to get a fix out soon.

The fix is to turn off Wassup’s automatic table optimization in Wassup-Options:

• – Login as WordPress Admin
• – Go to “Manage Files and Data” tab under Wassup menu >> Options tab
• – Scroll down until you see the “Table Optimization” section
• – Uncheck the “Enable automatic table optimization” checkbox
• – Scroll down a little more and click the “save settings” button.

And you are done!

Thank you for your helpful suggestions.

We have removed Thickbox from latest revision of Wassup available on GitHub (still in beta). If you would like to try this version, it is available here:
github.com/michelem09/wassup

• This reply was modified 7 years ago by helened. Reason: fixed typo
• This reply was modified 7 years ago by helened. Reason: fixed link

I cannot duplicate this problem on my test site. Are u still seeing this error in the latest version of Wassup?

• This reply was modified 7 years ago by helened.
• This reply was modified 7 years ago by helened.

Thanks for responding so quickly.
Unfortunately, the information in the screenshots is incomplete. Don’t hide the ip/hostname fields, unless it’s from your own host server. And in the referer field, only hide your site’s domain. Show the rest of the url, even if it’s just ‘/’. I need this info to understand these records and verify that they aren’t spam/hack attempts.

If don’t want the public seeing your referering urls or visitors, you can email me the screenshots/links directly at wassup (at) helenesit (dot) com. Thx.