Changelog

Check out the latest releases from the WooCommerce project.
Subscribe to all release posts via our RSS feed.

  • There’s a new version of WooCommerce Blocks! Version 4.5.1 is now available on WordPress.org and GitHub.

    This release includes a new look for the payment methods section of the Checkout block, a new look for items in the Cart block and some design tweaks to how data is displayed in the Cart and Checkout blocks’ sidebars. The “Place order” button is correctly aligned in the Checkout block now, too!

    Old payment method design

    New payment method design

    We also made changes to the way errors are reported when something goes wrong during checkout relating to stock availability or coupon validity. These errors now explain the problem, which will help the customer to understand why their checkout failed, and what they can do to fix it.

    Another change we made was to the way links to the “Terms and Conditions” and “Privacy Policy” pages are handled, they will now be hidden if the respective page becomes unpublished.

    This release also fixes:

    • a bug where tax would not be calculated properly in the Cart and Checkout blocks
    • a bug where special characters would not render correctly in the Cart sidebar, and
    • a bug where a warning would be displayed if two different items in the Cart had the same name.

    Changelog

    Bug Fixes

    • Fix JS warning if two cart products share the same name. (3814)
    • Align place order button to the right of the block. (3803)
    • Ensure special characters are displayed properly in the Cart sidebar. (3721)
    • Fix a bug where the total price of items did not include tax in the cart and checkout blocks. (3851)

    Enhancements

    • Login links on the checkout should use the account page. (3844)
    • Prevent checkout linking to trashed terms and policy pages. (3843)
    • Improved nonce logic by moving nonces to cart routes only. (3812)
    • If coupons become invalid between applying to a cart and checking out, show the user a notice when the order is placed. (3810)
    • Improve design of cart and checkout sidebars. (3797)
    • Improve error displayed to customers when an item’s stock status changes during checkout. (3703)
    • Dev – Block Checkout will now respect custom address locales and custom country states via core filter hooks. (3662)
    • Update checkout block payment methods UI. (3439)

  • WooCommerce 5.1 is now available for beta testing! You can either download it directly from WordPress.org or install our WooCommerce Beta Tester Plugin.

    What’s new?

    This is a minor release focusing on bug fixes and performance improvements. Just like other minor releases, this release also aims to be backward compatible with previous WooCommerce releases.

    Highlights

    1. WooCommerce Blocks 4.4: Blocks package have been updated to 4.4.3. Please take a look at the release post to see what’s new and improved.
    2. WooCommerce Admin 2.0: WooCommerce Admin package has also been updated to 2.0.1 with this release of WooCommerce. This new package contains lots of bug fixes and stability improvements.
    3. jQuery 3 deprecated items: This will be an ongoing effort to fully remove all deprecated jQuery 3 items from core. #28753
    4. Updating order tax: Previously after recalculating totals when tax setting has changed (such as name and/or rate), the tax name does not update in the order meta. This has been fixed. #28983
    5. Notices not going away: Previously when trying to close an admin notice such as the “Database has been updated” notice, this notice keeps reappearing. This has been fixed. #28500

    Filters and actions

    We have added two new filters in this release.

    FilterDescription
    woocommerce_exporter_product_typesFilter to allow third-parties to filter the exportable product types. #28950

    woocommerce_cancel_unpaid_orders_interval_minutesFilter to change the interval minutes for holding stock on cancel/unpaid orders. #28933
    5.1 new filter hooks

    Database Changes

    This release does not introduce any database changes.

    Template changes

    This release does not introduce any changes to templates.

    Release Schedule

    This version of WooCommerce is scheduled to be released as follows:

    VersionRelease
    BetaFebruary 16th, 2021
    Release CandidateFebruary 23th, 2021
    5.1 Final ReleaseMarch 9th, 2021
    Release schedule for 5.1

    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.

  • We’re excited to announce that WooCommerce 5.0 is now released! This is the second minor release of 2021 and has

    1. 255 commits from 30 contributors in WooCommerce core.
    2. 163 commits from 26 contributors in the WooCommerce admin package.

    This is a minor release, which means everything is backward compatible with the previous version.

    As always, we recommend creating a backup of your site and making sure that themes and plugins are compatible before updating. You can check out this update guide for more information.

    What’s new in 5.0?

    Versioning

    Previous to this release, we’ve partially followed the Semantic Versioning (Semver) schema. Going forward we’ve decided to follow the WordPress versioning schema. This means that although we’re releasing version 5.0 (which usually means a backwards compatible breaking release under Semver), we will maintain backwards compatibility.

    See more details in Developer Advisory: Changes to WooCommerce Versioning Scheme.

    WooCommerce Admin 1.9.0

    This release updates the WooCommerce admin package to 1.9.0 from 1.8.3. Mostly bugfixes and improvements are included in this update, including:

    • Help tooltip will now appear when a task has not been completed the second time to give additional help for the merchant. (#5826)
    • Home screen task extensibility. Allows 3pd to add their own tasks. (#5794).
    • Added “unread” indicator to inbox messages. This helps to quickly see which inbox messages have not been read. (#6047)

    Notable fixes and improvements

    1. Product Review Count: Previously in 4.9, we fixed the product review count from this PR #28624. This worked for all new comments being created however it did not correctly fix the issue that already happened. So we’ve put in a migration script which will fix the review count when new reviews are added. #28814
    2. Deprecate legacy reports: Since WooCommerce 4.0, it has added a new and improved WooCommerce Analytics. We’re encouraging users to start using the new WooCommerce Analytics and thus we have soft deprecated the legacy reports with a notice in the legacy reports section. #28799
    3. CSS Variables: We’ve added WooCommerce prefixed CSS variables to the stylesheet. This provides easier extendibility when developers need to utilize the same WooCommerce default styling without needing to recreate the CSS. #28709
    4. Restoring products, orders and coupons: Previously after trashing orders, products or coupons — when restoring, it puts these items into “draft” status. Now it will restore to the same status as what it was before to prevent issue. #28690
    5. Changing product type with attached files: Previously when an order is placed with a product that had downloadable files and when you change the product type to say a variable product, the permission for the downloadable files would be lost and access would be denied. This has been fixed so that it now recognizes the change of product type and when you go to use the same downloadable file, it would recognize it and recreate the permissions for the same customer. #28521

    You can find the complete changelog for this release in the changelog.txt file.

    Database Changes

    While there are no schema changes to the database tables, we want to highlight that there will be a script that runs in the database that fixes any potential issues with the product review counts. #28814. This in turn will bump the database version to 5.0.0.

    Template Changes

    This release does not introduce any changes to template files.

    Filters and actions

    We have added one new action in this release.

    ActionDescription
    woocommerce_activated_pluginAction to signal that packages such as WC Admin has been activated. #28698
    5.0 new action hooks

    We have added two new filters in this release.

    FilterDescription
    woocommerce_delete_variations_on_product_type_changeFilter to prevent
    variations from being deleted while switching from a variable product type to a variable product type. #27137

    woocommerce_new_order_email_allows_resendFilter to allow resending of the new order email to the admin. #28858
    5.0 new filter hooks

    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

    claudiosanches roykho rrennick vedanshujain Konamiman veljkho
    claudiosanches roykho rrennick vedanshujain Konamiman veljkho
    peterfabian helgatheviking jonathansadowski zhongruige mfs-mindsize menakas
    peterfabian helgatheviking jonathansadowski zhongruige mfs-mindsize menakas
    lsinger ObliviousHarmony Dan-Q psealock Aljullu budzanowski
    lsinger ObliviousHarmony Dan-Q psealock Aljullu budzanowski
    stevegrunwell JoseeWouters sc0ttkclark jahir07 mehrshaddarzi paulochang
    stevegrunwell JoseeWouters sc0ttkclark jahir07 mehrshaddarzi paulochang
    jffng kevinruscoe raicem ilyasfoo
    jffng kevinruscoe raicem ilyasfoo

    WooCommerce Admin

    samueljseay joshuatf joelclimbsthings louwie17 octaedro moon0326
    samueljseay joshuatf joelclimbsthings louwie17 octaedro moon0326
    hsingyuc psealock adrianduffell ilyasfoo becdetat johndcoy
    hsingyuc psealock adrianduffell ilyasfoo becdetat johndcoy
    ribaricplusplus nerrad manjeet-wisetr tomalec
    ribaricplusplus nerrad manjeet-wisetr tomalec

  • We have released a WooCommerce 5.0 release candidate 3 and are still on track for our planned release February 9th.

    Note that this is a minor release focusing on bug fixes and performance improvements. See more details of our versioning changes in Developer Advisory: Changes to WooCommerce Versioning Scheme.

    Changes

    • WooCommerce Admin 1.9.0 final release

    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.

    Thanks to all of our testers and contributors!

  • Today we released a patch version of WooCommerce Blocks to fix compatibility with 3rd party payment gateway integrations.

    Version 4.4.2 is now available on WordPress.org and GitHub.

    Changelog

    Bug Fixes

    • Adds a default “features” array for payment methods which do not define supported features. Fixes conflicts with 3rd Party payment method integrations.

  • We recently released updates to all of our end-to-end testing packages:

    Below you’ll find an overview of what has changed for each of these packages.

    @woocommerce/api

    This release contained compatibility fixes for the core tests and utilities packages. There were no new features released.

    @woocommerce/e2e-core-tests

    FLAKY TESTS

    There were a few tests that would intermittently fail when run locally in headless mode. We addressed almost all of the known ones with either a small code fix or by using an alternate method to complete an action.

    CONFIG DEPENDENCY

    In version 0.1.0, if you added this package to your project without the e2e-environment package, it would only work if you had the config dependency in your main package. Version 0.1.1 includes the dependency.

    NEW TESTS

    We added and updated a number of tests. See @woocommerce/e2e-core-tests for more details.

    @woocommerce/e2e-utils

    CONFIG DEPENDENCY

    In version 0.1.1, if you added this package to your project without the e2e-environment package, it would only work if you had the config dependency in your main package. Version 0.1.2 includes the dependency.

    MERCHANT AND SHOPPER FLOWS

    To be more consistent with the terminology we are using for end-to-end testing we have renamed a few test flows.

    • StoreOwnerFlow is now merchant
    • CustomerFlow is now shopper

    Tests using either StoreOwnerFlow or CustomerFlow will log a deprecated message. The deprecated messages are warnings and will not cause tests to fail.

    UTILITY FUNCTIONS

    We added a number of utility functions. See @woocommerce/e2e-utils for more details.

    @woocommerce/e2e-environment

    Note: With this release we have completed all of the planned features for this package. As a result, we have bumped the version of the package to 0.2.0. While we may have maintenance releases, we are not planning any new development for this package.

    DOCKER LIBRARY NEW IMAGE DELAY

    When new images are published by Docker, such as images containing new versions of PHP, the image is initially pushed to the API that we query to get the latest software versions. There is a time lag between new images being listed as available on the API and being available to docker-compose. We changed the image version lookup to ignore images that are less than 12 hours old.

    E2E SHORTHAND SCRIPT

    In version 0.1.6 accessing the package scripts required you to run the following command:

    npm explore @woocommerce/e2e-environment -- npm run <script>

    In 0.2.0 npx wc-e2e <script> accomplishes the same thing.

    CUSTOM CONTAINER NAME

    In version 0.1.6 the Docker containers were automatically named <project-folder-name>_*. In 0.2.0 you can implement a custom container prefix in tests/e2e/config/default.json. For example:

    "url": "http://localhost:8084/",
"appName": "custom_container_prefix",

    For full details on the release see @woocommerce/e2e-environment.

    What’s Next?

    We will be publishing resources in the developer portal in the near future to provide instructions on implementing these packages in your development projects.

    Over the next few months, we will continue to iterate on the core tests and API packages. As we flesh those packages out, we will be adding functionality to the utilities package. We will be releasing updates to those packages as that work completes.

  • There’s a new version of WooCommerce Blocks! Version 4.4.0 is now available on WordPress.org and GitHub.

    This release includes several small tweaks and bug fixes across our blocks to fix markup issues and improve accessibility.

    One minor change theme authors may need to be aware of is that the star ratings markup within the All Products block no longer uses the classname star-rating. This is to prevent conflicts with themes using this class to add star icons which conflict with the icons that blocks adds. This component can still be targeted with the classname .wc-block-components-product-rating.

    Additionally, behind the scenes there have been compatibility improvements in preparation for subscriptions support, and in preparation for widget areas coming soon to WordPress core, the All Products Block (and related filter blocks) have been disabled in widget areas until we have a better idea on how to support them properly.

    Changelog

    Bug Fixes

    • Fix – Ensure empty categories are correctly hidden in the product categories block. (3765)
    • Fix – Added missing wrapper div within FeaturedCategory and FeatureProduct blocks. (3746)
    • Fix – Set correct text color in BlockErrorBoundry notices. (3738)
    • Hidden cart item meta data will not be rendered in the Cart and Checkout blocks. (3732)
    • Fix – Improved accessibility of product image links in the products block by using correct aria tags and hiding empty image placeholders. (3722)
    • Add missing aria-label for stars image in the review-list-item component. (3706)
    • Prevent “X-WC-Store-API-Nonce is invalid” error when going back to a page with the products block using the browser back button. (3770)

    Compatibility

    • Hide the All Products Block from the new Gutenberg Widget Areas until full support is achieved. (3737)
    • Legacy star-rating class name has been removed from Product rating block (inside All Products block). That element is still selectable with the .wc-block-components-product-rating class name. (3717)

    Enhancements

    • Design tweaks to the cart page which move the quantity picker below each cart item and improve usability on mobile. (3734)

  • We have released a second release candidate for WooCommerce 5.0 and are still on track for our planned release February 9th.

    Note that this is a minor release focusing on bug fixes and performance improvements. See more details of our versioning changes in Developer Advisory: Changes to WooCommerce Versioning Scheme.

    Changes

    • Fixed deprecated notices in Cart, Checkout and My Account page in WordPress 5.7 alpha #28993
    • Increased minimum WordPress version required to 5.4 according to our WordPress core support policy.

    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.

    Thanks to all of our testers and contributors!

  • We’re excited to announce that the release candidate is now available! We are on track for our planned February 9th release date.

    Note that this is a minor release focusing on bug fixes and performance improvements. See more details of our versioning changes in Developer Advisory: Changes to WooCommerce Versioning Scheme.

    Changes

    This release candidate doesn’t include any changes since 5.0 beta 2.

    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.

    Thanks to all of our testers and contributors!

  • This fix release is a preparation for the upcoming 5.0 release and corrects the messaging of update notices to align them with the recently adopted versioning schema. Since going from 4.9 to 5.0 is not considered a breaking or major release anymore, we’ve decided to remove the extra warnings WooCommerce core previously added. Thus, it should prevent confusion and provide a more seamless upgrade experience to all users who upgrade to 4.9.2.

    The warnings in the plugin and System Status screens are thus are no longer relevant and have been removed:

    Changelog

    This release contains only a single change:

    • Deactivate untested plugins’ notices on major releases. #28840

    You can download the latest release of WooCommerce here or visit Dashboard → Updates to update the plugin from your WordPress admin screen.

    As usual, if you spot issues in WooCommerce core, please log them in detail on GitHub. Found a security issue? Please submit a report via HackerOne.