Jason Crouse

Thank you for clarifying. Yes, now that makes sense. Slimstat now relies on a Javascript mechanism to submit its filters to the engine. This is only triggered when users click on the link directly, not right-click or open it in a new window. We are looking at a way of reintroducing partial support for right-clicked links. Stay tuned.

Jason.

Again, we could not reproduce this issue on our end. Would you care to share the steps one would follow to cause this problem?

Thank you,
Jason

Hi @fadzak,

Slimstat will allow you to track any query string parameters through the Access Log report.

Best,
Jason

Hi @salsabunny,

thank you for pointing this out. We are working on a feature that will display a message overlay (as a text box at the bottom of the viewport) with two buttons: one to accept and one to opt out. Given that different sites will want to engage their audiences in various ways, the message itself will be customizable, and might include links to custom terms and conditions, more information about GDPR and so on. You will also be able to customize the look and feel by adding a few lines of CSS to your theme.

Based on our current understanding of this new law, please note that as long as the hosting provider where you are storing the information collected by Slimstat is GDPR compliant, then you won’t have to worry about any extra layers of compliance offered by software like ours. The main goal of this new set of rules is to make sure data is stored in a safe and secure way. One of our primary goals is to make sure no vulnerabilities are present within our code, and guarantee that you and only you are the sole owner of the data collected by our plugin. This has always been what makes Slimstat stand out from the crowd: while Jetpack, Google Analytics and many other services have full unrestricted access to the data they collect on your website, we at Slimstat don’t treat our users as the “product” we sell to other companies.

Also, Slimstat already includes a feature to anonymize all the IP addresses that it collects and stores in the database, by hiding its last octet. By enabling this option in the settings, you should be in further compliance with the law.

Now, do YOU think this will be enough to comply with the upcoming GDPR guidelines?

Best,
Jason

• This reply was modified 8 years, 1 month ago by Jason Crouse.

Yes,

you can exclude by specific username or by capability, under Slimstat > Settings > Filters.

Let me know if that answers your question.

Jason

Marc,

apologies, I just pushed it to the repo. Could you please try again?

Thank you,
Jason

Hi,

the interval_minutes filter has been temporarily removed from the code. It will be reintroduced in the next update. Thank you for your patience.

Best,
Jason

The next update will fix this issue. I’m going to push it to our Github repository later today, if you want to test it in advance:

http://github.com/slimstat/wp-slimstat

Best,
Jason