Specifications

  • Stable tag: 140725
  • Requires at least: 3.7
  • Tested up to: 3.9.1
  • Text Domain: quick-cache
  • License: GPLv2 or later
  • License URI: http://www.gnu.org/licenses/gpl-2.0.html
  • Contributors: WebSharks, JasWSInc, raamdev, anguz
  • Donate link: http://www.websharks-inc.com/r/wp-theme-plugin-donation/
  • Tags: cache, quick cache, quick-cache, quickcache, speed, performance, loading, generation, execution, benchmark, benchmarking, debug, debugging, caching, cash, caching, cacheing, super cache, advanced cache, advanced-cache, wp-cache, wp cache, options panel included, websharks framework, w3c validated code, includes extensive documentation, highly extensible

Speed up your site (BIG time!) — Quick Cache provides reliable page caching for WordPress. Easy-to-use (very simple installation).

If you care about the speed of your site, Quick Cache is one of those plugins that you absolutely MUST have installed :-) Quick Cache takes a real-time snapshot (building a cache) of every Page, Post, Category, Link, etc. These snapshots are then stored (cached) intuitively, so they can be referenced later, in order to save all of that processing time that has been dragging your site down and costing you money.

The Quick Cache plugin uses configuration options that you select from the options panel. See: Quick Cache -› Options in your Dashboard. Once a file has been cached, Quick Cache uses advanced techniques that allow it to recognize when it should and should not serve a cached version of the file. By default, Quick Cache does not serve cached pages to users who are logged in, or to users who have left comments recently. Quick Cache also excludes administrative pages, login pages, POST/PUT/DELETE/GET(w/ query string) requests and/or CLI processes.

Features

  • SIMPLE and well-documented configuration (just enable and you're all set!).
  • The ability to set an automatic expiration time for cache files.
  • Client-Side Caching (to allow double-caching in the client-side browser).
  • Caching for 404 requests to reduce the impact of those requests on the server.
  • RSS, RDF, and Atom Feed caching.
  • The ability to cache or ignore URLs that contain query strings (GET Requests).
  • An Advanced Cache Plugin system for theme and plugin developers.

Pro Features

  • The ability to cache logged-in users too! (VERY powerful, particularly for membership sites).
  • A new improved "Clear Cache" button in the admin bar (along with an option to enable/disable this feature).
  • The ability to disable Dashboard notifications related to automatic clearing/purging on change detections.
  • The ability to clear Markdown-related cache files generated by the s2Clean theme for WordPress (if installed).
  • Import/Export functionality for Quick Cache configuration files.
  • URI exclusion patterns (now supporting wildcards too).
  • User-Agent exclusion patterns (now supporting wildcards too).
  • HTTP referrer exclusion patterns (now supporting wildcards too).
  • A Dynamic Version Salt (customize the caching engine).
  • HTML Compressor to automatically combine and compresses CSS/JS/HTML code.
  • Auto-Cache Engine to pre-cache your site at 15-minute intervals.
  • An Automatic Updater to update Quick Cache Pro from your WordPress Dashboard.
  • Rockstar support for all Quick Cache features.

TIP: you can preview Pro features in the free version by clicking the "Preview Pro Features" link at the top of your Quick Cache options.

Screenshot 1
Screenshot 2
Screenshot 3
Screenshot 4
Screenshot 5
Screenshot 6
Screenshot 7
Screenshot 8
Screenshot 9
Screenshot 10

Quick Tip: WordPress® can only deal with one cache plugin being activated at a time. Please uninstall any existing cache plugins that you've tried in the past. In other words, if you've installed W3 Total Cache, WP Super Cache, DB Cache Reloaded, or any other caching plugin, uninstall them all before installing Quick Cache. One way to check, is to make sure this file: wp-content/advanced-cache.php and/or wp-content/object-cache.php are NOT present; and if they are, delete these files BEFORE installing Quick Cache. Those files will only be present if you have a caching plugin already installed. If you don't see them, you're ready to install Quick Cache :-).

Quick Cache is Very Easy to Install

  1. Upload the /quick-cache folder to your /wp-content/plugins/ directory.
  2. Activate the plugin through the Plugins menu in WordPress®.
  3. Navigate to the Quick Cache panel & enable it.

How will I know Quick Cache is Working?

First of all, make sure that you've enabled Quick Cache. After you activate the plugin in WordPress, go to the Quick Cache options panel and enable caching (you can't miss the big yellow checkbox). Then scroll to the bottom and click Save All Changes. All of the other options on that page are already pre-configured for typical usage. Skip them all for now. You can go back through all of these later and fine-tune things the way you like them.

Once Quick Cache has been enabled, you'll need to log out (and/or clear browser cookies). Cache files are NOT served to visitors who are logged in, and that includes you too :-) Cache files are NOT served to recent commenters either. If you've commented (or replied to a comment lately); please clear your browser cookies before testing.

To verify that Quick Cache is working, navigate your site like a normal visitor would. Right-click on any page (choose View Source), then scroll to the very bottom of the document. At the bottom, you'll find comments that show Quick Cache stats and information. You should also notice that page-to-page navigation is lightning fast compared to what you experienced prior to installing Quick Cache.

Running Quick Cache On A WordPress® Multisite Installation

WordPress® Multisite Networking is a special consideration in WordPress®. If Quick Cache is installed under a Multisite Network installation, it will be enabled for ALL blogs the same way. The centralized config options for Quick Cache, can only be modified by a Super Administrator operating on the main site. Quick Cache has internal processing routines that prevent configuration changes, including menu displays; for anyone other than a Super Administrator operating on the main site.

EMERGENCY: If All Else Fails (How-To Remove Quick Cache)

