thescarletfire

Same here. New users. No account linked or anything.
Just every post and page edit in the admin shows this annoying popup.
Please fix this bug!

I also have this problem with Google’s Page Speed Insight. Mine dropped to 66 I noticed, yikes not sure how long that’s been going on. But it’s a Slimstat thing for sure. CDN option doesn’t help.

Any chance this will get resolved or is it part of the plugin’s core?
Thanks!

FYI, before certain folks come here and simply paste a helpful URL to the “fix”, please note:

I’ve already signed up for Maxmind, changed my password, downloaded the archive file, renamed the database from Geolite2-City.mmdb to maxmind.mmdb and uploaded it to wp-content/uploads/wp-slimstat as stated in the official Slimstat help pages.

It doesn’t work. ??

I can confirm, sadly that this is true. All location info is basically null now. Every location comes up as “unknown” in all recent records (going back at least 2 weeks on my end here fwiw).

Hopefully this can be fixed soon ??

Hi @nicecms

Yes, the most recent version of Slimstat has the issue fixed, because WPFC would appear as a “bot” so there were some hangsup. All sorted now. Update and you should be all good ??

Also working great with WP Rocket.

Hello again!

You were absolutely correct. I tried the web link and the products work great from my storefront DIR outside wp-content. I am so happy. You guys are AWESOME ?? ?? THANK YOU!

Hi!
Thank you so much for that. It really helps.
I really would prefer NOT to have my entire storefront moved into wp-content, for several reasons. But I will try the web path and see if that works. Will let you know shortly!

Question for you.
If I move a product outside wp-content, but still on my VPS server outside my WP install, and create a web path like you suggest, will EDD expose this link to my customer and create a security issue? Or will it protect it like it used to before version 2.9.13?

Anyway, Solved ??
I just create a drive share and link works fine, as is.

Done ??

Jason,

I would 100% be glad to help with my testing, yup. You got it.
It makes TOTAL sense now that you mention it, it does appear as a bot after I took a closer look. Damn. Now it’s so clear haha. Hmm.

So glad you know how to proceed ?? You rock. Good luck!

Jason,

You are the best. Slimstat rules the roost baby! ??
I can confirm too that using “free” settings in WPFC indeed works fine, so obviously those who pay for the premium plugin and expect to be able to use all the settings for the best cache experience, will be sad to see SlimStat not working in that case.

Maybe add an FAQ if this never gets resolved?
SlimStat + WPFC premium settings conflict or something.
(Notice one of the gray checkbox says “footer” for JS, see?? Hmm maybe that’s the bugger?)

I’d bet a good amount of people would find SlimStat + WPFC issues and use a jump to conclusions mat and blame Slim! lol

I guess maybe Monday or Tuesday I’ll move along and go back to using good ole WP Super Cache or something.

I needs my SlimStats ??

Thanks for rocking the best WP support Jason! Have a good weekend.

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

Jason,

Just wanted you to know that I really appreciate your time and effort trying to fix this bug. I’ve been frustrated with this for a while now, and I’m tempted to just jump ship and leave that cache.

Are you positive that the cache plugins you mentioned above work 100% flawlessly with Slimstat, regarding accurate visit traffic and no cache conflicts? ??

I guess WPFC with all grayed out options just can’t work with slim ?? oh well. It happens.

I’ll move along if you think I should ??

Hi Jason!

Thank you so much for reaching out to the dev on this issue. I am confused a bit, forgive me. Earlier in the thread, you wrote this:

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.

Now are you saying that yours just works somehow? Or just their dev site happens to work in a clean install? Does that really prove the fix? I am confused.

My clients have pro features enabled so obviously it’s a bug on their end – still – but it seems to only pertain to the grayed out options.

Can you help find out more from them? I assure you, if you enable all options on a paid premium version of the WPFC plugin, indeed the bug is very much alive and well ??

Trust me – if the dev enabled all options it would fail the test. I wonder why though. Maybe a minify issue? Thanks for the screenshot though ?? It actually really helps because now we *know* it’s a grayed out premium option that is causing the slimstat glitch. Hope I helped. PS. also gzip should be enabled, imo for all sites, so I know mine has that enabled for sure ??

Doh! You’re right. I typed it all up to but must have never hit send, sorry! (It’s actually still in my browser on my other computer, where is my brain??)

I did reach out to the WPFC folks with no response ?? I figured maybe you could consider doing it as well for one big reason: you are a fellow developer and maybe they’d listen to you and your views or requests more?

Just an idea.

If not, I’d have to switch all my sites to a new cache plugin. Are you able to confirm with 100% certainty that another cache plugin works seamlessly with SlimStat in the follow situations:

Preload enabled
static HTML files
Accurate IP address per visit (without cloudflare or with)

If so, I would feel better switching. But I was hoping WPFC would want to fix ??

Many thanks.

Jason,

Any progress on the fix for this? It’s not resolved ?? Users still can’t use the preload feature of the fantastic WP Fastest Cache plugin with static pages and Slimstat?

Are we out of luck because of the cache?