W3 Total Cache v0.12.0 Released

Thank you for using W3 Total Cache!

The newest update for W3 Total Cache is here and we will continue to deliver more speed for your WordPress websites while continually improving the user experience.

In this release we’ve added query string based URL structures to cache AMP pages using a query string, filter of minify options (added support for ‘postprocessor’ option usage programmatically), lazyload picture tag support, removed the footer link “Support Us” option, improved wp_die handling, lazyload handling of content in script tags, lazyload handling of feeds, printing tags coming from feeds, handling of modified posts before wp_rewrite initialized and handling of .htaccess files in regard to EOF (End of File). Nginx rules have also changed a lot to avoid “location” block conflicts. That change may cause problems on some systems using non-default WordPress rules – keep a backup of your original rules to ensure you minimize issues. We’ve also fixed Varnish purging and HTML minification of data tags equaling 0. In our public repository on GitHub, you can review our source code, post issues, and even submit pull requests if you are interested in contributing to the project. You are welcome to join us there, and we really appreciate all users that have contributed, both past and present.

We are always looking for ways to improve W3 Total Cache with new features, UI improvements, and of course, improvements to the user experience. If you like what we have done, please be sure to take some time and rate our plugin on the WordPress Plugin Repository.

Once again, we are sending a big thanks to all of our supporters, including those who are active in the community forums helping out end-users.

Nginx non-default WordPress rules

 

In previous W3 Total Cache versions, rules for the Nginx server were not correct when the option “Prevent caching of objects after settings change” in Performance > Browser Cache > General was enabled along with “Rewrite URL structure of objects”.  Having both of these enabled caused PHP fallback to be used for all minify assets when utilizing the Disk: Enhanced page cache engine.

W3 Total Cache 0.12.0  removes “location” block conflicts for URL postfix rewrites and adds header directives for all other “location” blocks.

In 0.12. version security headers will also work correctly now, which wasn’t the case before as Minify set to disk was not rewriting when Browser Cache with Prevent Object Caching was used in Nginx

That change may, however, due to problems on some systems using non-default WordPress rules so keep a backup of your original rules to ensure you minimize issues.

Particularly WordPress Networks (WPMU) deployed in subfolders instead of in the root directory of the domain, i.e. myhost.com/myfolder/ for WordPress set up and myhost.com/myfolder/my-blog2/ for subdirectory network blogs.