Changelog
Check out the latest releases from the WooCommerce project.
Subscribe to all release posts via our RSS feed.
-
We are pleased to announce the release of WooCommerce 6.1. This release should be backwards compatible with the previous version.
This release contains:
- 309 commits from 35 contributors in WooCommerce Core
- 32 commits from 15 contributors in WooCommerce Admin
- 85 commits from 19 contributors in WooCommerce Blocks
- 78 commits from 8 contributors in ActionScheduler
As always, we recommend creating a backup of your site and making sure that your theme and any other plugins are compatible before updating. You can check out this update guide for more information.
What’s new in 6.1?
- WooCommerce Blocks: We’ve updated to the 6.5.1 version of the feature plugin. See the release posts for 6.4.0 and 6.5.0, and the changelog for 6.5.1 to see what’s new.
- WooCommerce Admin: We’ve updated to the 3.0.3 version of the feature plugin. See the changelog to find out what’s new.
- ActionScheduler: ActionScheduler has been updated to version 3.4.0. See the release post to see what’s new.
These are just some of the changes that are included in WooCommerce 6.1. You can find the complete changelog for this release in the changelog.txt file.
Actions and Filters
This release adds one action:
Action Description woocommerce_page_wc-addons_connection_error Triggered when there is an error with the connection to the woo.com marketplace. This release doesn’t add any filters.
Database Changes
There are no database changes in this release.
Template Changes
There are no template changes in this release.
Deprecations
The
is_ajax
function has been deprecated. The WordPress functionwp_doing_ajax
should be used instead.Much 💜 to all the contributors
Finally a big thanks to everyone in the community who has contributed via issue reports, fixes, translation, testing, supporting other users, or simply spreading the word.
WooCommerce core
MrJnrman Luc45 roykho rrennick zhongruige jonathansadowski rodelgc lanej0 tjcafferkey ObliviousHarmony claudiosanches vedanshujain barryhughes sunyatasattva anitaa1990 jeffstieler louwie17 drjamesj Aljullu Konamiman tammullen joelclimbsthings adrianduffell ilyasfoo psealock WooCommerce Admin
chihsuan moon0326 louwie17 joshuatf octaedro joelclimbsthings jeffstieler NeosinneR ilyasfoo adrianduffell johnregan3 WooCommerce Blocks
ralucaStan mikejolley sunyatasattva gigitux Aljullu tjcafferkey opr dinhtungdu alexflorisca nielslange jonny-bull malithsen Action Scheduler
ovidiul barryhughes danielbitzer glagonikas Konamiman peterfabian olegabr jeffstieler vedanshujain roykho jonathansadowski
-
A new version of WooCommerce Blocks has been released! Version 6.7.1 is now available for download from GitHub and WordPress.org.
This is a patch release to fix the
payment_data[0] [value] is not of type string.boolean
error users were seeing in the Checkout block when trying to pay with their saved cards. This was a regression introduced in version 6.6.0.For more details checkout the Changelog below.
Changelog
Bug Fixes
- Convert token to string when setting the active payment method. (5535)
-
It’s been a while since we bumped the minimum PHP version of WooCommerce to 7.0, and it is about time for a new bump. Starting with version 6.5, scheduled for release in May 2022, WooCommerce will require PHP 7.2 or newer to work.
Why this change?
The PHP ecosystem is evolving rapidly. At the time of writing this, the only actively maintained versions of PHP are 8.0 and 8.1; PHP 7.4 entered “security fixes only” mode and PHP 7.3 went unsupported as of December 2021. WordPress recommends at least PHP 7.4 for performance and security reasons, and these reasons are even more important on an e-commerce site.
WooCommerce also depends on a number of third-party packages — and many of those are gradually dropping support for older PHP versions. This is already causing issues, as it’s increasingly hard to find packages that support all the range of PHP versions from 7.0 to 8.1.
Why 7.2 specifically? This is the oldest version that still has a significant number of WooCommerce installs running according to our data:
Note that of all the sites running on PHP 7.0 or 7.1, only about half seem to be actively maintained — that is, running a WooCommerce version that is at most six months old.
What happens if I don’t upgrade?
If your server is still on PHP 7.0 or 7.1 by the time WooCommerce 6.5 is published, your WooCommerce instance will continue working, but you won’t be able to upgrade past WooCommerce 6.4 (or any 6.4.x maintenance release published afterwards).
We strongly recommend upgrading your servers to at least PHP 7.4 in order to keep your WooCommerce sites up to date, performant, and secure.
-
We’re excited to announce that the second release candidate for WooCommerce 6.1 is now available. We are currently on track for our planned January 11th release date.
Changes
Since the release of RC.1, the following changes have been made:
- WooCommerce Admin has been updated from 3.0.0-RC1 to 3.0.1. The changelog is available here.
- Support has been added for Gutenberg 12.1.0’s block template naming convention. (#31522)
Testing
If you’d like to dive in and help test this new release, our handy WooCommerce Beta Tester plugin allows you to switch between beta versions and release candidates. You can also download the release from WordPress.org.
A set of testing instructions has been published on our Wiki page in GitHub. We’ve also posted a helpful writeup on beta testing to help get you started.
If you discover any bugs during the testing process, please let us know by logging a report in GitHub.
-
A new version of WooCommerce Blocks has been released! Version 6.7.0 is now available for download from GitHub and WordPress.org.
Full-Site Editing templates
This release rolls out some fixes for the Block based Full-Site Editing templates, specifically one regarding custom templates and one around the template retrieving logic. It also adds Global Styles support for the Active Product Filters block.
WooCommerce Blocks
We fixed two bugs signalled to us by our users: blank fields in the Checkout block for logged in customers and a bug happening in the On Sale Products block when no variable products are present. The Checkout block now prevents a zero shipping price from being shown in the Checkout when no shipping methods are available.
For more details please see the Changelog below:
Changelog
Bug Fixes
- Fixed an issue where the checkout address fields would be blank for logged in customers. (5473)
- Account for products without variations in the On Sale Products block. (5470)
- Ensure that the translation of the “Proceed to Checkout” button is working. (5453)
- Remove text decorations from product filtering blocks items. (5384)
- Update the template retrieving logic to allow for older Gutenberg convention and newer one (`block-templates`/`block-template-parts` vs. `templates`/`parts`). (5455)
- Fix custom templates with fallback to archive being incorrectly attributed to the user in the editor instead of the parent theme. (5447)
Various
-
We’re excited to announce that the first release candidate for WooCommerce 6.1 is now available. We are currently on track for our planned January 11th release date.
Changes
Since the beta release, the following change has been made:
- WooCommerce Blocks has been updated to 6.5.1. The changelog is available here.
Testing
If you’d like to dive in and help test this new release, our handy WooCommerce Beta Tester plugin allows you to switch between beta versions and release candidates. You can also download the release from WordPress.org.
A set of testing instructions has been published on our Wiki page in GitHub. We’ve also posted a helpful writeup on beta testing to help get you started.
If you discover any bugs during the testing process, please let us know by logging a report in GitHub.
-
Beta 1 for the January 2022 release of WooCommerce is now available for testing! You can either download it directly from WordPress.org or install our WooCommerce Beta Tester Plugin.
Highlights
- WooCommerce Blocks: We’ve updated to the 6.5.0 version of the feature plugin. See the release posts for 6.4.0 and 6.5.0 to see what’s new.
- WooCommerce Admin: We’ve updated to the 3.0.0-rc version of the feature plugin. See the changelog to find out what’s new.
- ActionScheduler: ActionScheduler has been updated to version 3.4.0. See the release post to see what’s new.
Filters and Actions
This release adds one action:
Action Description woocommerce_page_wc-addons_connection_error Triggered when there is an error with the connection to the woo.com marketplace. This release doesn’t add any filters.
Database Changes
There are no database changes in this release.
Template Changes
There are no template changes in this release.
Deprecations
- The
is_ajax
function has been deprecated. The WordPress functionwp_doing_ajax
should be used instead.
Release Schedule
Version Release Beta December 21, 2021 Release Candidate December 28, 2021 Final Release January 11, 2022 Testing
If you’d like to dive in and help test this new release, our handy WooCommerce Beta Tester plugin allows you to switch between beta versions and release candidates. You can also download the release from WordPress.org.
A set of testing instructions has been published on our Wiki page in GitHub. We’ve also posted a helpful writeup on beta testing to help get you started.
If you discover any bugs during the testing process, please let us know by logging a report in GitHub.
-
A new version of WooCommerce Blocks has been released! Version 6.6.0 is now available for download from GitHub and WordPress.org.
This release rolls out some fixes for the Block based full-site editing templates, fixes some performance issues, improves data sync between cart and draft orders, and improves error handling with the new checkout experience.
Dev Notes
- We’ve been increasing the adoption of TypeScript across the codebase, and in this release, we’ve updated
usePaymentMethodInterface
to include correct typescript definitions, so if you were importing our typedefs, you’ll need to modify where you pull them from. - The Store API will now sync cart data (on change via a Store API route) to any existing draft order. Additonally, there is now an extra
woocommerce_blocks_cart_update_customer_from_request
hook should you need to update custom customer data from thecustomer-update
route.
Changelog
Bug Fixes
- “Added By” template column value is user friendly for modified WooCommerce block templates. (5420)
- Fixed a performance issue with the cart by preventing an extra network request on mount. (5394)
- Use the themes product archive block template for product category & product tag pages if the theme does not have more specific templates for those. (5380)
- Cart block: Switch to correct view if inner block is selected. (5358)
- Respect implicit quantity updates coming from server or directly from data stores. (5352)
- Fixed a case where payments could fail after validation errors when using saved cards. (5350)
- Add error handling for network errors during checkout. (5341)
- Fix cart and checkout margin problem by removing the full-width option. (5315)
Various
- Sync draft orders whenever cart data changes. (5379)
- Removed legacy handling for shipping_phone in Store API. (5326)
- Site Editor template list: Fix wrong icon displayed on WooCommerce templates after they have been edited. (5375)
- Fix validation error handling after using browser autofill. (5373)
- Update loading skeleton animations. (5362)
- Add error handling to
get_routes_from_namespace
method. (5319)
- We’ve been increasing the adoption of TypeScript across the codebase, and in this release, we’ve updated
-
We are pleased to announce the release of WooCommerce 6.0. This release should be backwards compatible with the previous version.
Due to internal process changes, the WooCommerce 6.0 release was delayed by one day. This allowed for us to complete some additional testing, and we don’t anticipate a delay for the WooCommerce 6.1 release.
This release contains:
- 356 commits from 27 contributors in WooCommerce Core
- 117 commits from 20 contributors in WooCommerce Admin
- 194 commits from 25 contributors in WooCommerce Blocks
As always, we recommend creating a backup of your site and making sure that your theme and any other plugins are compatible before updating. You can check out this update guide for more information.
What’s new in 6.0?
- WooCommerce Blocks: We’ve updated to the 6.3.3 version of the feature plugin. See the release posts for 6.3.2 and 6.2.0 to find out what’s new.
- WooCommerce Admin: We’ve updated to the 2.9.4 version of the feature plugin. See the changelog to find out what’s new.
- Product Attribute Filtering: With this release, we are entering the final stages of delivering our revamp of product attribute filtering. We have removed the need for a code snippet to show the feature; both the feature flag and system tool is now available for all merchants.
- Rate Limit Table: In order to address the performance issues caused by storing rate limits in the options table, we have created a new table to hold rate limit entries. See #30960 for more details.
These are just some of the changes that are included in WooCommerce 6.0. You can find the complete changelog for this release in the changelog.txt file.
Actions and Filters
This release adds two actions:
Action Context woocommerce_product_options_shipping_product_data After the shipping options in the product data metabox. #30876 woocommerce_after_variations_table After the variations table on the add-to-cart form. #29642 This release adds two filters:
Filter Description woocommerce_quantity_input_autocomplete Allows filtering the ‘autocomplete’ attribute for quantity inputs. #31196 woocommerce_has_block_template Filters the return value of the block template check. #30997 Database Changes
- New
woocommerce_rate_limits
table. #30960
Template Changes
Template File Description templates/emails/customer-new-account.php Removed the generated password and replaced with a reset link. templates/emails/plain/customer-new-account.php Removed the generated password and replaced with a reset link. templates/myaccount/form-login.php Changed the text informing users that the password will be emailed to them to inform them that a reset link will be sent to them. Much 💜 to all the contributors
Finally a big thanks to everyone in the community who has contributed via issue reports, fixes, translation, testing, supporting other users, or simply spreading the word.
WooCommerce Core
roykho MrJnrman rrennick rodelgc masteradhoc zhongruige ObliviousHarmony peterfabian psealock barryhughes Konamiman vedanshujain claudiosanches andfinally jeffstieler jonathansadowski tammullen moon0326 unscripted adrianduffell sultann Aljullu mahmoudsaeed nielslange superdav42 tjcafferkey matt-h kkmuffme WooCommerce Admin
moon0326 joshuatf louwie17 octaedro ilyasfoo adrianduffell joelclimbsthings jacob-sewell johnregan3 mikkamp hellwig-data443 mattsherman WooCommerce Blocks
mikejolley Aljullu dinhtungdu sunyatasattva gigitux tjcafferkey alexflorisca nielslange senadir ralucaStan opr Konamiman nerrad Action Scheduler
ovidiul barryhughes Konamiman
-
A new version of WooCommerce Blocks has been released! Version 6.4.0 is now available for download from GitHub and WordPress.org.
This release fixes an issue with the Featured Product block search functionality when you have a store with a large (100+) product catalog. In addition to this we also added global styles support for the Product Categories List block.
Changelog
Enhancements
- Added global styles (text color, link color, line height, and font size) to the Product Title block. (5133)
Bug Fixes
- Fixed the Featured Product Block search not working for large stores with 100+ products. (5156)