Ordinarily you can just deactivate Quick Cache from the plugins menu in WordPress. However, if you're having a more serious issue, please follow the instructions here.

  1. Log into your site via FTP; perhaps using FileZilla.
  2. Delete this file: /wp-content/advanced-cache.php
  3. Delete this directory: /wp-content/plugins/quick-cache/
  4. Remove this line from your /wp-config.php file: define('WP_CACHE', TRUE);

Quick Cache is now completely uninstalled and you can start fresh :-)

How do I know that Quick Cache is working the way it should be?

First of all, make sure that you've enabled Quick Cache. After you activate the plugin, go to the Quick Cache options panel and enable it, then scroll to the bottom and click Save All Changes. All of the other options on that page are already pre-configured for typical usage. Skip them all for now. You can go back through all of them later and fine-tune things the way you like them.

Once Quick Cache has been enabled, you'll need to log out (and/or clear browser cookies). Cache files are NOT served to visitors who are logged in, and that includes you too :-) Cache files are NOT served to recent commenters either. If you've commented (or replied to a comment lately); please clear your browser cookies before testing.

To verify that Quick Cache is working, navigate your site like a normal visitor would. Right-click on any page (choose View Source), then scroll to the very bottom of the document. At the bottom, you'll find comments that show Quick Cache stats and information. You should also notice that page-to-page navigation is lightning fast compared to what you experienced prior to installing Quick Cache.

What is the down side to running Quick Cache?

There is NOT one! Quick Cache is a MUST HAVE for every WordPress® powered site. In fact, we really can't think of any site running WordPress® that would want to be without it. To put it another way, the WordPress® software itself comes with a built in action reference for an advanced-cache.php file, because WordPress® developers realize the importance of such as plugin. The /wp-content/advanced-cache.php file is named as such, because the WordPress® developers expect it to be there when caching is enabled by a plugin. If you don't have the /wp-content/advanced-cache.php file yet, it is because you have not enabled Quick Cache from the options panel yet.

So why does WordPress® need to be cached?

To understand how Quick Cache works, first you have to understand what a cached file is, and why it is absolutely necessary for your site and every visitor that comes to it. WordPress® (by its very definition) is a database-driven publishing platform. That means you have all these great tools on the back-end of your site to work with, but it also means that every time a Post/Page/Category is accessed on your site, dozens of connections to the database have to be made, and literally thousands of PHP routines run in harmony behind-the-scenes to make everything jive. The problem is, for every request that a browser sends to your site, all of these routines and connections have to be made (yes, every single time). Geesh, what a waste of processing power, memory, and other system resources. After all, most of the content on your site remains the same for at least a few minutes at a time. If you've been using WordPress® for very long, you've probably noticed that (on average) your site does not load up as fast as other sites on the web. Now you know why!

In computer science, a cache (pronounced /kash/) is a collection of data duplicating original values stored elsewhere or computed earlier, where the original data is expensive to fetch (owing to longer access time) or to compute, compared to the cost of reading the cache. In other words, a cache is a temporary storage area where frequently accessed data can be stored for rapid access. Once the data is stored in the cache, it can be used in the future by accessing the cached copy rather than re-fetching or recomputing the original data.

Where & why are the cache files stored on my server?

The cache files are stored in a special directory: /wp-content/cache/quick-cache. This directory needs to remain writable, just like the /wp-content/uploads directory on many WordPress® installations. The /quick-cache/cache directory is where cache files reside. These files are stored using an intutive directory structure that named based on the request URL (HTTPS/HTTP_HOST/REQUEST_URI). See also: Dashboard -› Quick Cache -› Cache Directory/Expiration Time for further details.

Whenever a request comes in from someone on the web, Quick Cache checks to see if it can serve a cached file; e.g. it looks at the HTTPS/HTTP_HOST/REQUEST_URI environent variables, then it checks the /quick-cache/cache directory. If a cache file has been built already, and it matches an existing HTTPS.HTTP_HOST.REQUEST_URI combination; and it is not too old (see: Dashboard -› Quick Cache -› Cache Directory/Expiration Time), then it will serve that file instead of asking WordPress® to regenerate it. This adds tremendous speed to your site and reduces server load.

If you have GZIP compression enabled, then the cache file is also sent to the browser with compression (recommended). Modern web browsers that support this technique will definitely take advantage of it. After all, if it is easier to email a zip file, it's also easier to download a web page that way. That is why on-the-fly GZIP compression for web pages is recommended. This is supported by all modern browsers.

If you want to enable GZIP, create an .htaccess file in your WordPress® installation directory and put the following few lines in it. Alternatively, if you already have an .htaccess file, just add these lines to it, and that is all there is to it. GZIP is now enabled!

<IfModule deflate_module>
    <IfModule filter_module>
        AddOutputFilterByType DEFLATE text/plain text/html
        AddOutputFilterByType DEFLATE text/xml application/xml application/xhtml+xml application/xml-dtd
        AddOutputFilterByType DEFLATE application/rdf+xml application/rss+xml application/atom+xml image/svg+xml
        AddOutputFilterByType DEFLATE text/css text/javascript application/javascript application/x-javascript
        AddOutputFilterByType DEFLATE font/otf font/opentype application/font-otf application/x-font-otf
        AddOutputFilterByType DEFLATE font/ttf font/truetype application/font-ttf application/x-font-ttf
    </IfModule>
</IfModule>

If your installation of Apache does not have mod_deflate installed. You can also enable GZIP compression using PHP configuration alone. In your php.ini file, you can simply add the following line anywhere: zlib.output_compression = on

What happens if a user logs in? Are cache files used then?

By default, Quick Cache does NOT serve cached pages to users who are logged in, or to users who have left comments recently. Quick Cache also excludes administrative pages, login pages, POST/PUT/DELETE/GET(w/ query string) requests and/or CLI processes. That being said, the Pro version of Quick Cache DOES make it possible to cache pages even when users ARE logged-in; adding even more speed! This is particularly helpful on membership sites; e.g. sites that run plugins like s2Member™ for instance.

