Hi,
can you check if the tracker is reporting any errors under Slimstat > Settings > Maintenance?
Thank you,
Jason
Hi Jason,
Tracker Error reports: So far so good.
Tracker Notice reports: So far so good.
Cheers,
Rene
Would you be able to post the URL of the website where you installed Slimstat?
I see you are using Autoptimize. That plugin is known to cause issues when used in conjunction with Slimstat. In this case, for example, it is removing some inline code that the tracker needs to uniquely identify your page views. Please ask its developer to help you exclude Slimstat from the minimized portion of the page.
Thanks, I will first disable Autoptimize and see what happens.
In this case, for example, it is removing some inline code that the tracker needs to uniquely identify your page views. Please ask its developer to help you exclude Slimstat from the minimized portion of the page.
by default inline JS is not optimized in AO (unless you installed long time ago), disable the option to “also aggregate inline JS” and you should be good to go 🙂
frank (ao dev)
@futtta, thank you for chiming in. Your help is much appreciated 🙂
Hi guys, I completely disabled Autoptimize, but it still doesn’t work.
Hm, I just visited your website and my page view was correctly recorded by the tracker (no error codes returned). Can you try again? Are you excluding yourself? Browser cache?
I deleted the cache and now I see some data appearing.
Thanks a lot!
Great! A review for Slimstat would be a nice way to say thank you:
https://ww.wp.xz.cn/support/plugin/wp-slimstat/reviews/#new-post
Best,
Jason
Too bad, I was excited too fast. After a few records, the logging stopped again. 🙁
I just setup a new WordPress (4.7.1.) installation without any plugins (this sandbox), except Slimstat. In the maintenance section, there was an error about caching but slimstat is also not working there either.
@renarios, your test server is sending the following HTTP headers back to the browser:
X-Frame-Options:SAMEORIGIN
X-XSS-Protection:1; mode=block
Those headings are preventing the browser from loading the tracking Javascript file from the CDN. You can easily fix this by deactivating the CDN option in your settings, and thus serving the tracking script from your local server (which will increase the amount of traffic generated, though).
You can learn more about what your server is doing on this page:
https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/X-XSS-Protection
Best,
Jason
-
This reply was modified 9 years, 4 months ago by
Jason Crouse.
-
This reply was modified 9 years, 4 months ago by Jason Crouse.
As for the main site, it is not tracking because you haven’t configured Autoptimize the way Frank described here above 🙂 I hope this makes sense.
Jason
