pawdl

I tried the steps above with the latest WooCommerce Services plugin, but no good. I don’t know how you can mark this as resolved. I will go back to 1.21.1.

If you are running a version after v.1.21.1, you may want to consider (re)installing v.1.21.1. I had the same issue, or similar, and this took care of it for me.

I mentioned this earlier at the bottom of another thread, but has not received a reply.

HTH

I just ran into this problem. I cleared my browsers cache and am not using caching plugins. Did not help. I even tried two other browsers that I have never used before without relief. Downgrading took care of this problem for now.

Probably the reason your views were tracked is because I went back to 4.7.9.1. I may have to check for an ad blocker, but if it is, how many true visitors will be using an ad blocker?

I have no caching plugins.

I will try to reinstall 4.8 later today.

I’m probably doing something wrong. I uploaded the resulting files to /wp-content/plugins/wp-slimstat/. Verified the version on the plugin page is 4.8. Now, nothing logged since. I have tried:

Client Mode enabled / CDN Enabled
Client Mode enabled / CDN Disabled
Server Mode enabled / CDN Enabled
Server Mode enabled / CDN Disabled

Nothing logged yet after uploading 4.8 files.

How do I get 4.8? When I go to https://support.wp-slimstat.com/, I get a 403 Forbidden.

I am running v.4.7.9.1 and have tried running in client mode with CDN on and off. No stats.

I haven’t had time to check any further. The stats seems to work only when Tracking Mode is is set to Server. I am not using a caching plugin, so it seems this option should be set to Server, but it was set to Client and stats seemed to have worked then. Which way should it be?

I can also confirm switching Tracking Mode from Client to Server and stats seem to work again with the BOT/Crawler notation.

Looking at the hosting servers log files which go back to March, there are many 400 errors on admin-ajax.php. That part is nothing new, so I would have to say that’s not directly the issue. It appears that Google indicates many people talking about 400 errors on admin-ajax.php

Also – I have not changed any settings in Slimstat since it has not been working. Slimstat Tracking Mode is set to client and Track Client Info is on. I do have it configured to not track admin pages, though, but that has been set that way since I started using Slimstat in January.

Thanks for your time!

Thanks for looking into this. I’m not sure how you checked this, but if I go directly to https://pawdell.com/wp-admin/admin-ajax.php, I don’t believe I am getting blocked. It does only return a 0 (zero) and that file is marked readable by the world.

I am trying to better understand my problem before contacting my host provider.

Thanks…

Hi Jason,

Website is https://PawDell.com. Yes, will test.

Thanks…
Paul

Thanks @tiagonoronha for the info on how to fix it. All good here.

Thank you – I had to add (re-add?) menu contents.

• This reply was modified 5 years, 8 months ago by pawdl.

Thanks for the reply and information.

And I may need to do this even though the links were visible and working in Storefront the day before yesterday? I didn’t look yesterday.