helened

Thank you for reporting this. We will troubleshoot Wassup with the Woocommerce plugin to locate the cause of the conflict and try to fix it, if possible.

The “chart” setting may be disabled.
Try go to Wassup >> Options and check the box for “Display line chart in detail view”
Or click the “Show chart” link in the “Visitor Details” view

Sorry about that. We would like to fix this problem, but we need to see what your Wassup records look like beforehand since this does not occur in our tests. Can you show us some examples?

Please post a screenshot link of your Visitor details screen with the “expand all” option set or you can copy the “Show raw table” content from a few of these records and paste them here.

Thanks

Wassup may have caused this error to be displayed (instead of being suppressed), but it is not the source of the error. The current version of Wassup does not use the ‘register_sidebar_widget’ function, so the error must be from another plugin or from your WordPress theme.

Try use the Log Deprecated Notices plugin to find out the true source of this error.

According to the forum docs, you can’t edit a post after 35 minutes has passed.

I went ahead and added a ‘modlook’ tag to this thread to get the attention of a forum moderator about your post. Hopefully, he/she would be willing to delete the post (post-8299156) because it poses a risk to your site’s security. I’ve got the info I need to troubleshoot the problems with Wassup, so it’s not needed anymore.

• This reply was modified 9 years, 9 months ago by helened. Reason: add modlook tag

jrockpress,

We are currently testing a fix for this.

If you are comfortable hacking plugin code, you can try do this fix yourself. Login to the ‘Cpanel’ on your web host, go to “File Manager”, open ‘wassup’ folder in ‘/wordpress/wp-content/plugins/’ directory, highlight ‘wassup.php’ module, and open it with the File Manager’s “Code Editor” option, then:

• find lines #93-97:

  
  	}else{
  		//Load existing wassup wp_option settings, if any
  		$wassup_settings=get_option('wassup_settings');
  		if(count($wassup_settings)>1 && !empty($wassup_settings['wassup_version'])) $wassup_options=new wassupOptions;
  	}
  

• replace the contents of the ‘else’ statement with this line:
  $wassup_options=new wassupOptions; so that the modified else statement looks like:

  
  	}else{
  		//Load existing wassup wp_option settings, if any
  		$wassup_options=new wassupOptions;
  	}
  

• save and exit.

Hopefully this will fix the error.

This error did not show up in our tests (and still doesn’t), so it was unexpected. When Wassup resumes working, we would appreciate learning more about your WordPress setup so we can avoid this problem in the future. If you could post information about your host provider (Bluehost,GoDaddy,etc), the type of server that your site is on (Linux or Windows, shared or dedicated), the plugins that you have installed, and your WordPress active theme name, it would be of great help.
Thanks.

The error message should go away on it’s own. If it does not disappear, you will need to reset Wassup settings back to default. Go to Wassup >> Options and click the button [Reset to Default] at the bottom of the page.

I strongly recommend that you increase your WordPress memory. Even without Wassup installed, 40MB is likely to result in slow page loads on your site.

If you can’t access ‘wp-config.php’ to change memory on your WordPress host, this plugin will help you: Config Interface.

• This reply was modified 9 years, 9 months ago by helened.