W3 Total Cache v0.10.1 Released

Thank you for using W3 Total Cache!

With this minor release, we fixed slowdown in Memcached engine, Purge Cache menu links so they flush current blog in WPMU, and fixed am an error during upgrade, “Call to undefined method W3TC Util_Content::is_database_error”.  We’ve also updated Redis cache engine to avoid “Function Redis::delete() is deprecated” warning

In our public repository on GitHub, you can review our source code, post issues, and even submit Pull requests. 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 forums helping end-users. 

 

W3 Total Cache v0.10.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 we continually improve the user experience.

In this release, we’ve added a new statistics component for pro users, redirects by using safer wp_safe redirect, .htaccess usage when page cache does not require it, protection of unexpected values in global variables, and improved support for CloudFront distributions with multiple origins. We’ve also added support for the Memcached binary protocol when available, more Amazon S3 regions, and caching for webp MIME type. 

Additionally, we have fixed some bugs with the usage of base URL with minify, S3 + CloudFront URLs when CNAMEs not used, and mixing the content of sync & async scripts with minify.

In our public repository on GitHub, you can review our source code, post issues, and even submit Pull requests. 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 forums helping end-users. 

W3 Total Cache v0.9.7.5 Released

Thank you for using W3 Total Cache!

We are continuing to improve W3 Total Cache by delivering more speed for your websites and better user experience. With this release, we’ve Updated AWS library due to the deprecation of older API versions scheduled on June 6, 2019, and added support of set_sql_mode by dbcluster. We’ve fixed the PHP warning when remote service cannot be loaded, PHP warnings on the support page and improved support for a web server running on non-default port with disk-enhanced and menu icons.

In our public repository on GitHub, you can review our code, post issues, and Pull requests, and you are welcome to join us there.

We are always looking to improve W3 Total Cache with new features and UI improvements and of course, fixes and improvements for improved user experience so make sure to take some time and rate our plugin here.

Again, big thanks to all of our supporters, including those who are active in the forums helping end users.

 

 

W3 Total Cache v0.9.7.4 Released

Thanks for using W3 Total Cache!

First, we want to thank all of you for bringing bugs and issues to our attention. This is helping us to fix and improve the W3 Total Cache to user satisfaction. In this release we improved security on calls to Opcache flush, cache delivery of /feed URLs, purging of the current page by using post_id instead of URL and minification of files in environments running on non-default ports.

We’ve also added fixes for database cluster in WordPress 5.1, minification in multisite when URLs were set to root-blog based URL, undefined w3tc_ga issue, warning caused by user agent theme change used, 404 in multisite caused by subdirectory issue and PHP warning when Redis integration not configured correctly

Make sure to visit our public repository on GitHub where you can review our code, post issues, and Pull requests.

In future releases, you can expect a lot of new features and UI improvements and of course, fixes and improvements for improved user experience

A big thanks to all of our supporters, including those who are active in the forums helping end users. Please take some time and rate our plugin here. Every feedback and every issue reported is helping us continue offering a top-notch product.

 

W3 Total Cache v0.9.5.3 Released

Thanks for using W3 Total Cache! We are proud to announce that we released the latest build of W3 Total Cache with support from various dedicated contributors (amiga-500 and nigrosimone) and a new partner, Swarmify!

This release includes various improvements to increase compatibility and the reliability of the plugin. And we’re very excited to announce that for those of you that produce video content, you can also us Swarmify to optimize the user experience of that content. Check them out to learn more!

As always, thanks to all of our supporters, including those who are active in the forums helping end users.

W3 Total Cache v0.9.5.2 Released

Thanks for using W3 Total Cache! Our journey to enable great user experiences in WordPress continues with today’s release. As will any minor release, the focus has been on improved security and interoperability / compatibility. With this release we’ve added two security fixes to ensure that your hosting environment is more secure, improved reliability of the plugin itself, and increased the responses of the WordPress administration panel.

As always, thanks to all of our supporters, including those who are active in the forums helping end users.

W3 Total Cache v0.9.5.1 Released

Thanks to everyone that provided bug reports and helped to troubleshoot issues in the forums for other users. As the changelog will show, many of the most glaring issues have been resolved, which hopefully will reveal the next set of high priority concerns users are facing. I hope everyone tests out this release in a staging environment or sandbox before moving to a production environment.

A word to those who’s support of the project takes the form of code:

Looking forward, we’ll be re-visiting our plans for making the github repository public, making our tests available and sharing the roadmap for those who are interested in helping us accelerate it.

Thanks for your support and for using W3 Total Cache!

W3 Total Cache v0.9.5 Released

As always, security is very important to us. A few folks from the community came forward and called those issues to our attention and helped us test those fixes. Specifically, SecuPress team for testing the various security fixes: Security Token ByPass, Arbitrary File Upload, Arbitrary File Download, Arbitrary PHP Eval and the XSS vector. Thanks to those that continue to be supportive in their efforts and kind words.

This release has some cosmetic bugs in the latest version of WordPress, but our test suite shows that core functionality is working as intended. Having said that, I’m sure there are other bugs and bumps in the upgrade process – we’d love to learn about those, so we can push a follow-up release. Thanks in advance for reporting any issues you find. Hopefully, you find them in a staging area and not in your production site.

