An example: i corrected the grammar in some TAGS and all my cache has cleared. Why ?
Holly Cow !
I changed my FlickR API key in a plugin, and the whole website cache was cleared.
I’m closing this.
In my website, using Quick Cache, the whole cache is deleted at least 4-5 times per day, and that makes the caching plugin of no use.
The cache needs to be totally cleared in some cases but not always.
In Quick Cache Pro you can disable the automatic clearing routines if they’re too much for your site. That way you have manual control over when the cache should be cleared.
See the full documentation here: https://github.com/websharks/quick-cache/wiki/Clear-Cache-and-Wipe-Cache-Routines
Thanks for the reply, i appreciate it.
Still, for example, changing the FlickR API ID (a number) should not clear the whole cache, for Lite, Pro, or whatever. That kind of changes that have absolutely no effect for the cached content, should not happen.
I’m not speaking for the general cleanup, that is needed when some major changes happen.
Apparently we disagree what is considered as important change.
Still, for example, changing the FlickR API ID (a number) should not clear the whole cache, for Lite, Pro, or whatever.
Quick Cache has no knowledge of anything Flickr related. I assume that you have a Flickr Plugin installed and that’s where you’re “changing the Flickr API ID”. The Flickr plugin is executing a WordPress action hook when you update the API ID and that action hook is telling Quick Cache “something major changed on this WordPress site”. Quick Cache is simply configured to detect any “major site changes” and then clear the cache when that happens, to ensure that a stale out-of-date cache file is not inadvertently served to a site visitor.
Sure, i understand that.
But the question is what is the real use of a cache if it is cleared several times per day ? Why have it ?
What is the reason to have an expiration date greater that a few hours ?
But the question is what is the real use of a cache if it is cleared several times per day ? Why have it ?
The same argument could be made for a stale cache. What good is a cache if it’s serving a cache file that no longer reflects the actual content on the site? If the site content has changed in some way, the cache needs to be cleared so that fresh cache files can be created.
What is the reason to have an expiration date greater that a few hours ?
If you have a site that doesn’t change much, you can set a longer expiration date.
So a better way must be found for QC to “understand” if some real change happened (that affects the content) or just something that doesn’t change anything as far as the cache is concerned.
I think my original example (about the Flickr API) says it all.
All in all, QC works very well, i just wish it was not so aggresive to small changes.
no reason to continue this talk.
