Releases: wpsharks/comet-cache
Releases · wpsharks/comet-cache
v140605
http://www.websharks-inc.com/product/quick-cache/
- New Feature: Branched Cache Structure. Cache files are now written to the cache directory using a more intuitive format of
PROTOCOL
/HOSTNAME
/PERMALINK
(e.g.,http/example-com/sample-page.html
). For more details, please see https://github.com/WebSharks/Quick-Cache/wiki/Branched-Cache-Structure - New Feature: 404 Page caching. It's now possible to enable/disable the caching of 404 requests. Enabling this feature generates a single cache file for your 404 Page and then symlinks future 404 requests to that cache file. See Dashboard -> Quick Cache -> Plugin Options -> 404 Requests.
- New Feature (Pro): HTML Compressor (experimental). This new experimental feature automatically combines and compresses CSS/JS/HTML code. See Dashboard -> Quick Cache -> Plugin Options -> HTML Compressor. For more details about how this feature works, please see https://github.com/WebSharks/HTML-Compressor
- New Feature (Pro): Auto-Cache Engine. When enabled, the Auto-Cache Engine will pre-cache your site at 15-minute intervals, rebuilding cache files when necessary (it will not rebuild cache files until they have expired). This helps eliminate the slowness a user may experience when visiting a page on your site that has not yet been cached. See Dashboard -> Quick Cache -> Plugin Options -> Auto-Cache Engine.
- New Feature: Auto-Purge "Author Page". When a single Post/Page is changed in some way, Quick Cache can also purge any existing cache files for the associated Author Page. See Dashboard -> Quick Cache -> Plugin Options -> Clearing the Cache. (This option is enabled by default; disabling this requires Quick Cache Pro.)
- New Feature: Auto-Purge "Category Archives". When a single Post/Page is changed in some way, Quick Cache can also purge any existing cache files for the associated Category archive views. See Dashboard -> Quick Cache -> Plugin Options -> Clearing the Cache. (This option is enabled by default; disabling this requires Quick Cache Pro.)
- New Feature: Auto-Purge "Tag Archives". When a single Post/Page is changed in some way, Quick Cache can also purge any existing cache files for the associated Tag archive views. See Dashboard -> Quick Cache -> Plugin Options -> Clearing the Cache. (This option is enabled by default; disabling this requires Quick Cache Pro.)
- New Feature: Auto-Purge "Custom Term Archives". When a single Post/Page is changed in some way, Quick Cache can also purge any custom Terms that may have their own Term archive views. See Dashboard -> Quick Cache -> Plugin Options -> Clearing the Cache. (This option is enabled by default; disabling this requires Quick Cache Pro.)
- Enhancement: Improved conflict handling of other plugins using
ob_start()
. See #97 - Enhancement: Added a postload filter for
status_header
so that Quick Cache can properly detect calls to the WP core functionstatus_header()
- Enhancement: The Quick Cache cache directory has been changed to
wp-content/cache/quick-cache/
to provide better organization of cache files and avoid interfering with another plugin that may also be writing to thewp-content/cache/
directory. See #123 - Enhancement: New detailed debugging notes (see Dashboard -> Quick Cache -> Plugin Options -> Enable/Disable). There is now an extra option to show detailed debugging information in addition to the Quick Cache notes in the HTML source. For now, this feature only applies when the HTML Compressor is enabled.
- Enhancement: Better Debugging Notices. If Quick Cache is not caching a particular page (such as when a logged-in user visits the site and logged-in user caching is not enabled), Quick Cache will now report why that page is not being cached in the HTML notes.
- Enhancement: Improved compatibility with the Nav Menu Roles plugin. See #164
- Bug Fix: Obey custom content directories. If you have customized your
WP_CONTENT_DIR
andWP_CONTENT_URL
constants to point somewhere other than the default, Quick Cache will now obey those and use your custom directory for storing cache files. See #95 - Bug Fix: Scheduled posts now trigger the clearing of any associated archive views when those posts go live (assuming you have those archive views set to Auto-Purge in Dashboard -> Quick Cache -> Plugin Options -> Clearing the Cache). See #26
- Bug Fix: Fixed a bug where saving a post as
draft
would trigger the Auto-Purge Post routine and clear the cache for that post. Now only purges post statuspublish
andprivate
and when transitioning frompublish
orprivate
post status todraft
,future
, orprivate
. See #43 - Bug Fix: Split/paginated comments and multi-page Posts/Page cache files are now purged properly when the post cache is purged. See #75
v140529 (Release Candidate 2)
Changelog:
- Bug Fix: In some scenarios, database error pages were being cached. This bug fix uses the PHP function
http_response_code()
to improve the routines that check for non-cachable status codes. See #175 - Bug Fix: Unlocked the output buffer for better compatibility with themes/plugins that might use output buffering. See #176
This release includes changes from v140520 (Release Candidate 1). See v140520 changelog.
v140520 (Release Candidate)
Changelog:
- New Feature: Branched Cache Structure. Cache files are now written to the cache directory using a more intuitive format of
PROTOCOL
/HOSTNAME
/PERMALINK
(e.g.,http/example-com/sample-page.html
). For more details, please see https://github.com/WebSharks/Quick-Cache/wiki/Branched-Cache-Structure - New Feature: 404 Page caching. It's now possible to enable/disable the caching of 404 requests. Enabling this feature generates a single cache file for your 404 Page and then symlinks future 404 requests to that cache file. See Dashboard -> Quick Cache -> Plugin Options -> 404 Requests.
- New Feature (Pro): HTML Compressor (experimental). This new experimental feature automatically combines and compresses CSS/JS/HTML code. See Dashboard -> Quick Cache -> Plugin Options -> HTML Compressor. For more details about how this feature works, please see https://github.com/WebSharks/HTML-Compressor
- New Feature (Pro): Auto-Cache Engine. When enabled, the Auto-Cache Engine will pre-cache your site at 15-minute intervals, rebuilding cache files when necessary (it will not rebuild cache files until they have expired). This helps eliminate the slowness a user may experience when visiting a page on your site that has not yet been cached. See Dashboard -> Quick Cache -> Plugin Options -> Auto-Cache Engine.
- New Feature: Auto-Purge "Author Page". When a single Post/Page is changed in some way, Quick Cache can also purge any existing cache files for the associated Author Page. See Dashboard -> Quick Cache -> Plugin Options -> Clearing the Cache. (This option is enabled by default; disabling this requires Quick Cache Pro.)
- New Feature: Auto-Purge "Category Archives". When a single Post/Page is changed in some way, Quick Cache can also purge any existing cache files for the associated Category archive views. See Dashboard -> Quick Cache -> Plugin Options -> Clearing the Cache. (This option is enabled by default; disabling this requires Quick Cache Pro.)
- New Feature: Auto-Purge "Tag Archives". When a single Post/Page is changed in some way, Quick Cache can also purge any existing cache files for the associated Tag archive views. See Dashboard -> Quick Cache -> Plugin Options -> Clearing the Cache. (This option is enabled by default; disabling this requires Quick Cache Pro.)
- New Feature: Auto-Purge "Custom Term Archives". When a single Post/Page is changed in some way, Quick Cache can also purge any custom Terms that may have their own Term archive views. See Dashboard -> Quick Cache -> Plugin Options -> Clearing the Cache. (This option is enabled by default; disabling this requires Quick Cache Pro.)
- Enhancement: Improved conflict handling of other plugins using
ob_start()
. See #97 - Enhancement: Added a postload filter for
status_header
so that Quick Cache can properly detect calls to the WP core functionstatus_header()
- Enhancement: The Quick Cache cache directory has been changed to
wp-content/cache/quick-cache/
to provide better organization of cache files and avoid interfering with another plugin that may also be writing to thewp-content/cache/
directory. See #123 - Enhancement: New detailed debugging notes (see Dashboard -> Quick Cache -> Plugin Options -> Enable/Disable). There is now an extra option to show detailed debugging information in addition to the Quick Cache notes in the HTML source. For now, this feature only applies when the HTML Compressor is enabled.
- Enhancement: Better Debugging Notices. If Quick Cache is not caching a particular page (such as when a logged-in user visits the site and logged-in user caching is not enabled), Quick Cache will now report why that page is not being cached in the HTML notes.
- Bug Fix: Obey custom content directories. If you have customized your
WP_CONTENT_DIR
andWP_CONTENT_URL
constants to point somewhere other than the default, Quick Cache will now obey those and use your custom directory for storing cache files. See #95 - Bug Fix: Scheduled posts now trigger the clearing of any associated archive views when those posts go live (assuming you have those archive views set to Auto-Purge in Dashboard -> Quick Cache -> Plugin Options -> Clearing the Cache). See #26
- Bug Fix: Fixed a bug where saving a post as
draft
would trigger the Auto-Purge Post routine and clear the cache for that post. Now only purges post statuspublish
andprivate
and when transitioning frompublish
orprivate
post status todraft
,future
, orprivate
. See #43 - Bug Fix: Split/paginated comments and multi-page Posts/Page cache files are now purged properly when the post cache is purged. See #75
v140104
http://www.websharks-inc.com/product/quick-cache/
- New Options for Feed Caching. It's now possible to control RSS, RDF, and Atom Feed caching. The new default is for feed caching to be disabled, which resolves an issue where new posts don't show up in the feed until the cache is cleared. This version of Quick Cache disables feed caching to prevent this from happening. If you wish to cache feeds, you can enable feed caching in the options. See: #44
- New Automatic Updater for Quick Cache Pro. Quick Cache Pro now includes an automatic updater which lets you to keep Quick Cache Pro updated right from within your WordPress Dashboard. To upgrade to a new version of Quick Cache Pro using the Automatic Updater, simply fill in your WebSharks-Inc.com credentials in the new Plugin Updater sub-panel (Quick Cache Pro -› Plugin Updater). See: #21
v131224
http://www.websharks-inc.com/product/quick-cache/
- New Lite Enhancement. The Home Page cache and Posts Page cache are now automatically purged when necessary (such as when a new post is published). See: #40
- Improved Quick Cache version check notice.
- Improved Quick Cache options validation.
- Bug Fix. Quick Cache was previously not properly excluding systematic WordPress areas reliably, e.g. any file that begins with
wp-
and/or thexmlrpc
file. These are now properly auto-excluded. On Multisite installations,/files/
is also auto-excluded from being cached. This bug required fixing incorrect instances of[?$]
in regex patterns. See: #41 - Multisite Enhancement. When running Quick Cache on Multisite Network installation, only allow the plugin to be "Network Activated" (becuase that is how Quick Cache is designed to work). See: #50
- Multisite Enhancement. New 'Wipe' button allows a site owner to clear (wipe) the cache for all sites in a Multisite Network at once. See: #48
- Multisite Bug Fix. Clearing the cache on a Multisite Network configured to use sub-directories now works properly. See: #39
- Multisite Bug Fix. Fixed unmatched closing parenthesis in regex. See: #37
- Multisite Bug Fix. Added support for
PATH_CURRENT_SITE
and$GLOBALS['base']
. - Multisite Bug Fix. Removed depreciated VHOST code that was causing issues with clearing the cache.