We are pleased to announce that WooCommerce 3.7 is now officially available for beta testing.
To beta test this release of WooCommerce 3.7 you can download it from the WordPress.org plugin repository, directly from GitHub, or install our WooCommerce Beta Tester plugin which allows you to easily test out this beta and all future beta and release candidates.
What’s new in 3.7?
WooCommerce 3.7 is the second minor release of 2019, and being a minor release everything included in this release is backward compatible. This minor release is also a bit smaller in changes than previous minor releases as we work towards smaller more frequent releases.
We are excited to include WooCommerce Product Blocks 2.3 in this release. WooCommerce Products Blocks is our eCommerce focused blocks for the Gutenberg editor that has been part of WordPress since 5.0.
The first Product Blocks were included in WooCommerce 3.6 and with the inclusion of Product Blocks 2.3 in WooCommerce 3.7, there are several new features added.
Some new features and improvements include:
- A new Focal Point picker on the Featured Product block.
- Searching for products in Featured Product & Hand-picked Product blocks is faster.
- A new Product Categories List block.
- Better block branding for easier discoverability.
- A new Featured Category Block; feature a category and show a link to its archive.
- A new Products by Tag(s) block.
In order to have access to the new Product Blocks, you will need to have WordPress 5.1+ installed or have the latest version of the Gutenberg Editor plugin installed.
With our continued focus on improving performance in WooCommerce, this release also includes some under the hood changes to ensure WooCommerce is faster than ever.
We have improved the speed of the admin dashboard even more, reduced the number of queries required to populate variations, fixed issues with the persistent cart that slowed things down a bit, and are now excluding action scheduler task from comment queries which speed up a lot of pages where comment data is retrieved (product reviews, post comments, admin pages).
New PHP and WordPress minimum requirements
With this release we are bumping the minimum required PHP version to PHP 5.6. This is needed to work towards having our customer stores run on a supported version of PHP as well as set us up for using newer and more performant functionality.
We are also bumping the minimum required WordPress version to WordPress 4.9 in this release and will likely in the next release move that to WordPress 5.0.
We have added upgrade nudges in WooCommerce 3.6.5 pointing users to our new document you can follow to make sure you have the latest and greatest versions. Stores running a version of PHP less than 5.6 and WordPress 4.9 will not be able to update to WooCommerce 3.7.
A new package management system
With the new PHP 5.6 minimum requirement in place, we are able to utilize PHP packages. End users are not affected by this change.
Since the majority of new WooCommerce features are being developed as feature plugins, separate from WooCommerce core, under the hood we have made some change on how these features are included and loaded.
We have removed the Product Blocks as well as REST API functionality from WooCommerce core and these are all now developed and released independently yet included with each WooCommerce release via Composer.
This allows us to eliminate feature plugin conflicts easier, utilize namespaces and ensure more efficient loading of the code as it is needed within WooCommerce core.
In addition to the above, we have also included the following enhancements in WooCommerce 3.7.
- The ability to change the “Thanks” wording in emails from the email settings.
- Moved tax classes from using WordPress options to its own
wc_tax_rate_classestable for storage.
- Added new Coupon code generator functionality to the coupons page.
Beyond these enhancements, the release also contains some tweaks, new hooks and, fixes – all of which you can find out about in the readme.
Template file changes
The following template files have been updated/changed in this release.
|All template files||Reviewed and updated the escaping.|
|checkout/thankyou.php||Added new filter |
|cart/mini-cart.php||Removed subtotal function call and replaced with new |
|cart/cart.php||Added new filter |
|loop/result-count.php||Correct the plurals form usage.|
Deprecated functions and methods
- Deprecated the
WC_Abstract_Order::get_used_coupons()method and replaced it with a new method
WC_Abstract_Order::get_coupon_codes()to make it easier to identify that codes are returned and no coupon objects.
- Removed the
WC_Cart::restore_cart_item()in favor of the existing
woocommerce_cart_item_removedaction. This action should already be in use if you are using woocommerce_before_cart_item_quantity_zero.
|Beta||16 July 2019|
|RC||29 July 2019|
|Release 3.7||12 August 2019|
If you’d like to help us test, you can use our new WooCommerce Beta Tester plugin. We posted a nice little write-up on beta testing here which should get you started. Please read that and jump right in!
We would also like to welcome all testers to join us at our next Community Chat scheduled for 25 July 2019 at 16:00 UTC in the #core channel of the WooCommerce Community Slack.
6 replies on “WooCommerce 3.7 Beta 1”
“We have removed the Product Blocks as well as REST API functionality from WooCommerce core and these are all now developed and released independently yet included with each WooCommerce release via Composer.”
For those who already use the API, will it be necessary to upgrade WooCommerce and install the API plugin?
No, as stated nothing changes for the end user. When we release a new version of WooCommerce we include the API with it.
LikeLiked by 3 people
The real speed change will come with separating products and orders from Post tables. You had this in development and it was somehow abandoned after. Do you have any info when it would come to Wocommerce? Thanks.
Liviu, it is not abandoned we are still exploring it, but with all the changes we made in WooCommerce 3.6 already the speed difference we saw with the current implementation are a bit negligible that is why we are exploring those ideas further.
The scale of changes makes the chance of breaking things when upgrading to a custom table solution very high, that is why we set out to explore a different approach.
If we do decide to roll out custom tables in the future it will also not be in a minor release like this but rather a major one like 4.0 of 5.0.
LikeLiked by 3 people