Will comments and other dynamic parts of my blog update immediately?

It depends on your configuration of Quick Cache. There is an automatic expiration system (the garbage collector), which runs through WordPress® behind-the-scene, according to your Expiration setting (see: Dashboard -› Quick Cache -› Cache Directory/Expiration Time). There is also a built-in expiration time on existing files that is checked before any cache file is served up, which also uses your Expiration setting. In addition; whenever you update a Post or a Page, Quick Cache can automatically prune that particular file from the cache so it instantly becomes fresh again. Otherwise, your visitors would need to wait for the previous cached version to expire.

By default, Quick Cache does NOT serve cached pages to users who are logged in, or to users who have left comments recently. Quick Cache also excludes administrative pages, login pages, POST/PUT/DELETE/GET(w/ query string) requests and/or CLI processes.

How do I enable GZIP compression? Is GZIP supported?

There is no need to use an .htaccess file with this plugin; caching is handled by WordPress®/PHP alone. That being said, if you also want to take advantage of GZIP compression (and we do recommend this), then you WILL need an .htaccess file to accomplish that part. This plugin fully supports GZIP compression on its output. However, it does not handle GZIP compression directly. We purposely left GZIP compression out of this plugin, because GZIP compression is something that should really be enabled at the Apache level or inside your php.ini file. GZIP compression can be used for things like JavaScript and CSS files as well, so why bother turning it on for only WordPress-generated pages when you can enable GZIP at the server level and cover all the bases!

If you want to enable GZIP, create an .htaccess file in your WordPress® installation directory and put the following few lines in it. Alternatively, if you already have an .htaccess file, just add these lines to it, and that is all there is to it. GZIP is now enabled!

<IfModule deflate_module>
    <IfModule filter_module>
        AddOutputFilterByType DEFLATE text/plain text/html
        AddOutputFilterByType DEFLATE text/xml application/xml application/xhtml+xml application/xml-dtd
        AddOutputFilterByType DEFLATE application/rdf+xml application/rss+xml application/atom+xml image/svg+xml
        AddOutputFilterByType DEFLATE text/css text/javascript application/javascript application/x-javascript
        AddOutputFilterByType DEFLATE font/otf font/opentype application/font-otf application/x-font-otf
        AddOutputFilterByType DEFLATE font/ttf font/truetype application/font-ttf application/x-font-ttf
    </IfModule>
</IfModule>

If your installation of Apache does not have mod_deflate installed. You can also enable gzip compression using PHP configuration alone. In your php.ini file, you can simply add the following line anywhere: zlib.output_compression = on

I'm a plugin developer. How can I prevent certain files from being cached?

<?php
define('QUICK_CACHE_ALLOWED', FALSE); // The easiest way.
// or $_SERVER['QUICK_CACHE_ALLOWED'] = FALSE; // Also very easy.
// or define('DONOTCACHEPAGE', TRUE); // For compatibility with other cache plugins.

When your script finishes execution, Quick Cache will know that it should NOT cache that particular page. It does not matter where or when you define this Constant; e.g. define('QUICK_CACHE_ALLOWED', FALSE); because Quick Cache is the last thing to run during execution. So as long as you define this Constant at some point in your routines, everything will be fine.

Quick Cache also provides support for define('DONOTCACHEPAGE', TRUE), which is used by the WP Super Cache plugin as well. Another option is: $_SERVER['QUICK_CACHE_ALLOWED'] = FALSE. The $_SERVER array method is useful if you need to disable caching at the Apache level using mod_rewrite. The $_SERVER array is filled with all environment variables, so if you use mod_rewrite to set the QUICK_CACHE_ALLOWED environment variable, that will end up in $_SERVER['QUICK_CACHE_ALLOWED']. All of these methods have the same end result, so it's up to you which one you'd like to use.

What should my expiration setting be?

If you don't update your site much, you could set this to 6 months; optimizing everything even further. The longer the cache expiration time is, the greater your performance gain. Alternatively, the shorter the expiration time, the fresher everything will remain on your site. A default value of 7 days (recommended expiration time), is a good conservative middle-ground.

Keep in mind that your expiration setting is only one part of the big picture. Quick Cache will also purge the cache automatically as changes are made to the site (i.e. you edit a post, someone comments on a post, you change your theme, you add a new navigation menu item, etc., etc.). Thus, your expiration time is really just a fallback; e.g. the maximum amount of time that a cache file could ever possibly live.

That being said, you could set this to just 60 seconds and you would still see huge differences in speed and performance. If you're just starting out with Quick Cache (perhaps a bit nervous about old cache files being served to your visitors); you could set this to something like 30 minutes and experiment with it while you build confidence in Quick Cache. It's not necessary, but many site owners have reported this makes them feel like they're more-in-control when the cache has a short expiration time. All-in-all, it's a matter of preference :-)

EMERGENCY: If all else fails, how can I remove Quick Cache?

Ordinarily you can just deactivate Quick Cache from the plugins menu in WordPress. However, if you're having a more serious issue, please follow the instructions here.

  1. Log into your site via FTP; perhaps using FileZilla.
  2. Delete this file: /wp-content/advanced-cache.php
  3. Delete this directory: /wp-content/plugins/quick-cache/
  4. Remove this line from your /wp-config.php file: define('WP_CACHE', TRUE);

Quick Cache is now completely uninstalled and you can start fresh :-)

So Why Does WordPress® Need To Be Cached?

To understand how Quick Cache works, first you have to understand what a cached file is, and why it is absolutely necessary for your site and every visitor that comes to it. WordPress® (by its very definition) is a database-driven publishing platform. That means you have all these great tools on the back-end of your site to work with, but it also means that every time a Post/Page/Category is accessed on your site, dozens of connections to the database have to be made, and literally thousands of PHP routines run in harmony behind-the-scenes to make everything jive. The problem is, for every request that a browser sends to your site, all of these routines and connections have to be made (yes, every single time). Geesh, what a waste of processing power, memory, and other system resources. After all, most of the content on your site remains the same for at least a few minutes at a time. If you've been using WordPress® for very long, you've probably noticed that (on average) your site does not load up as fast as other sites on the web. Now you know why!

