Branched Cache Structure; Not Clearing Old qc-c-* Files
#127
Labels
Milestone
Comments
jaswrks
pushed a commit
that referenced
this issue
Apr 26, 2014
jaswrks
pushed a commit
to wpsharks/comet-cache-pro
that referenced
this issue
Apr 26, 2014
This was referenced Apr 26, 2014
|
Ah! Great catch! Thanks so much for reporting and patching this. I'll merge the Pull Request shortly. |
jaswrks
pushed a commit
to wpsharks/comet-cache-pro
that referenced
this issue
Aug 17, 2015
- Enhancing DirStats class. - Improving organization of SCSS files. - Improving cache directory utilities; integrating DirStats where applicable. - Implementing Admin Bar Directory Stats. - Improving AJAX clear/wipe cache interaction. - Creating `cleanupCache()` method to give the CRON cleanup a method of its own. - Improving PostloadUtils, excluding all plugin actions from automatic user cache clearing. This was already the case (for the most), but this change allows us to pick up ALL plugin actions. - Build `zc-` prefixed files using `SHORT_NAME` for easier branding. - Removing FontAwesome dependency in favor of Sharkicons. - Updating to the latest release of Sharkicons and integrating this w/ ZenCache. - Adding `wurgeCache()` and `autoWurgeCache()` for global cache purging. See: wpsharks/comet-cache#83 and wpsharks/comet-cache#127
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
While testing the latest dev branch I noticed that if you add the latest version of Quick Cache or Quick Cache Pro to a site that was previously running a version that used the older cache structure (i.e.
qc-c-*files); those files never get cleared away; even on a full wipe of the cache. Not a huge issue, but we don't want those old files sitting around whenever the new version is released.The text was updated successfully, but these errors were encountered: