Raam Dev

@ronnieg303 Quick Cache already detects many such changes and figures out when it should clear the cache. For example, when you switch your theme, Quick Cache detects this and wipes...

Including comments from #302 (so that it can be closed in favor of this issue): @ronnieg303 writes... > Enhancement Request: > > I have a large website where the content...

Including comment from #482 (so that it can be closed in favor of this issue): @ronnieg303 writes... > Add an optional cache expiration override parameter to urls in the ACE...

> things begin to get hairy; i.e., more difficult to debug. This is easily resolved by providing more debugging information inside the cached files themselves. For example, if there's a...

Requested here: https://wordpress.org/support/topic/shorter-cache-expiration-time-for-the-homepage/

@garrett-eclipse Thanks for the feature request! I think this is a great idea.

@jaswsinc Could I get an estimate on this when you get a chance?

@Blackbam Thanks for the suggestion and the Pull Request! :-) I apologize for not responding to this sooner. Could you please submit this as a Pull Request to the [Comet...

@lkraav Thank you for opening this GitHub issue. :-) @jaswsinc Could I get an estimate on this?

@danielmt2k Clearing the entire cache on activation/deactivation of a plugin is expected behavior. Comet Cache does that because it has no way of knowing if the plugin being activated/deactivated changes...