The Definition Of A Cached File (from the Wikipedia)

In computer science, a cache (pronounced /kash/) is a collection of data duplicating original values stored elsewhere or computed earlier, where the original data is expensive to fetch (owing to longer access time) or to compute, compared to the cost of reading the cache. In other words, a cache is a temporary storage area where frequently accessed data can be stored for rapid access. Once the data is stored in the cache, it can be used in the future by accessing the cached copy rather than re-fetching or recomputing the original data.

Prepare To Be Amazed / It's Time To Speed Things Up

Quick Cache is extremely reliable, because it runs completely in PHP code, and does not hand important decisions off to the mod_rewrite engine or browser cache; also making Quick Cache MUCH easier to setup and configure.

In addition, Quick Cache actually sends a no-cache header (yes, a no-cache header); which allows it to remain in control at all times. It might seem weird that a caching plugin would send a no-cache header :-). Well, no-cache headers are a key component in this plugin, and they will NOT affect performance negatively. On the contrary, this is how the system can accurately serve cache files to public users vs. users who are logged-in, commenters, etc.

If you care about the speed of your site, Quick Cache is one of those plugins that you absolutely MUST have installed :-) Quick Cache takes a real-time snapshot (building a cache) of every Page, Post, Category, Link, etc. These snapshots are then stored (cached) intuitively, so they can be referenced later, in order to save all of that processing time that has been dragging your site down and costing you money.

The Quick Cache plugin uses configuration options that you select from the options panel. See: Quick Cache -› Options in your Dashboard. Once a file has been cached, Quick Cache uses advanced techniques that allow it to recognize when it should and should not serve a cached version of the file. By default, Quick Cache does not serve cached pages to users who are logged in, or to users who have left comments recently. Quick Cache also excludes administrative pages, login pages, POST/PUT/DELETE/GET(w/ query string) requests and/or CLI processes.

Running Quick Cache On A WordPress® Multisite Installation

WordPress® Multisite Networking is a special consideration in WordPress®. If Quick Cache is installed under a Multisite Network installation, it will be enabled for ALL blogs the same way. The centralized config options for Quick Cache, can only be modified by a Super Administrator operating on the main site. Quick Cache has internal processing routines that prevent configuration changes, including menu displays; for anyone other than a Super Administrator operating on the main site.

How To Enable GZIP Compression for Even Greater Speeds

You don't have to use an .htaccess file to enjoy the performance enhancements provided by this plugin; caching is handled by WordPress®/PHP alone. That being said, if you want to take advantage of GZIP compression (and we do recommend this), then you WILL need an .htaccess file to accomplish that part. This plugin fully supports GZIP compression on its output. However, it does not handle GZIP compression directly. We purposely left GZIP compression out of this plugin, because GZIP compression is something that should really be enabled at the Apache level or inside your php.ini file. GZIP compression can be used for things like JavaScript and CSS files as well, so why bother turning it on for only WordPress-generated pages when you can enable GZIP at the server level and cover all the bases!

If you want to enable GZIP, create an .htaccess file in your WordPress® installation directory and put the following few lines in it. Alternatively, if you already have an .htaccess file, just add these lines to it, and that is all there is to it. GZIP is now enabled!

<IfModule deflate_module>
    <IfModule filter_module>
        AddOutputFilterByType DEFLATE text/plain text/html
        AddOutputFilterByType DEFLATE text/xml application/xml application/xhtml+xml application/xml-dtd
        AddOutputFilterByType DEFLATE application/rdf+xml application/rss+xml application/atom+xml image/svg+xml
        AddOutputFilterByType DEFLATE text/css text/javascript application/javascript application/x-javascript
        AddOutputFilterByType DEFLATE font/otf font/opentype application/font-otf application/x-font-otf
        AddOutputFilterByType DEFLATE font/ttf font/truetype application/font-ttf application/x-font-ttf
    </IfModule>
</IfModule>

If your installation of Apache does not have mod_deflate installed. You can also enable GZIP compression using PHP configuration alone. In your php.ini file, you can simply add the following line anywhere: zlib.output_compression = on

EMERGENCY: If All Else Fails (How-To Remove Quick Cache)

Ordinarily you can just deactivate Quick Cache from the plugins menu in WordPress. However, if you're having a more serious issue, please follow the instructions here.

  1. Log into your site via FTP; perhaps using FileZilla.
  2. Delete this file: /wp-content/advanced-cache.php
  3. Delete this directory: /wp-content/plugins/quick-cache/
  4. Remove this line from your /wp-config.php file: define('WP_CACHE', TRUE);

Quick Cache is now completely uninstalled and you can start fresh :-)

Quick Cache Pro Features

  • The ability to cache logged-in users too! (VERY powerful, particularly for membership sites).
  • A new improved "Clear Cache" button in the admin bar (along with an option to enable/disable this feature).
  • The ability to disable Dashboard notifications related to automatic clearing/purging on change detections.
  • The ability to clear Markdown-related cache files generated by the s2Clean theme for WordPress (if installed).
  • Import/Export functionality for Quick Cache configuration files.
  • URI exclusion patterns (now supporting wildcards too).
  • User-Agent exclusion patterns (now supporting wildcards too).
  • HTTP referrer exclusion patterns (now supporting wildcards too).
  • A Dynamic Version Salt (customize the caching engine).
  • HTML Compressor to automatically combine and compresses CSS/JS/HTML code.
  • Auto-Cache Engine to pre-cache your site at 15-minute intervals.
  • An Automatic Updater to update Quick Cache Pro from your WordPress Dashboard.
  • Rockstar support for all Quick Cache features.

TIP: you can preview Pro features in the free version by clicking the "Preview Pro Features" link at the top of your Quick Cache options.

Copyright: © 2013 WebSharks, Inc. (coded in the USA)

Released under the terms of the GNU General Public License.

Credits / Additional Acknowledgments

v140725

  • Enhancement: Improved overall performance by optimizing the auto-purge routines. See also: #130
  • Enhancement: The "GET Requests" UI Panel now explains that you can use ?qcAC=0 to disable caching when you ARE caching GET Requests. See also: #210.
  • New Pro Feature: Auto-Purge XML Sitemaps. If you're generating XML Sitemaps with a plugin like Google XML Sitemaps, you can now tell Quick Cache to automatically purge any cached sitemap files whenever it purges a Post/Page cache. You may also specify a list of XML Sitemap patterns to clear, if you have multiple sitemap files. See also: #169
  • Enhancement (Pro): The Quick Cache Pro Updater now accepts a License Key in place of the WebSharks password.
  • Enhancement (Pro): In a Multisite Network, the Auto-Cache Engine will now also auto-cache each child blog. See also: #169
  • Bug Fix: Fixed a bug that was causing unapproved, spam, and trash comments to unnecessarily purge the cache. See also: #159
  • Bug Fix: A custom WP_CONTENT_DIR is now obeyed in the scenario where it's set to a path outside of ABSPATH. See also: #95
  • Bug Fix: The UI now correctly displays custom WP_CONTENT_DIR in the "Directory/Expiration Time" options panel. See also: #206
  • Bug Fix: Quick Cache LITE now correctly sets the QUICK_CACHE_PRO constant to false. See also: #229
  • Bug Fix: Workaround for broken page navigation on the front page of some sites. This is a WordPress redirect_canonical() bug workaround. See also: #209
  • Bug Fix (Pro): 404 Caching now properly returns a 404 HTTP Status code when serving a cached 404 page. See also: #197
  • Bug Fix (Pro): The HTML Compressor now properly preserves %#%{%#%%#%}%#% character whitespace during CSS compression. See also: #25
  • Bug Fix (Pro): The Pro Updater upgrade link now points to the correction location when displayed from a Child Blog in a Multisite Network. See also: #205
  • Bug Fix (Pro): The Auto-Cache Engine now correctly handles the sitemap when home_url() differs from site_url().
  • Bug Fix (Pro): The "Dynamic Version Salt" options panel now correctly displays the last saved value. See also: #231

v140605

  • 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 https://github.com/WebSharks/Quick-Cache/issues/97
  • Enhancement: Added a postload filter for status_header so that Quick Cache can properly detect calls to the WP core function status_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 the wp-content/cache/ directory. See https://github.com/WebSharks/Quick-Cache/issues/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 https://github.com/WebSharks/quick-cache/issues/164
  • Bug Fix: Obey custom content directories. If you have customized your WP_CONTENT_DIR and WP_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 https://github.com/WebSharks/Quick-Cache/issues/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 https://github.com/WebSharks/Quick-Cache/issues/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 status publish and private and when transitioning from publish or private post status to draft, future, or private. See https://github.com/WebSharks/Quick-Cache/issues/43
  • Bug Fix: Split/paginated comments and multi-page Posts/Page cache files are now purged properly when the post cache is purged. See https://github.com/WebSharks/Quick-Cache/issues/75

v140104

  • 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: https://github.com/WebSharks/Quick-Cache/issues/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: https://github.com/WebSharks/Quick-Cache/issues/21

v131224

  • 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: https://github.com/WebSharks/Quick-Cache/issues/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 the xmlrpc 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: https://github.com/WebSharks/Quick-Cache/issues/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: https://github.com/WebSharks/Quick-Cache/issues/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: https://github.com/WebSharks/Quick-Cache/issues/48
  • Multisite Bug Fix. Clearing the cache on a Multisite Network configured to use sub-directories now works properly. See: https://github.com/WebSharks/Quick-Cache/issues/39
  • Multisite Bug Fix. Fixed unmatched closing parenthesis in regex. See: https://github.com/WebSharks/Quick-Cache/issues/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.

v131206

  • New Pro Feature. It's now possible for developers to add custom PHP code to the cache clearing routines (e.g. custom code which might consider things like APC or memcache also). This requires Quick Cache Pro. Please check your Dashboard under: Quick Cache Pro -› Clearing the Cache. See also: this screenshot.
  • Multisite Bug Fix. Unable to clear the cache when running sub-directories. See: https://github.com/WebSharks/Quick-Cache/issues/30
  • Multisite Bug Fix. The "Clear Cache" button was not displayed for child blogs in a network. Fixed in this release.

v131205

  • Added hook to wp_set_comment_status to purge the comment cache when a comment status changes.
  • Ignore set_time_limit() errors in case function is disabled in PHP configuration. This is a temporary fix and will be handled more appropriately in a future maintenance release. See also: https://github.com/WebSharks/Quick-Cache/issues/20
  • Added Raam Dev to the contributors list. Raam will now be leading the development of Quick Cache and Quick Cache Pro.

v131128

  • New Plugin Architecture for Quick Cache. This release introduces a new way for theme/plugin developers to modify the way Quick Cache operates at the advanced-cache.php level (e.g. very early-on). For further details on this, please check your Dashboard under: Quick Cache -› Theme/Plugin Developers. See also: https://github.com/WebSharks/Quick-Cache/issues/17
  • Compatibility. This release further improves PHP v5.3 detection. Quick Cache will now generate an administrative notice instead of a PHP exception; allowing the plugin to be activated, but without actually loading the plugin under this scenario. A notice to the site owner is helpful in cases where the plugin is NOT being updated through the Dashboard. This will remove the risk of crashing a site that's attempting to run Quick Cache w/o PHP v5.3+ installed. See also: https://github.com/WebSharks/Quick-Cache/issues/13

