Releasing Quick Cache v140605

quick-cache/includes/advanced-cache.tpl.php

@@ -139,7 +139,7 @@ class advanced_cache # `/wp-content/advanced-cache.php`
 		/**
 		 * Flagged as `TRUE` if QC advanced cache is active & running.
 		 *
-		 * @since 14xxxx Improving output buffers
+		 * @since 140605 Improving output buffers
 		 *
 		 * @var boolean `TRUE` if QC advanced cache is active & running.
 		 */
@@ -239,7 +239,7 @@ class advanced_cache # `/wp-content/advanced-cache.php`
 		/**
 		 * An array of debug info.
 		 *
-		 * @since 14xxxx Improve output buffering.
+		 * @since 140605 Improve output buffering.
 		 *
 		 * @var array An array of debug info; i.e. `reason_code` and `reason` (optional).
 		 */
@@ -270,7 +270,7 @@ class advanced_cache # `/wp-content/advanced-cache.php`
 		/**
 		 * Is the current request a WordPress content type?
 		 *
-		 * @since 14xxxx Improving debug notes display.
+		 * @since 140605 Improving debug notes display.
 		 *
 		 * @var boolean `TRUE` if is a WP content type.
 		 *
@@ -570,7 +570,7 @@ class advanced_cache # `/wp-content/advanced-cache.php`
 		/**
 		 * No-cache because we detected an early buffer termination.
 		 *
-		 * @since 14xxxx Improving output buffer.
+		 * @since 140605 Improving output buffer.
 		 *
 		 * @var string A unique string identifier in the set of `NC_DEBUG_` constants.
 		 */
@@ -620,7 +620,7 @@ public function load_ac_plugins()
 		/**
 		 * Registers a shutdown flag.
 		 *
-		 * @since 14xxxx Improving output buffer.
+		 * @since 140605 Improving output buffer.
 		 *
 		 * @note In `/wp-settings.php`, Quick Cache is loaded before WP registers its own shutdown function.
 		 * Therefore, this flag is set before {@link shutdown_action_hook()} fires, and thus before {@link wp_ob_end_flush_all()}.
@@ -963,7 +963,7 @@ public function output_buffer_callback_handler($buffer, $phase)
 		/**
 		 * Echoes `NC_DEBUG_` info in the WordPress `shutdown` phase (if applicable).
 		 *
-		 * @since 14xxxx Improving debug info output phase.
+		 * @since 140605 Improving debug info output phase.
 		 *
 		 * @attaches-to `shutdown` hook in WordPress w/ a late priority.
 		 */
@@ -1289,7 +1289,7 @@ public function host_token($dashify = FALSE)
 		/**
 		 * Produces a token based on the current site's base directory.
 		 *
-		 * @since 14xxxx First documented version.
+		 * @since 140605 First documented version.
 		 *
 		 * @param boolean $dashify Optional, defaults to a `FALSE` value.
 		 *    If `TRUE`, the token is returned with dashes in place of `[^a-z0-9\/]`.

quick-cache/quick-cache.inc.php

@@ -49,7 +49,7 @@ class plugin
 			 *
 			 * @var string Current version of the software.
 			 */
-			public $version = '140529';
+			public $version = '140605';
 
 			/**
 			 * Plugin text domain for translations.
@@ -101,7 +101,7 @@ class plugin
 			/**
 			 * Cache directory.
 			 *
-			 * @since 14xxxx Moving to a base directory.
+			 * @since 140605 Moving to a base directory.
 			 *
 			 * @var string Cache directory; relative to the configured base directory.
 			 */
@@ -632,7 +632,7 @@ public function all_admin_notices()
 			/**
 			 * Enqueue an administrative notice.
 			 *
-			 * @since 14xxxx Adding enqueue notice/error methods.
+			 * @since 140605 Adding enqueue notice/error methods.
 			 *
 			 * @param string  $notice HTML markup containing the notice itself.
 			 *
@@ -703,7 +703,7 @@ public function all_admin_errors()
 			/**
 			 * Enqueue an administrative error.
 			 *
-			 * @since 14xxxx Adding enqueue notice/error methods.
+			 * @since 140605 Adding enqueue notice/error methods.
 			 *
 			 * @param string  $error HTML markup containing the error itself.
 			 *
@@ -1064,7 +1064,7 @@ public function auto_purge_post_cache($id, $force = FALSE)
 			 *
 			 * @attaches-to `transition_post_status` hook.
 			 *
-			 * @since 14xxxx First documented version.
+			 * @since 140605 First documented version.
 			 *
 			 * @param string   $new_status New post status.
 			 * @param string   $old_status Old post status.
@@ -1225,7 +1225,7 @@ public function auto_purge_posts_page_cache()
 			 *
 			 * @attaches-to `post_updated` hook.
 			 *
-			 * @since 14xxxx First documented version.
+			 * @since 140605 First documented version.
 			 *
 			 * @param integer  $post_ID A WordPress post ID.
 			 * @param \WP_Post $post_after WP_Post object following the update.
@@ -1325,7 +1325,7 @@ public function auto_purge_author_page_cache($post_ID, $post_after, $post_before
 			 * @attaches-to `added_term_relationship` hook.
 			 * @attaches-to `delete_term_relationships` hook.
 			 *
-			 * @since 14XXXX First documented version.
+			 * @since 140605 First documented version.
 			 *
 			 * @param integer $id A WordPress post ID.
 			 * @param bool    $force Defaults to a `FALSE` value.
@@ -1507,7 +1507,7 @@ public function auto_purge_comment_post_cache($id)
 			 * This constructs an absolute server directory path (no trailing slashes);
 			 *    which is always nested into {@link \ABSPATH} and the configured `base_dir` option value.
 			 *
-			 * @since 14xxxx Moving to a base directory structure.
+			 * @since 140605 Moving to a base directory structure.
 			 *
 			 * @param string $rel_dir_file A sub-directory or file; relative location please.
 			 *
@@ -1533,7 +1533,7 @@ public function abspath_to($rel_dir_file)
 			 * This constructs a relative/base directory path (no leading/trailing slashes).
 			 *    Always relative to {@link \ABSPATH}. Depends on the configured `base_dir` option value.
 			 *
-			 * @since 14xxxx Moving to a base directory structure.
+			 * @since 140605 Moving to a base directory structure.
 			 *
 			 * @param string $rel_dir_file A sub-directory or file; relative location please.
 			 *
@@ -2124,7 +2124,7 @@ public function host_token($dashify = FALSE)
 			/**
 			 * Produces a token based on the current site's base directory.
 			 *
-			 * @since 14xxxx First documented version.
+			 * @since 140605 First documented version.
 			 *
 			 * @param boolean $dashify Optional, defaults to a `FALSE` value.
 			 *    If `TRUE`, the token is returned with dashes in place of `[^a-z0-9\/]`.

quick-cache/quick-cache.php

@@ -1,6 +1,6 @@
 <?php
 /*
-Version: 140529
+Version: 140605
 Text Domain: quick-cache
 Plugin Name: Quick Cache
 Network: true

quick-cache/readme.txt

@@ -1,8 +1,8 @@
 === Quick Cache (Speed Without Compromise) ===
 
-Stable tag: 140104
+Stable tag: 140605
 Requires at least: 3.7
-Tested up to: 3.9
+Tested up to: 3.9.1
 Text Domain: quick-cache
 
 License: GPLv2 or later
@@ -29,6 +29,9 @@ The Quick Cache plugin uses configuration options that you select from the optio
 5. Quick Cache Screenshot #5
 6. Quick Cache Screenshot #6
 7. Quick Cache Screenshot #7
+8. Quick Cache Screenshot #8
+9. Quick Cache Screenshot #9
+10. Quick Cache Screenshot #10
 
 == Installation ==
 
@@ -85,9 +88,9 @@ In computer science, a cache (pronounced /kash/) is a collection of data duplica
 
 = Where & why are the cache files stored on my server? =
 
-The cache files are stored in a special directory: `/wp-content/cache/`. This directory needs to remain writable, just like the `/wp-content/uploads` directory on many WordPress® installations. The `/cache` directory is where MD5 hash files reside. These files are named (with an MD5 hash) based on `HTTPS/HTTP_HOST/REQUEST_URI`. See also: **Dashboard -› Quick Cache -› Cache Directory/Expiration Time** for further details.
+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 `/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.
+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.
 
@@ -231,7 +234,9 @@ Quick Cache is now completely uninstalled and you can start fresh :-)
 - 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 (customize the caching engine).
+- 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.
 
@@ -273,6 +278,27 @@ Requires PHP v5.3+. The latest version of Quick Cache is a complete rewrite (OOP
 
 == Changelog ==
 
+= 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>