Jason Crouse

Terrific, thank you so much for testing the new version! I’m working on a few other things, and hopefully I’ll be able to release it in a couple of weeks.

Best,
Jason

@davor_wp my apologies, I forgot to mention that you will need to deactivate the CDN option under Slimstat > Settings > Tracker. Otherwise it will load the tracker from the cloud, instead of locally. And of course we haven’t released the new tracker to the public just yet 🙂

Thank you for your patience,
Jason

Please keep in mind that this might not be the FINAL release, so don’t forget to update again when the official version is released on the WordPress repo!

Best,
Jason

I found a possible glitch related to how Google Bot is presenting itself as a “mobile” device. A fix has been added to the next update, which should be released in a couple of weeks. It’s already available on Github, if you want to test it in advance:

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

Best,
Jason

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

Jason

I see. Hey, thanks for the loyalty!

Now that you mentioned the Preload Cache feature, I tried deleting the cache and enabling the Preload again, and this time the tracker was removed from all the pages. So that seems to be the culprit. If I disable the preload, the page is still cached (I see the WPFF signature at the end) but the Slimstat tracker is there too, as it should be. If I enable it again (AND DELETE THE CACHE), then the tracker disappears, even with the exclusion rule in place (JS contains wp-slimstat). So it looks like a bug on their end, when they preload the site, they might not be calling the wp_footer action that Slimstat uses to append the tracker to the source code.

Please confirm that that’s the case for you as well. I’ll consider this ticket resolved.

Best,
Jason.

• This reply was modified 7 years ago by Jason Crouse.

All the pages in my dev setup have the WPFF signature, which looks like:

<!– WP Fastest Cache file was created in 0.27939105033875 seconds, on 24-04-19 16:15:22 –>

So they are being cached, unless I’m missing something? I also checked the filesystem, and I do indeed see a bunch of HTML files and folders under

/wp-content/cache/all/

Anyway, I enabled the “preload” feature in the free version, and Slimstat is still working. If you’re using the premium/paid version, would you mind giving me access to a temporary clone of your website to try and troubleshoot the issue directly where it happens, since I can’t reproduce it on my end?

Best,
Jason

Hi @denizci88

you can do that by setting the start date (05.04.2015) and then the number of days in your timeframe, which you can calculate using one the many websites available out there:

https://www.timeanddate.com/date/duration.html

Best,
Jason