v131127

v131121

  • Updated to support all features and functionality of WordPress v3.7+ (this new release of Quick Cache requires WordPress v3.7+). The Quick Cache plugin is now being actively maintained and future updates and improvements will be released periodically by lead developer Jason Caldwell. The popularity of this plugin and recent acknowldegments at WordCamp in Boston have inspired Jason to revamp Quick Cache!
  • The latest version of Quick Cache is a complete rewrite (OOP design). Faster! and even more dependable. NOTE: the free version of Quick Cache (this new LITE version); while it remains fully functional and is more-than-adequate for most sites; is now limited in some ways. The following advanced features from the previous release are no longer available in the lite version: a custom MD5 Version Salt; custom Exclusion Patterns; the Clear Cache button in the admin bar. These, and MANY other brand new features are now available only in the pro version of the plugin. For further details, please see: http://www.websharks-inc.com/product/quick-cache/.
  • Bug fix. Quick Cache now considers the HTTPS evironment variable in order to prevent cache collisions on sites that serve pages over SSL. Nothing to configure, this is now built into the Quick Cache engine.
  • UI updates. An improved user interface makes configuring this plugin a dream! Quick Cache got an awesome makeover in this release.
  • Improved support for multisite networks. It's never been easier to run Quick Cache on a multisite network. For further details, please see: Dashboard -› Network Admin -› Quick Cache when/if you have Multisite Networking enabled in WordPress.
  • Update; PUT and DELETE requests are now considered by Quick Cache. By default, Quick Cache does NOT serve cached pages to users who are logged in, or to users who have left comments recently. Quick Cache also excludes administrative pages, login pages, POST/PUT/DELETE/GET(w/ query string) requests and/or CLI processes.
  • Dropping support for ob_gzhandler(); and the like. Quick Cache will now throw PHP exceptions to warn you about this should it be an issue in your hosting environment. If you want to enable GZIP, please follow the instructions provided by Quick Cache and avoid the use of ob_gzhandler() as this is not a recommended way to enable GZIP on any hosting platform.
  • Truly atomic cache file write updates. Removing support for SEM vs. FLOCK for file locking. Quick Cache no longer needs a mutex file. Cache file updates are written to a temp file and renamed for the best reliability and improved speed too!
  • Localization. Quick Cache is now translatable. This release adds support for gettext translations, a very popular method for translating WordPress plugins. All parts of the Quick Cache plugin can be localized now. The source code was updated with calls to the __ function and a new text domain was added: quick-cache. PO translation files should be placed in your plugins directory, example: /wp-content/plugins/quick-cache-en_US.mo; or in WP_LANG_DIR/plugins/quick-cache-en_US.mo.
  • Capability requirement. This release of Quick Cache requires that an Administrator be logged-in with the Capability of activate_plugins. This is a default Capability that comes with the Administrator Role in WordPress. So, unless you've modified your WordPress Roles/Capabilities in some extremely creative way, this should not impact you; just something to be aware of.
  • (Pro Version) There is now a pro version of this plugin available. Please see: http://www.websharks-inc.com/product/quick-cache/. The initial set of pro features include: the ability to cache logged-in users too! (VERY powerful, particularly for membership sites); a new improved "Clear Cache" button in the admin bar (along with an option to enable/disable this feature); the ability to disable Dashboard notifications related to automatic clearing/purging on change detections; Import/Export functionality for Quick Cache configuration files; URI exclusion patterns (now supporting wildcards too); User-Agent exclusion patterns (now supporting wildcards too); HTTP referrer exclusion patterns (now supporting wildcards too); an MD5 Version Salt; and rockstar support for all Quick Cache features.
  • (Pro Version) Regarding URI/User-Agent/HTTP Referrer exclusion patterns. If you configured any of these options in the previous release and would like to continue to use them in this release, please upgrade to the pro version or contact lead developer Jason Caldwell for assistance. Note: if you had these options configured in the previous release, once you upgrade to the pro version they will come back just like they were. Either that, or you may choose to continue using the previous version of Quick Cache where this functionality still exists.
  • Lite version source code now available on GitHub also: https://github.com/WebSharks/Quick-Cache.

v111203

  • Updated to support WordPress® v3.3. Backward compatibily remains for WordPress® v3.2.x.

v110720

  • Bug fix. Corrected XSS security issue associated with the handling of $_SERVER["REQUEST_URI"] inside the comment lines that Quick Cache introduces at the bottom of the source code.
  • Bug fix. Corrected cosmetic issue in WordPress v3.2 related to the positioning of the Clear Cache button.

v110709

  • Routine maintenance. No signifigant changes.

v110708

  • Routine maintenance. No signifigant changes.
  • Compatibility with WordPress v3.2.

v110523

  • Versioning. Starting with this release, versions will follow this format: yymmdd. The version for this release is: 110523.
  • Routine maintenance. No signifigant changes.

v2.3.6

  • Routine maintenance. No signifigant changes.

v2.3.5

  • Bug fix. Under the right scenario, errors regarding the function is_user_logged_in() in the second phase of advanced-cache.php have been resolved in this release of Quick Cache.
  • Compatibility. Quick Cache is now capable of dealing with themes/plugins that attempt to use ob_start("ob_gzhandler") inside a header.php file, or in other places that may create a problem in the nesting order of output buffers. For instance, this release of Quick Cache resolves some incompatiblities with Headway themes for WordPress®. Please note that GZIP should be enabled at the Apache level ( i.e. with an .htaccess file ), or in PHP using zlib.output_compression = on. Both of these methods are preferred over ob_start("ob_gzhandler"). If you must use ob_start("ob_gzhandler"), please make this declaration inside your /wp-config.php file, and NOT inside /header.php, as this creates a problem that Quick Cache must work around, and could ultimately prevent GZIP from working at all if you do it this way. For further details on how to enable GZIP with Quick Cache, please see the included /readme.txt file.

