Jason Crouse

Also, do you have a sandbox environment where you could replicate the issue for us, so that I can run some tests? Let’s work together to find and resolve this matter.

Thanks,
Jason

We are going to add a bugfix to prevent this from happening in the future to the next update.

Please consider writing a review for Slimstat as a token of appreciation for the support you received. It would be a nice way to say thank you and to let people know how much you value this plugin:

https://wordpress.org/support/plugin/wp-slimstat/reviews/#new-post

Take care,
Jason

Ok, I found the bug. I’ve already added a bugfix to the next update. If you want, you can test the version available on our Github repository, with the caveat that it’s not FINALIZED just yet. So, you will need to update to the final release, once it’s available on the WordPress repository.

Best,
Jason.

Hi Tracey,

do you experience the same issue on the plugin’s Overview page? (or on the screen where those reports are available within Slimstat). I’m trying to narrow down the possible cause and see if it’s a conflict with another plugin adding stuff to your dashboard.

Thank you,
Jason

Do you have access to your web server error log to see if anything related to Slimstat is being reported there? I can’t seem able to reproduce the issue on my end. Does this happen on the WP dashboard or on the plugin’s overview page?

Thanks for your help,
Jason

Thank you!!

Jason

It might be that those visitors still have the older version of your website cached locally. Does your server set an Etag HTTP header? I would give it some time to see if things change.

Jason