Jason Crouse

Hi @olegelukin

that’s not a bug, it’s a feature. Please see the legend in the bottom right hand corner. We are working on upgrading the rendering tool, since AmMaps 4.0 was released a few months ago and introduces performance improvements and new map features.

Best,
Jason

Got it – finally got the search terms limit working and it was a schoolboy error – I forgot that shortcodes should be added in the text editor, rather than the visual one.

Terrific! Nicely done, sir. Time to celebrate at that white bar! Haha.

Take care,
Jason

Thank you for working with me on fixing that issue with your fantastic plugin!

Jason

Hi @steveraven

strange that limit_results doesn’t work for you. Enabling Debug Mode in the settings should show you the SQL query that was used, and you should see the “LIMIT” clause in it.

Yes, the second one is definitely not what you’re looking for. I will add your request to our wishlist for future consideration! Or you could write your own shortcode with a little help from a PHP developer 😉

Best,
Jason

My bad, I misread your original request. Replace post_link with searchterms:

[slimstat f="recent" w="searchterms"]limit_results equals 10[/slimstat]

Unfortunately Slimstat doesn’t currently support linking to search engine results pages connected to those keywords. The closest you could do is:

[slimstat f="recent" w="referer"]searchterms is_not_empty #&&&limit_results equals 10[/slimstat]

Jason

• This reply was modified 6 years, 10 months ago by Jason Crouse.

So, just a quick status update.

Emre insists that the issue is NOT related to the PRO version, and he can’t give me a copy of the PRO version to test. He thinks this might be related to the fact that in “Client Mode”, Slimstat does not track bots, and in Preload Cache, WPFC acts as a bot when retrieving the content from the website itself. In short, WPFC pretends to be a browser and takes a snapshot of each page on your website, when Preload Cache is enabled. Now, Slimstat sees that as a bot, and in Client Mode will ignore those page views (and not enqueue the tracker). Early next week I will run some tests on my end and see if this is the case. If that’s true, I will work on my code to see if I can add some kind of exception for WPFC based on its user agent. Would you be available to test this new code, once available, with your PRO version of WPFC?

Thanks,
Jason

Hi @thescarletfire,

thank you for confirming that the FREE version of WPFC does not cause the issue. I’m not that crazy after all 😀

Maybe add an FAQ if this never gets resolved?
SlimStat + WPFC premium settings conflict or something.

Yes, if the developer doesn’t provide a solution in a few days, I’ll definitely add a note to our FAQs to let people know about this incompatibility issue.

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

Why not use a free Cloudflare account? Does your provider allow you to point the DNS servers for your website to an external resource? That would solve the problem even better than any other caching plugin.

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

Glad to be of service, my friend!

Best,
Jason

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.

I setup a test site on our dev environment, with the FREE version of WPFC and a clean install of Slimstat. While back then I could reproduce the bug as I had mentioned, now it looks like I can’t in this new environment I created. So, yes, it must be something related to the PRO version. I’ve asked the developer to see if he could provide a copy for testing purposes. I also invited him to reply directly to this thread with any helpful information he might have.

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 🙁

I’m 100% certain that the bug is happening for you, don’t worry! I know how frustrating it is when you have a problem that is hard to reproduce. Believe me.

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.

If you don’t mind, let’s just wait a few more days and see if the developer and I can find the problem and fix it. I feel like he has a great solid product, and I would love to be able to say that Slimstat works just fine with WPFC 😀

Thank you,
Jason