v2.3.2

  • Compatiblity. References to dirname() that were processed by the Quick Cache /advanced-cache.php handler should have been using WP_CONTENT_DIR for improved compatibility with WordPress® installations that may use non-standardized installation directories and/or symlinks.
  • New Filter available for developers. Multisite Super Admins can now give their Child Blog owners the ability to manually clear the cache for their own site in the Network. Quick Cache accomplishes this by making the "Clear Cache" button visible in the administrative header for Child Blog owners. If you wish to enable this, you can use this Filter: add_filter("ws_plugin__qcache_ms_user_can_see_admin_header_controls", "__return_true");. This button is always visible to Super Admins. Adding this Filter makes it visible to all child Blog Owners as well.

v2.3.1

  • Framework updated; general cleanup.
  • Optimizations. Further internal optimizations applied through configuration checksums that allow Quick Cache to load with even less overhead now.
  • Bug fix. Quick Cache was suffering from a bug regression related to stale Last-Modified headers being sent with cached copies. This has been resolved in Quick Cache v2.3.1+.

v2.3

  • Framework updated; general cleanup.
  • Updated with static class methods. Quick Cache now uses PHP's SPL autoload functionality to further optimize all of its routines.

v2.2.8

  • Framework updated; general cleanup.
  • Updated for compatibility with WordPress® 3.1.

v2.2.7

  • Framework updated. General cleanup.

v2.2.6

  • Updated to disable caching on database failures that do not trigger a 5xx error code. Quick Cache is now capable of disabling the cache engine dynamically on all database connection failures within WordPress®.

v2.2.5

  • Updated to support all 5xx error codes. Quick Cache now monitors the status_header function for 5xx error codes. If a 5xx status header is detected, caching is automatically disabled, as it should be.

v2.2.3

  • Framework updated. General cleanup.

v2.2.2

  • Minor updates to the Ajax clearing routines that were implemented in v2.2.1.
  • This update also adds compatibility with (offline) localhost installations of WordPress® (WAMP/MAMP).

v2.2.1

  • Support for glob() has been added to Quick Cache. In previous versions, it was impossible to pinpoint a specific cache file through Dynamic Pruning routines ( at least, not with 100% accuracy ). This was because an MD5 Version Salt could have been generated; based on arbitrary conditionals, set by the site owner. Quick Cache now stores its cache files with three MD5 hash strings, producing longer file names; but with the added benefit of improved Multisite compatibility, and improvements in optimization overall. Quick Cache can now handle dynamic pruning with 100% accuracy. Even supporting complex Multisite installations, with or without SUBDOMAIN_INSTALL.
  • New feature. Quick Cache now integrates a Clear Quick Cache button into the WordPress® Dashboard. This makes it easy to force a "cache reset, via ajax", without having to navigate through the Quick Cache menu for this simple task. Another great benefit to this new button, is that it works in all Dashboard views, even in a Multisite installation across different backends. If you're running a Multisite installation, you can use this new button to clear the cache for a particular site/blog in your network, without interrupting others.
  • Bug fix. The Constant QUICK_CACHE_ALLOWED was being defined too early in the buffering routine. This has been resolved in v2.2.1.
  • Optimization of advanced-cache.php. A few things have been streamlined even further.
  • Added compatibility for the WP Maintenance Mode plugin, and also the Maintenance Mode plugin. Quick Cache will disable itself when these plugins are enabled for maintenance.
  • Added compatibility for other Maintenance Mode plugins that are capable of sending a Status: 503 header, or a Retry-After: header.
  • Added compatibility for plugins that create PHP sessions. Quick Cache will automatically disable itself when a PHP session is active.
  • Added compatiblity for web hosts that insert a port number into the $_SERVER["HTTP_HOST"] variable. Quick Cache is now capable of handling this gracefully.
  • Improvement. Removed references to $blog_id = 1 in favor of is_main_site(); providing support for Multisite Mode, where there are multiple sites, instead of just multiple blogs.
  • Updated Dynamic Pruning Hooks for Custom Post Types, and Custom Taxonomies in WordPress® 3.0+.
  • Extended compatiblity for Quick Cache on SSL enabled blogs.

v2.1.9

  • Framework updated; general cleanup.
  • Updated minimum requirements to WordPress® 3.0.

v2.1.8

  • Framework updated to WS-P-3.0.

v2.1.7

  • Bug fix. A bug related to gzinflate variations handled by the WP_Http class has been resolved. This was preventing Quick Cache from validating a custom MD5 Version Salt on some servers.
  • Framework updated to WS-P-2.3.

v2.1.6

  • Auto-Cache Engine. References to ws_plugin__qcache_curl_get(), have been replaced by c_ws_plugin__qcache_utils_urls::remote(), which makes use of wp_remote_request() through the WP_Http class. This removes an absolute dependency on the cURL extension for PHP. This also gives Quick Cache/WordPress® the ability to decide with method of communication to use for HTTP requests; based on what the installation server has available. Note: this only affects the Auto-Cache Engine for Quick Cache, which is completely optional.
  • Compatibility. Quick Cache is now smarter about the way it reports errors. For example, when/if there are directory permission issues with your wp-content directory; Quick Cache can help with this, in a more intuitive fashion.
  • Compatibility. Support has been added for WordPress® 3.0 with Multisite/Networking enabled.
  • Updated minimum requirements to WordPress® 2.9.2.
  • Framework updated to WS-P-2.2.

v2.1.5

  • A new option for Dynamic Cache Pruning was added. You can now choose Single + Front Page. This makes it possible to Create or Edit a Post/Page, and have the cache automatically updated for that specific Post/Page. And.. in addition, your Front Page ( aka: Home Page ) will also be refreshed at the same time.
  • A minor bug was fixed in the Dynamic Cache Pruning routines. This bug was originally introduced in Quick Cache v2.1.1, and has now been corrected in v2.1.5. This bug, under certain circumstances, was preventing Quick Cache from locating an expired md5 cache file, for some Posts/Pages being updated.
  • Advanced feature addition. Quick Cache now comes bundled with a robust Auto-Cache Engine. This is an optional feature, for VERY advanced users. You'll find the new Auto-Cache Engine listed right along with all of the other Quick Cache options. This works in conjunction with an XML Sitemap.

