Feature Request: Add option to disable `auto_clear_cache` #23
Comments
Okay. I just found out that this happens when you create a new post and save it as draft. Publishing a post doesn't give this problem but only when clicking the save as draft button. |
@sarangandk Thanks for reporting this important issue.See: https://github.com/WebSharks/Quick-Cache/blob/000000-dev/quick-cache/quick-cache.inc.php#L110
The intended behavior is to clear only the cache for the specific Post/Page being saved. This is working as expected in my tests thus far; e.g. I've been unable to reproduce this so far. However, see: https://github.com/WebSharks/Quick-Cache/blob/000000-dev/quick-cache/quick-cache.inc.php#L121
@sarangandk If you create a new category or tag in the process of creating a new Post/Page; this CAN result in a complete clearing of the cache. Is it possible this is what may have triggered this on your installation? |
Yes, you were right. This happended because I created a post, created new category and saved as draft. I have a suggestion: Add an option to completely disable 'complete clearing of the cache' because it costs server resources everytime this happens. Especially for a WordPress photo website which have about 7 million photos and millions of cached files. All other single post cache option is fine and it's important. Please consider this in future versions. Thanks. |
@sarangandk Point taken, thank you for the reply and feedback. Happy holidays :-) |
I have this problem too. "Single post publish and draft = Clearing/ Resets all caches" If i add thumbnail and tag in post Clearing/ Resets all caches but i don't add thumbnail and tag in post caches not clearing. Help me please. |
Hello Jas, From what i read here, it is supposed to cache the actual published post and maybe home page but with the line in quote above, it seems it's not the normal behaviour. I am new to this cache plugin and i suck using terms to describe problems like you would do, but i hope you understand my explanation and i hope you respond. Please reply, i might need some further assistance.. |
@Daniel1206 Could you please open a new issue for this? |
@sarangandk @Daniel1206 FYI, the problem with saving as Draft incorrectly clearing the cache was fixed in v140605. Regarding this feature request to be able to disable Moving this to the Future Release milestone. |
Good and thanks. |
@sarangandk writes in #337...
Thank you for the further explanation about why this feature is necessary. I can see with such a large site why you'd want to completely disable the automatic purging routines. At the very least, I can make it possible to disable these automatic purging routines through a filter, so that you don't have to keep modifying the code after each update. Let me work on that now. I'll update here when I have more information. |
This feature has been added to Quick Cache Pro and will go out with the next release. For full documentation on this feature and how to use it, please see https://github.com/websharks/quick-cache/wiki/Clear-Cache-and-Wipe-Cache-Routines |
Next release changelog:
|
Very cool! Love the wiki article too.
Nice! |
For unknown reason, it didn't worked after I upgraded to the latest version 141110. I tried to restore all settings to default and everything works fine now. |
I'm using Quick Cache latest version on a very very high traffic site. Without any caching plugins my server will not survive. When I publish a single post then Quick Cache clears all the caches in site instead of only clear that particular post's cache and homepage's cache. Because of that time was peek time, my server was overloaded and everything went down.
Quick Cache: detected changes. Found cache files for this site (auto-clearing).
Why does you plugin reset the caches for whole site when I only publish a single post? I need a solution for this problem.
Please advice.
The text was updated successfully, but these errors were encountered: