This ZenCache release candidate includes 3 new features, 7 bug fixes, and 6 enhancements. You can download and try out this release using the link below. Please report bugs and feedback on GitHub.
The two most notable additions to this release include a new Clear Cache Options Menu in the WordPress Admin Bar that allows you to clear the cache for just the Home Page, the Current URL, a Specific URL, PHP's OPCache (if active), or the CDN Cache (when Static CDN Filters are configured).
The other big addition is a brand new section inside the Automatic Cache Clearing panel that allows you to specify a list of Custom URLs that should always be cleared whenever ZenCache clears a Post/Page cache.
Download ZenCache Pro v151105 Release Candidate (you must be logged into your account at ZenCache.com to access this download)
- Deactivate and Delete any existing ZenCache plugin via Dashboard -> Plugins
- Download the release candidate using the link above
- Install the release candidate you downloaded by going to Dashboard -> Plugins -> Add New -> Upload and selecting the downloaded zip file
- Activate ZenCache
Changelog for ZenCache v151105 (Release Candidate)
- New Feature! The Clear Cache button in the Admin Bar now includes a sub-menu with several new options for clearing the cache from anywhere on your site. You can clear the cache for just the Home Page, the Current URL, a Specific URL, PHP's OPCache (if active), or the CDN Cache (when Static CDN Filters are configured). This menu comes in two flavors and can be customized (or disabled entirely) inside ZenCache → Plugin Options → Manual Cache Clearing. Props @jaswsinc. See Issue #596.
- New Feature! It's now possible to specify a list of Custom URLs whose cache files should be cleared whenever you update a Post/Page, approve a Comment, or make other changes where ZenCache detects that a Post/Page cache should be cleared to keep your site up-to-date. See ZenCache → Plugin Options → Automatic Cache Clearing → Misc. Auto-Clear Options → Auto-Clear a List of Custom URLs Too? Props @kristineds. See Issue #111.
- Bug Fix: Fixed a bug with Static CDN Filters and Cross-Origin Resource Sharing (CORS) that was generating a "Cross-Origin Request Blocked" error. ZenCache will now update the root
.htaccessfile to include a
Header set Access-Control-Allow-Origin "*"rule for
jsfiles whenever the Static CDN Filters are enabled. This is necessary to avoid "Cross-Origin Request Blocked" errors. Note that if you are already experiencing this error, you should create and configure a new CDN hostname to resolve the issue. In our tests it appears that some CDNs are caching the initial header response received by the server, which means it's necessary to send the
Access-Control-Allow-Originheader before configuring the Static CDN Filters with a CDN hostname. See Issue #427.
- Bug Fix: Removed
eot,ttf,otf,wofffont extensions from the Static CDN Filter Blacklisted Extensions. These were added in a previous release in an attempt to resolve an issue with Cross-Origin Resource Sharing (CORS), however now that the HTML Compressor has been updated to work with Static CDN Filters, the CSS compressed by the HTML Compressor is now served from the CDN. Fonts are most likely to be referenced by CSS, which is static. So when Static CDN Filters are applied, the CSS is getting moved to the CDN and the fonts are then expected to live on the CDN too. By excluding them from the Static CDN Filter, we were creating a problem instead of solving one. This release removes the font extensions from the default Blacklisted Extensions so that fonts can be hosted on the CDN alongside the CSS that references them. See Issue #427.
- Bug Fix: Fixed a bug related to updating plugins with WP-CLI on a site that was running ZenCache Pro. While ZenCache Pro updates must still be done through the ZenCache Pro Updater inside the Dashboard, updating other plugins via WP-CLI was generating a harmless ZenCache exception: "Invalid argument; host token empty!". With this fix, ZenCache will properly detect when WP-CLI is running to avoid these errors. Props @MarioKnight @renzms. See Issue #563.
- Bug Fix: Fixed a bug where post previews were being cached when Logged-In User Caching and GET Request caching were both enabled (both are disabled by default). This release now detects previews in this scenario and excludes those requests from being cached. Props @clavaque @kristineds. See Issue #583.
- Bug Fix: Fixed an issue where a PHP Notice was generated when an inactive WordPress component was being upgraded. This issue did not have any adverse affect on the site, but this fix resolves the issue so that the notice won't appear in PHP logs. See Issue #589.
- Bug Fix: Fixed a bug where a commented-out
wp-config.php(such as what WP Super Cache leaves behind) was being incorrectly ignored and resulted in caching being silently disabled. Props @davidfavor. See Issue #591.
- Bug Fix: Fixed a bug where in some scenarios a page might not be cached due to a stray
SECURE_AUTH_COOKIEcookie, even when the user is not logged in. Props @jaswsinc @renzms. See Issue #592.
- Enhancement: Excluded several unnecessary files from the plugin zip file that were being used during the build process but were not necessary to run the plugin. Props @bridgeport. See Issue #579.
- Enhancement: When the Cache Directory location is changed, ZenCache now cleans up the old Cache Directory and any old cache files instead of leaving them behind. Props @clavaque @renzms. See Issue #580.
- Enhancement: Added a new API Function that allows a site owner to clear the cache for a specific URL via
zencache::clearUrl($url);. See this article for further details. Props @kristineds. See Issue #590.
- Enhancement: Improved the HTML Notes generated by ZenCache when s2Member (a membership plugin for WordPress) is specifically disabling caching. s2Member automatically disables caching on certain pages that are required to remain dynamic. The HTML Notes generated by ZenCache now explain when this is happening. Props @renzms. See Issue #504.
- Enhancement: In Logged-In User Caching, the "Yes, but DON'T maintain a separate cache for each user" option has been hidden because this particular option has the potential to create a security issue if not configured properly. If you were already using this option, it will not be hidden and it will continue to work. Otherwise, if you require this particular option you can now enable it using a filter (see this comment). Props @renzms @jaswsinc. See Issue #497.
- Enhancement: The Auto-Cache Engine now detects when the configured XML Sitemap is not valid or is unreachable and displays an appropriate notice. Props @kristineds and @jaswsinc. See Issue #555.
Please note that when this version leaves beta and an official release is made, the ZenCache Pro Plugin Updater will automatically detect the new version and ask you to upgrade. You must configure the Pro Plugin Updater (Dashboard -> ZenCache -> Plugin Updater) to be notified when there is a new official release.
Please report bugs and feedback on GitHub.