A couple of weeks ago WooCommerce 3.6.0 was released. As stated by the developers, 3.6 is a minor release, meaning that it should be backwards compatible with existing themes and plugins. Let’s have a look at some of the features of this release.
By far the most important part of the update are the newly introduced product blocks for the WordPress block editor (they were previously available via a separate plugin, but are now bundled with WooCommerce 3.6). If you are running WooCommerce 3.6+ on a WordPress 5.0+ site you will have 8 product blocks as your disposal, similar in functionality to the already available default WooCommerce widgets. To learn more about the product blocks and how to programmatically customize them, have a look at this blog post.
WooCommerce 3.6 aims to be noticeably faster than its predecessors due to many performance improvements, some highlights are:
- A 62% improvement in the load time when ordering and filtering products
- Reduced overall load time by bypassing inactive webhooks
- Reduced the load time for pages with category or product attribute lists
- Reduced load time of product pages with attributes
For a more in depth look at performance improvements check out this post.
Along with the above this version brings many improvements, tweaks and fixes, laid out in detail in the release’s readme file.
CSSIgniter eCommerce themes and WooCommerce 3.6+
Almost half of our WooCommerce compatible themes are already compatible with the new version due to the template-less compatibility implementation, if you are using one of our eCommerce themes and after updating to the latest WooCommerce version you did not get a “templates out of date” nag by WooCommerce, you are good to go. For the rest of you, we have updated our themes to be compatible with the latest version and began releasing them. If you are using our dashboard updater you will get a notification to update your theme, if not you can always find the theme zip files in our downloads section. As always we strongly recommend backing up your site’s database and files before proceeding with the update, the developers may list it as a minor release, but it is better to be safe than sorry.