There are a couple of highlights for this build aside from the security fixes including new functionality for Pro subscribers, new caching engines, new extensions, new integrations and increased interoperability. Please check out the changelog for specifics.

Thanks for using W3 Total Cache!

W3 Total Cache Pro Activation Patch

We recently noticed an increase in the number of customers experiencing activation issues with W3 Total Cache Pro. For those of you who don’t know, this is how it works:

Once you upgrade from the Community (free) version of W3 Total Cache to the Pro version ($99/yr subscription), you’re assigned a license key that in most cases is automatically applied. In the event that activation isn’t automatic, you simply need to paste the license key (which is sent via email and displayed in your browser at the time of purchase) in the License field on the General Settings page and save settings.

A number of customers were unsuccessful in getting the Pro version activated despite following the steps above, and our investigation has revealed that a patch is required in order to complete the activation process if you’re among those affected.

Two things before I reveal the patch:

  1. We’re happy to implement this patch for you! Just email us at w3tc-team@w3-edge.com and let us know that you need help. We’ll provide you with a secure link so you can send us WP Admin and filesystem (SSH or FTP) access. Note that both required to implement and verify the patch, so please be sure you have both ready.
  2. This patch will be in the next release, so most people won’t have to worry about it. We don’t have an ETA we can give you for this release, but it will be available “soon” (smile).

Without further ado.

On line 117 of /w3-total-cache/lib/W3/Licensing.php, the following line:

network_admin_url('admin.php?page=w3tc_general&w3tc_licensing_check_key'))

needs to be replaced with:

wp_nonce_url(network_admin_url('admin.php?page=w3tc_general&w3tc_licensing_check_key'), 'w3tc'))

That’s it.

Please make a backup of this file before making changes if you attempt this on your own, and as always, thanks so much for using W3 Total Cache.

W3 Total Cache and HTTPS

As many of you know, Google has now announced HTTPS as a ranking signal.

In plain English this means that all things being equal, a site served over HTTPS will rank higher than a site served over HTTP. And don’t take “all things being equal” lightly, there are hundreds of factors that influence how well your site ranks (so there’s no need to drop everything and buy an SSL certificate). Regardless, security (as in the case with performance) is clearly a direction towards which the web is moving.

Configuring SSL is a pain, even when you know what you’re doing. The last thing we want here at W3 EDGE is to make it harder for you to run a secure website once you’ve gone through the trouble of implementing security measures.

There are a number of ways in which W3 Total Cache supports both performance and security, and we wanted to highlight a few of these capabilities below:

Page caching

  1. Caching of HTTPS pages: on the page cache settings page, you can “Cache SSL (https) requests” (uniquely) for improved performance.
  2. Page caching exceptions: Pages with customer-specific data (such as shopping cart pages and member profiles) should not be cached in most cases, and W3TC allows you to implement a page caching exception on the pages of your choice via the “Never cache the following pages” section of the page cache settings page. Usage: simply enter “cart/” to exclude that page or “cart/*” to exclude that page and all sub-pages. (Without the quotes, of course.)
  3. Pro tip: you can also use the define('DONOTCACHEPAGE', true); define statement in your functions.php file to specify a page or series of pages where page caching should be disabled. Navigate to Performance > FAQ in your Dashboard for more information.

Content Delivery Networks

  1. Disable CDN on SSL pages: We have a lot of customers who run ecommerce websites and secure transaction pages (/cart, etc.) with SSL. Many of these customers also integrate a Content Delivery Network on their site to improve performance, and this can break SSL pages if the CDN URLs are HTTP. W3TC has long since allowed you to disable CDN on HTTPS pages with a snippet of code, but this functionality is now fully exposed through the UI. Usage: On the CDN Settings page, simply select the “Disable CDN on SSL pages” checkbox under the Advanced section.
  2. SSL Support: W3TC also supports CDNs served over HTTPS.
  3. Pro tip: to maximize the use of W3TC and your CDN on sites with both HTTP and HTTPS pages, you can define both versions of your CDN hostnames in the “Replace site’s hostname with” fields of the CDN settings page in the following format: cdn.yourdomain.com,ssl-cdn.yourdomain.com. You can see Yoast’s configuration illustrated in his excellent post on WordPress and CDNs.

CloudFlare

CloudFlare is a product that many of our customers use for securing and accelerating their sites. You can actually use CloudFlare’s Pro plan ($20/mo as of the time of this post) to serve your site over SSL without needing to purchase and configure an SSL certificate.

The latest version of W3TC ships with a CloudFlare extension to facilitate the connection between your site and the CloudFlare services. This connector is not required for CloudFlare to function of course (CloudFlare works at the DNS level), but our connector exposes a number of useful functions that allow you to make changes right from W3TC.

Fun fact: CloudFlare was originally conceived as a security product that ended up having performance benefits as a result of how it functions.

Help!

I know, this stuff can be overwhelming if you don’t have an engineering degree or if you’re just wading into these waters. You can drop us a note or order professional configuration if you need help.