**NOTICE: This plugin is no longer maintained.** Quick Cache has been renamed to ZenCache.
qcACvariable (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.
quick_cache\\share_disable_cache_locking) to allow disabling cache locking. Simply return boolean
TRUEto 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.
sem_get()is available and would result in improved performance. Return
quick_cache\\share::cache_lock_lock_typefilter to force Semaphore cache locking, or
flockto use the default method that uses
flock(). Note that this filter must be applied using an Advanced Cache Plugin (see Dashboard → Quick Cache → Plugin Options → Theme/Plugin Developers). See also #387.
\/in one of our regex patterns. Props @jaswsinc. See #365.
/includes/utils-feed.php) and refactored the XML feed clearing routine. With these utilities in place, the
auto_clear_xml_feeds_cache()method is now much easier to deal with and comprehend. Props @jaswsinc. See #351.
/https/, separately to help break apart what was previously a much larger directory scan for sites that serve pages over both schemes. This will improve performance on both standard and Multisite network installs. See #351.
includes/share.phpfor network-wide clearing/purging/wiping, host/blog-specific clearing/purging/wiping, recursively deleting a directory, assisting in translations, and several new string utilities. Props @jaswsinc. See #351.
\quick_cache\plugin::auto_purge_*methods, giving them the proper prefix of
auto_clear_*instead to reflect proper Wipe/Clear/Purge terminology. Along with this, all of the
auto_purge_option keys have been renamed as well. See new Wipe/Clear/Purge wiki article for a description of these terms. Props @jaswsinc. See #351.
change_notifications_enablewas off. Props @jaswsinc. See #351.
scripttags could become out of order in certain scenarios. See: #45
$this->static[__FUNCTION__]. Props @jaswsinc. See #351.
auto_clear_cache()routine. See #328.
<!DOCTYPE html>. See #299.
scripttags could end up out of order in certain scenarios. See #45.
advanced-cache.php. This will help reduce configuration overhead for site owners when migrating a WordPress installation from one server to another. See #258.
XMLReader()would fail with a PHP Warning notice when it was unable to properly parse the sitemap. See #250.
calc()statements. See #286.
?qcAC=0to disable caching when you ARE caching GET Requests. See also: #210.
WP_CONTENT_DIRis now obeyed in the scenario where it's set to a path outside of
ABSPATH. See also: #95
WP_CONTENT_DIRin the "Directory/Expiration Time" options panel. See also: #206
QUICK_CACHE_PROconstant to false. See also: #229
redirect_canonical()bug workaround. See also: #209
character whitespace during CSS compression. See also: #25
http/example-com/sample-page.html). For more details, please see https://github.com/WebSharks/Quick-Cache/wiki/Branched-Cache-Structure
ob_start(). See https://github.com/WebSharks/Quick-Cache/issues/97
status_headerso that Quick Cache can properly detect calls to the WP core function
wp-content/cache/quick-cache/to provide better organization of cache files and avoid interfering with another plugin that may also be writing to the
wp-content/cache/directory. See https://github.com/WebSharks/Quick-Cache/issues/123
WP_CONTENT_URLconstants to point somewhere other than the default, Quick Cache will now obey those and use your custom directory for storing cache files. See https://github.com/WebSharks/Quick-Cache/issues/95
draftwould trigger the Auto-Purge Post routine and clear the cache for that post. Now only purges post status
privateand when transitioning from
privatepost status to
private. See https://github.com/WebSharks/Quick-Cache/issues/43
For older Changelog entries, please see the
Requires: 3.7 or higher
Compatible up to: 4.1.10
Last Updated: 11 months ago
Active Installs: 70,000+
Got something to say? Need help?