Plugin not purge the cache after plugin updates anymore?

btw very useful plugin, my only problem is the API hiding in the cache-enabler
cache, if have way pass it and the short-link API be present when bots get inside the websites is be amazing.

the API key is much more important to me from the cache cleaning after plugin update because have plugin can clean the cache for your every day.

but of course, I preferred cache enabler will solve it for me as well as before.

We’re really happy to hear the plugin is useful for you. If Cache Enabler is updated then the plugin will clear its own cache. This hasn’t been changed. On a quick test from version 1.7.1 to 1.7.2 the cache was cleared as expected when Cache Enabler was updated.

You’ve already brought up the topic of the Link response header in the past (https://www.ads-software.com/support/topic/cache-enabler-not-support-short-link-hsts/). Please refer to that post for my detailed response. If you’d like to have the cache bypassed in certain circumstances, such as if a bot makes a request to your website, consider creating your own snippet to extend Cache Enabler to support this. That would bypass the Cache Enabler cache and allow the desired Link response header to be set by WordPress. For example, you could check the User-Agent request header and bypass the cache if a certain bot makes a request, for example: https://pastebin.com/dFYZ0RB6

In the snippet above you would replace BotName with the bot you’re wanting to exclude (case sensitive). This snippet would be added to your website, such as your functions.php file.

My apologies, excluding a specific User-Agent actually won’t work with the cache_enabler_bypass_cache hook due what’s posted in #189. We’re working on removing that limitation so this is supported. I’ll have to follow up here once this has changed.

• This reply was modified 3 years, 4 months ago by Anonymous User 16850768. Reason: correction

yeah but this topic is before a long time ago, and this is not the HSTS header.

Is the new API short link of WordPress…

this thing connect to all the plugin, plugin work different from WordPress 5.5
and the bots as well…

this short link is can be important to the bots crawl the site.

Now my topic was over a year…
nobody takes care of it and believes me, this plugin is very useful,
especially to people who use Autoptimize and search a little bit more boost.

I personally very much want to use the plugin.
but right now i don’t use him because of this issue, (and many more users as well).

sometimes 1 – 2 points in page speed not worth the damage the bots can do to you.
and believe me, Cache enabler is a very good plugin.

@coreyk

The title says: “Plugin not purge the cache after plugin updates anymore?”

FYI, this is not what I experience.

My CE settings have the 3x “Clearing” boxes empty. So I am not clearing for any reason and I have Cache Expiry = 24 hours.

However, I still find that when any plugin updates, the cache is cleared automatically.

Since WP 5.8 updated 4 days ago, there have been many plugin updates – and it from what I see, each plugin update clears the cache.

No complaints – just FYI.

Regards and thanks,
Angus

@hiskingdomprophecy, I originally thought the thread starter was referring to when Cache Enabler had been updated, but I may have been mistaken as the thread starter was possibly referring to the change in the cache clearing settings going from version 1.6.2 to 1.7.0.

To clear things up, the cache is automatically cleared if Cache Enabler is updated, which has been the case since version 1.2.3. As of version 1.7.0, clearing the site cache is automatically done when a plugin is updated and is no longer a setting (#215). Cache Enabler automatically handles clearing the site cache when the core, themes, and plugins are updated.

Yeah but if you work with another plugin like Autoptimize?
Any time have an update is a problem, but I notice cache enabler refresh the cache every 10 sec (This kind of Nginx caching style – I very liked that)

the only problem as I said is the API Shortlink.
This must be present to the bots.

I wish you will fix it already and I will be able to install the cache enabler.

Please if you have an update about the short link I will be more than glad.
@coreyk

• This reply was modified 3 years, 4 months ago by Nadav Levi.
• This reply was modified 3 years, 4 months ago by Nadav Levi.