v2.1.4

  • Advanced feature addition. You can now prevent caching dynamically whenever pages on your site receive traffic from specific URLs, specific domains, or even specific word fragments found within the HTTP_REFERER. This feature is very advanced, and will NOT impact your site unless you decide to use it for one reason or another.

v2.1.3

  • Added De-Activation Safeguards to the Quick Cache options panel.
  • Updated the Quick Cache options panel. It's been given a make-over.
  • Stable tag updated in support of tagged releases within the repository at WordPress.org.

v2.1.2

  • WebSharks Framework for Plugins has been updated to P-2.1.
  • Updated caching routines in support of hosting providers running with CGI/FastCGI. Quick Cache has been tested with VPS.net, HostGator, BlueHost, (mt) Media Temple (gs) and (dv), The Rackspace Cloud, and several dedicated servers ( including some Amazon EC2 instances ) running with Apache; including support for both mod_php and also CGI/FastCGI implementations. Quick Cache should work fine with any Apache/PHP combination. Please report all bugs through the Support Forum.
  • An issue was discovered with WordPress® MU /files/ being accessed through htaccess/mod_rewrite. Quick Cache has been updated to exclude all /files/ served under WordPress® MU, which is the way it should be. Requests that contain /files/ are a reference to WordPress® Media, and there is no reason, to cache, or send no-cache headers, for Media. Quick Cache now ignores all references to /files/ under WordPress® MU. This problem was not affecting all installations of WPMU, because there already are/were scans in place for Content-Type headers. However, under some CGI/FastCGI implementations, this was not getting picked on WMPU with mod_rewrite rules. This has been resolved in v2.1.2.

v2.1.1

  • A WPMU bug was corrected in Quick Cache v2.1.1. This bug was related to HTTP_HOST detection under WordPress® MU installations that were using sub-domains. Please thank QuickSander for reporting this important issue.

v2.1

  • Quick Cache has added further support for themes and plugins that dynamically set Content-Type headers through PHP routines. Quick Cache is now smart enough to automatically disable itself whenever a theme or plugin sends a Content-Type header that would be incompatible with Quick Cache. In other words, any Content-Type header that is not a variation of HTML, XHTML or XML.
  • Quick Cache has also been upgraded to support the preservation of scripted headers sent by PHP routines. If a plugin or theme sends scripted headers ( using the header() function in PHP ), those headers will be preserved. They'll be stored along with the cache. This allows them to be sent back to the browser whenever a cached version is served on subsequent visits to the original file.
  • Compatability checked against WordPress.org 2.9.1, 2.9.2 & WordPress MU 2.9.1, 2.9.2. Everything looks good. No changes required.

v2.0

  • A few tweaks to the options panel.
  • Documentation updated, several small improvements in error reporting.
  • Additional error checking to support an even wider range of hosting providers.
  • Added automation routines for safe re-activation after an upgrade is performed.

v1.9

  • Additional support added for WordPress® MU 2.8.6+.
  • Security file quick-cache-mu.php added specifically for MU installations. WordPress® MU is a special ( multi-user ) version of WordPress®. If you're running WordPress® MU, check the [readme.txt] file for WordPress® MU notations.

v1.8

  • Re-organized core framework. Updated to: P-2.0.
  • Updated to support WP 2.9+.

v1.7

  • Updated documentation. Added some additional code samples.
  • Tested with WP 2.8.5. Everything ok.

v1.6

  • We've added the ability to enable Double-Caching ( client-side caching ). Full documentation is provided in the Quick Cache options panel. This feature is for those of you who just want blazing fast speed and are not concerned as much about reliability and control. We don't recommend turning this on unless you realize what you're doing.

v1.5

  • Support for Dynamic Cache Pruning has been improved. Full documentation is provided in the Quick Cache options panel.
  • Additional feature-specific documentation has been added to assist novice webmasters during configuration.

v1.4

  • Garbage collection has been further optimized for speed and performance on extremely high traffic sites.
  • PHP Ternary expressions are now supported in your Version Salt. This takes your Version Salt to a whole new level.
  • Additional code samples have been provided for Version Salts; showing you how to deal with mobile devices and other tricky situations.

v1.3

  • We've implemented both Semaphore ( sem_get ) and flock() mutex. If you're on a Cloud Computing Model ( such as the Rackspace® Cloud ), then you'll want to go with flock() unless they tell you otherwise. In all other cases we recommend the use of Semaphores over Flock because it is generally more reliable. The folks over at Rackspace® have suggested the use of flock() because of the way their Cloud handles multi-threading. In either case, flock() will be fully functional in any hosting environment, so it makes a great fallback in case you experience any problems.

v1.2

  • We've implemented a way for plugin developers to disallow caching during certain routines or on specific pages. You can set the following PHP Constant at runtime to disable caching. define("QUICK_CACHE_ALLOWED", false). We have also added backward compatibility for WP Super Cache, so that define("DONOTCACHEPAGE", true) will also be supported by plugins that have previously been written for compatibility with Super Cache. In other words, Quick Cache looks for either of these two Constants.

v1.1

  • Added the ability to create a Version Salt. This is a feature offered ONLY by Quick Cache. Full documentation is provided in the Quick Cache options panel. This can become very useful for sites that provide membership services or have lots and lots of plugins installed that makes their site incompatible with WP Super Cache. With Quick Cache, you'll now have more control over the entire caching process using a custom Version Salt tailored to your specific needs.

v1.0

  • Initial release.