Releases: wpsharks/comet-cache
v150314
- Bug Fix: Fixed a bug in the Quick Cache back compat. method
\zencache\share\apply_wp_filters()
. It was not passing the ZenCache-filtered value through the Quick Cache back compat. routine. This bug affected sites that had disabled automatic cache clearing routines via a filter. - Bug Fix (Pro): Updated Static CDN Filters whitelist to include font file extensions
eot,ttf,otf,woff
, as site owners may wish to serve fonts with these extensions from the CDN (this would require a custom CORS configuration; see this article for instructions). See #427. - Bug Fix (Pro): Updated Static CDN Filters blacklist to exclude font file extensions
eot,ttf,otf,woff
by default, as they require custom CORS configuration to display properly. See #427. - Bug Fix (Pro): The Static CDN Filters feature was calling a protected method that was requiring PHP v5.4+ but now the Static CDN Filters feature works with PHP v5.3+. See #426.
- Bug Fix: Fixed a zero-byte
advanced-cache.php
bug related to migrating from Quick Cache. When you deleted/uninstalled Quick Cache after upgrading to ZenCache, the Quick Cache uninstallation process would empty theadvanced-cache.php
file, resulting in the site no longer being cached, despite ZenCache being active. ZenCache now continuously checks to make sure thatadvanced-cache.php
is installed properly. See #432.
ZenCache v150218
Announcing ZenCache, formerly Quick Cache!
We are very excited to announce the release of ZenCache, an advanced WordPress caching plugin inspired by simplicity. ZenCache is the successor to Quick Cache, a very popular WordPress caching plugin that has been downloaded over 1 million times and won acclaim for its speed, simplicity, and ease of configuration. Read the full announcement here.
ZenCache is an evolution of Quick Cache. It comes with a completely refactored codebase, subtle UI enhancements, internal optimizations; along with full backward compatibility with all previous versions of Quick Cache Lite and Quick Cache Pro. In fact, installing ZenCache on a site that was previously running Quick Cache is a piece of cake! Watch this video to learn more. All configuration options are preserved.
- New Pro Feature: CDN Integration: With the announcement and release of ZenCache we are excited to also announce a new, highly-requested feature: Static CDN Filters. This feature allows you to serve some and/or ALL static files on your site from a CDN of your choosing. See also: Introduction to Static CDN Filters.
- Full Backwards Compatibility with Quick Cache and Quick Cache Pro: ZenCache is fully backwards compatible with all previous versions of Quick Cache Lite and Quick Cache Pro. Simply install ZenCache and your existing Quick Cache options will preserved by ZenCache.
Quick Cache v150129.2
- NOTICE: Quick Cache is now ZenCache! No further updates will be made to Quick Cache after March 6th, 2015; see migration instructions.
- Enhancement: Improved the handling of long cache filenames, where especially long URLs were generating cache filenames that were too long for some file systems to handle. Props @jaswsinc. See #275.
- Bug Fix: Removed erroneous call to
from_lt_v150129_1()
. See: this GitHub issue for technical details.
v150129.1
- NOTICE: Quick Cache is now ZenCache! No further updates will be made to Quick Cache after March 6th, 2015; see migration instructions.
- Enhancement: Improved the handling of long cache filenames, where especially long URLs were generating cache filenames that were too long for some file systems to handle. Props @jaswsinc. See #275.
v150129
- Bug Fix (Pro): Fixed a bug where the Pro Updater would fail when FTP or SFTP details via the WordPress Dashboard are required to perform updates. Props @jaswsinc. See #389.
- Bug Fix: Several fixes for a stubborn bug related to "Fatal Error: 'Unable to clear dir'" error messages and errors referencing "SplFileInfo::getMTime(): stat failed". Props @jaswsinc. See #397.
- Bug Fix (Pro): Fixed a bug where the
qcAC
variable (used to force-enable/disable GET Request caching) was not respected properly whenever a URL contained a query string and a user was currently logged into the site. Props @jaswsinc. See #401.
v150121 (Release Candidate)
- Bug Fix (Pro): Fixed a bug where the Pro Updater would fail when FTP or SFTP details via the WordPress Dashboard are required to perform updates. Props @jaswsinc. See #389.
- Bug Fix: Several fixes for a stubborn bug related to "Fatal Error: 'Unable to clear dir'" error messages and errors referencing "SplFileInfo::getMTime(): stat failed". Props @jaswsinc. See #397.
- Bug Fix (Pro): Fixed a bug where the
qcAC
variable (used to force-enable/disable GET Request caching) was not respected properly whenever a URL contained a query string and a user was currently logged into the site. Props @jaswsinc. See #401.
v141231
- Bug Fix: Addressed another issue related to "Fatal Error: 'Unable to clear dir'" and tmp directories that don't get cleared by Quick Cache. This fix discards iteration references before renaming the tmp directories. Props @jaswsinc. See #288.
- Bug Fix: We have had a few reports of getMTime Stat failing when clearing the cache. This fix clears the Stat Cache before iteration when deleting files from the cache directory. Props @jaswsinc. See #385.
- Enhancement: Added a new filter (
quick_cache\\share_disable_cache_locking
) to allow disabling cache locking. Simply return booleanTRUE
to this filter to disable cache locking. This may be useful for site owners who are experiencing issues with cache locking on web hosting platforms with filesystems that don't properly support locking. Note that this filter must be applied using an Advanced Cache Plugin (see Dashboard → Quick Cache → Plugin Options → Theme/Plugin Developers). See also #387. - Enhancement: Added a new filter that allows forcing Semaphore cache locking on hosting platforms where
sem_get()
is available and would result in improved performance. Returnsem
to thequick_cache\\share::cache_lock_lock_type
filter to force Semaphore cache locking, orflock
to use the default method that usesflock()
. Note that this filter must be applied using an Advanced Cache Plugin (see Dashboard → Quick Cache → Plugin Options → Theme/Plugin Developers). See also #387.
v141229 (Release Candidate)
- Bug Fix: We have had a few reports of getMTime Stat failing when clearing the cache. This fix clears the Stat Cache before iteration when deleting files from the cache directory. Props @jaswsinc. See #385.
- Bug Fix: Addressed another issue related to "Fatal Error: 'Unable to clear dir'" and tmp directories that don't get cleared by Quick Cache. This fix discards iteration references before renaming the tmp directories. Props @jaswsinc. See #288.
- Enhancement: Added a new filter (
quick_cache\\share_disable_cache_locking
) to allow disabling cache locking. Simply return booleanTRUE
to this filter to disable cache locking. This may be useful for site owners who are experiencing issues with cache locking on web hosting platforms with filesystems that don't properly support locking. Note that this filter must be applied using an Advanced Cache Plugin (see Dashboard → Quick Cache → Plugin Options → Theme/Plugin Developers). See also #387. - Enhancement: Added a new filter that allows forcing Semaphore cache locking on hosting platforms where
sem_get()
is available and would result in improved performance. Returnsem
to thequick_cache\\share::cache_lock_lock_type
filter to force Semaphore cache locking, orflock
to use the default method that usesflock()
. Note that this filter must be applied using an Advanced Cache Plugin (see Dashboard → Quick Cache → Plugin Options → Theme/Plugin Developers). See also #387.
v141205
- Bug Fix: Addressed another issue with "Fatal Error: 'Unable to clear dir'" messages by adding new blocking methods for cache lock and unlock, making it so that cache writes (including clearing, purging, wiping) all gain an exclusive lock on the cache directory while work is underway. Props @jaswsinc. See #288.
- Bug Fix: Fixed a Home Page clearing bug that arose in the previous release as the result of an extra leading
\/
in one of our regex patterns. Props @jaswsinc. See #365.
Note: This release includes a hotfix for a bug discovered in v141204. See this comment for details.
v141204
- Bug Fix: Addressed another issue with "Fatal Error: 'Unable to clear dir'" messages by adding new blocking methods for cache lock and unlock, making it so that cache writes (including clearing, purging, wiping) all gain an exclusive lock on the cache directory while work is underway. Props @jaswsinc. See #288.
- Bug Fix: Fixed a Home Page clearing bug that arose in the previous release as the result of an extra leading
\/
in one of our regex patterns. Props @jaswsinc. See #365.