Changelog

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

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

    What’s new?

    The WooCommerce 4.7 release contains an updated version of WooCommerce Blocks 3.6.0, several fixes, and localization improvements.

    Notable fixes and improvements

    The main fixes and stability improvements in this release are:

    • Use first gallery image on single product when a product thumbnail isn’t assigned. (#27289). (Feature reverted in 4.7.0 beta 2).
    • Update product_cat/tag taxonomy template file names to product-cat, and product-tag. (#27736).
    • Exclude draft pages from the “Shop page” setting. (#27890).

    You can review the complete changelog for this release on the changelog.txt file.

    Filters and actions

    We have added one new filter:

    FiltersDescription
    woocommerce_should_send_low_stock_notificationDetermine if the current product should trigger a low stock notification..

    Database changes

    This release does not introduce any changes to the database.

    Template changes

    Several files were added or updated in this release, including:

    FileDescription
    content-product-cat.phpNew file introduced by #27736 to replace content-product_cat.php
    taxonomy-product-cat.phpNew file introduced by #27736 to replace taxonomy-product_cat.php
    taxonomy-product-tag.phpNew file introduced by #27736 to replace taxonomy-product_tag.php
    single-product/product-image.phpUpdated to support include the first image as a product thumbnail, see #27289 (Feature reverted in 4.7.0 beta 2)
    single-product/product-thumbnails.phpUpdated to support include the first image as a product thumbnail, see #27289 (Feature reverted in 4.7.0 beta 2)

    Note that content-product_cat.php, taxonomy-product_cat.php, and taxonomy-product_tag.php are still supported by WooCommerce.

    Release Schedule

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

    VersionRelease
    BetaOctober 20, 2020
    Release CandidateOctober 27, 2020
    4.7 Final ReleaseNovember 10, 2020

    Testing

    As with the previous several releases, we have published testing instructions for 4.7. We’d love your help in testing this release.

    If you discover any bugs during the testing process, please let us know by logging a report in GitHub.

  • We are excited to announce that WooCommerce 4.6 is now publicly available! It has been in development since September 2020 and has been updated with 327 commits from 31 contributors.

    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 4.6?

    The WooCommerce 4.6 release contains updated versions of WooCommerce Admin (1.6.1) and WooCommerce Blocks (3.4.0), fixes, and localization improvements.

    New home screen enabled for everyone

    https://woocommerce.files.wordpress.com/2020/06/home-screen.png?w=1024
    The new Home Screen in WooCommerce

    The new home screen was introduced in WooCommerce 4.3 for new stores and now we’re expanding this experience to existing stores as well. You can find more about it in the documentation.

    Notable fixes and improvements

    The main fixes and stability improvements in this release are:

    1. Sorting country names now works as expected for languages that use graphic accents (#27416).
    2. Style improvements to the notices when using the Twenty Twenty theme (#27387).
    3. It is now possible to assign to a product a tax class that contains non-ASCII characters (#27615).
    4. The old setup wizard was removed (#26853).

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

    Filters and actions

    We have added new filters and actions:

    FiltersDescription
    woocommerce_return_to_shop_textFilter to change the label of the “Return to shop” button in the empty cart page.
    woocommerce_cart_item_required_stock_is_not_enoughFilter to change the behavior when checking stock for items in the cart.
    woocommerce_should_send_no_stock_notificationFilter to let developers skip the no stock e-mail for certain products.
    woocommerce_after_order_detailsAction to add extra data after the order details section.

    Database changes

    This release does not introduce any changes to the database.

    Deprecated code

    This following parts of the code were deprecated in this release:

    • The classes WC_Admin_Setup_Wizard and WC_Admin_Setup_Wizard_Tracking with no replacement.
    • The method WC_Admin_Notices::install_notice() with no replacement.
    • The files includes/admin/views/html-notice-install.php, assets/css/wc-setup.scss and assets/js/admin/wc-setup.js with no replacement.

    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

    ObliviousHarmony rrennick rodrigoprimo Konamiman claudiosanches jonathansadowski
    ObliviousHarmony rrennick rodrigoprimo Konamiman claudiosanches jonathansadowski
    juliaamosova jondcampbell peterfabian vedanshujain timmyc kloon
    juliaamosova jondcampbell peterfabian vedanshujain timmyc kloon
    Knyazevich om4james joshuatf dd32 nerrad atimmer
    Knyazevich om4james joshuatf dd32 nerrad atimmer

    WooCommerce Admin

    becdetat psealock octaedro jeffstieler joshuatf samueljseay
    becdetat psealock octaedro jeffstieler joshuatf samueljseay
    adrianduffell timmyc joelclimbsthings dechov jconroy frosso
    adrianduffell timmyc joelclimbsthings dechov jconroy frosso

    WooCommerce Blocks

    nerrad Aljullu haszari senadir
    nerrad Aljullu haszari senadir

    Action Scheduler

    rrennick
    rrennick

  • Storefront 2.8.0 has been tagged for release and uploaded to WordPress.org. This is small maintenance release.

    Here’s the changelog:

    • Dev: Reinstate PHPcs linting #1463
    • Dev: Add wp-env npm script alias #1489
    • Dev: Tweak npm config & scripts for release tooling changes #1462
    • Dev: Various dependency updates

    Download the latest release of Storefront from WordPress.org, or venture over to Dashboard → Updates in your WordPress admin to update your theme.

    As usual, if you see any issues, please log them in detail on Github.

  • A new version of WooCommerce Blocks has been released! Version 3.6.0 is available for download from GitHub and WordPress.org.

    This release is fully compatible with WooCommerce 4.6, scheduled to be released tomorrow, and includes several bug fixes to the Checkout block payment flow.

    We’ve also updated the blocks styles so that they’re loaded after the WP editor CSS, ensuring blocks look more similar between the frontend of the store and the editor.

    For developers

    We fixed an inconsistency in the payment methods API with the retry property in the checkoutAfterProcessingWithSuccess/Error observers. Now it defaults to true if it’s not defined. We also introduced a shouldRetry method that allows adding more complex rules to whether a payment method should offer a customer the option to retry after a failed payment. You can read more details in the Checkout Block Flow documentation.

    We’ve also changed how the payment method tabs are loaded: prior to this release the content of all tabs was rendered on page load, but with this update, only the content of the selected tab will be rendered. This will ensure better performance for sites with many payment methods and will remove the need for payment gateways to check if they are the active one or not.

    Changelog

    Bug fixes

    • Make ‘retry’ property on errors from checkoutAfterProcessingWithSuccess/Error observers default to true if it’s undefined. (3261)
    • Ensure new payment methods are only displayed when no saved payment method is selected. (3247)
    • Load WC Blocks CSS after editor CSS. (3219)
    • Restore saved payment method data after closing an express payment method. (3210)

    Refactors

    • Don’t load contents of payment method hidden tabs. (3227)

  • After releasing the beta version last week we found a few issues that needed fixing. We fixed those issues and are moving ahead according to the plan. We’re excited to announce that the release candidate is now available! We are on track for our planned October 13 WooCommerce 4.6 final release date.

    Fixes

    Since the beta version, the following fixes were added:

    • Redirect users to setup wizard when WooCommerce is activated (#5214 and #5230).
    • Enlarged store profiler text in two steps (#5194).
    • Bug where sometimes the task list would not vanish after being completed (#5205).

    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!

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

    This release is mostly a fix release with more enhancements around payment methods.

    More resilient payment methods. When a payment method fails registration, the other will continue to be working.

    Changes to supported versions of WooCommerce and PHP. the plugin is now more aligned with WooCommerce in terms of supported PHP version (7.0) and a minimum of WooCommerce 4.3 is now required.

    Changelog

    Bug Fixes

    • Use light default background colour for country/state dropdowns. (3189)
    • Fix broken Express Payment Method use in the Checkout block for logged out or incognito users. (3165)
    • Fix State label for Spain. (3147)
    • Don’t throw an error when registering a payment method fails. (3134)

    refactor

    • Use noticeContexts from useEmitResponse instead of hardcoded values. (3161)

  • Edit 2020-09-29: Added one more item to the “Notable fixes and improvements” section that was missed in the original version of this post.

    Beta 1 for the October release of WooCommerce is now available for testing! You can either download it directly from WordPress.org or install our WooCommerce Beta Tester Plugin.

    What’s new?

    The WooCommerce 4.6 release contains updated versions of WooCommerce Admin (1.6.0) and WooCommerce Blocks (3.4.0), fixes, and localization improvements.

    Notable fixes and improvements

    The main fixes and stability improvements in this release are:

    1. The Home Screen introduced in 4.3 which has previously only been the default for new stores (existing stores had to opt-in), will now be the default for all stores (#5108).
    2. The old setup wizard was removed, and now all new installs will go through the new setup wizard provided by WooCommerce Admin (#26853 and #27047).
    3. Sorting country names now works as expected for languages that use graphic accents (#27416).
    4. Style improvements to the notices when using the Twenty Twenty theme (#27387).
    5. It is now possible to assign to a product a tax class that contains non-ASCII characters (#27615).

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

    Filters and actions

    We have added new filters and actions:

    FiltersDescription
    woocommerce_return_to_shop_textFilter to change the label of the “Return to shop” button in the empty cart page.
    woocommerce_cart_item_required_stock_is_not_enoughFilter to change the behavior when checking stock for items in the cart.
    woocommerce_should_send_no_stock_notificationFilter to let developers skip the no stock e-mail for certain products.
    woocommerce_after_order_detailsAction to add extra data after the order details section.

    Database changes

    This release does not introduce any changes to the database.

    Release Schedule

    This version of WooCommerce will be released as per this schedule:

    VersionRelease
    BetaSeptember 19, 2020
    Release CandidateSeptember 29, 2020
    4.6 Final ReleaseOctober 13, 2020

    Testing

    As with the previous few releases, we have published testing instructions for 4.6 as well. We’d like to request that everyone help us in testing this release.

    If you discover any bugs during the testing process, please let us know by logging a report in GitHub.

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

    This release is mostly a fix release with a few notable bug fixes and a performance fix.

    Fixed issue with shopper saved payment method overriding default selected new payment method. With this bug if a shopper had a saved card for Stripe but selected a new payment method and left the default selected payment method option (that might not be Stripe depending on what order your store payment methods are configured in), then Stripe would be attempted for making the purchase instead of the payment method selected.

    Fix broken Cart and Checkout Block sidebar layout in some themes. We discovered that some Storefront child themes didn’t define box-sizing: border-box; for some elements, so we implemented a change that helps with more consistent Cart and Checkout display in those themes.

    Improve performance of Checkout block. Some browser environments (in particular Firefox mobile) exhibited significant lag with the checkout block interactions. In this release we implemented some improvements to component structure and implementation that dramatically improves performance.

    Remove hard-coded wp-login.php url. Rather than using a hardcoded path for the login link in the checkout block (when configured to show), we switched to using wp_login_url for generating this link. This exposes a login_url filter for stores that want more control over where shoppers login to the store.

    Fix an issue with COD not showing when first enabled. Some WooCommerce blocks users were sharing with us about not seeing the COD payment method as an option with the blocks when enabled. We finally tracked down why that was happening and fixed in this release.

    More automated tests added. This isn’t reflected in the changelog but I thought it’s worth mentioning that every release we’re increasing our automated test coverage of the blocks and critical flows to help surface problems quicker as we iterate on the blocks.

    Changelog

    Bug Fixes

    • Ensure shopper saved card is used as default payment method (default was being overwritten in some circumstances). (3131)
    • Fix Cart & Checkout sidebar layout broken in some themes. (3111)
    • Fix product reviews schema date fields to use new (WP 5.5) date-time format. (3109)
    • Use wp_login_url instead of hardcoding login path. (3090)
    • Fix an issue with COD not showing when first enabled. (3088)
    • Fix JS console error when COD is enabled and no shipping method is available. (3086)

    performance

    • Create DebouncedValidatedTextInput component. (3108)

    refactor

    • Merge ProductPrice atomic block and component. (3065)

  • This release fixes bugs introduced in WooCommerce 4.4.0 and an issue introduced in WooCommerce 4.5.0.

    In WooCommerce 4.4.0, we introduced functionality that was intended to improve the handling of variable products with the “filter by attribute” widget. (#26260) This pull request caused some additional issues with the handling of attributes that weren’t used with variations, and the count was still incorrect for products that were marked “hidden for catalog”. We’ve decided to roll back the changes to the “filter by attribute” widget and reintroduce them in a future version of WooCommerce. (#27625)

    We’ve also fixed an issue introduced in 4.5.0 which prevented “0” from being used as an attribute value for variations. (#27633)

    Here is the additional changelog for this release:

    * Fix - Revert the changes in filtering by attribute that were introduced in WooCommerce 4.4. #27625
* Fix - Adjusted validation to allow for variations with "0" as an attribute value. #27633

    Thanks to everyone for reporting these issues promptly and helping out with the fix release.

    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 any other issues in the WooCommerce core, please log them in detail on GitHub. Found a security issue? Please submit a report via HackerOne.

  • This release fixes a bug that was introduced with the 4.5.0 release.

    In 4.5.0, if you have “hide shipping costs until an address is entered” enabled in WooCommerce > Settings > Shipping > Shipping options, shipping was neither calculated nor added to the order for countries without a state required in the shipping address. (#27624)

    We’ve fixed the issue and added additional tests to better prevent similar issues from occurring in the future. (#27628)

    We highly recommend upgrading to this version, especially if you have “hide shipping costs until an address is entered” enabled in your settings.

    Here is the additional changelog for this release:

    * Fix - Check for state and postcode fields only if required in `show_shipping`. #27628

    Thanks to everyone for reporting this issue promptly and helping out with the fix release.

    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 any other issues in the WooCommerce core, please log them in detail on GitHub. Found a security issue? Please submit a report via HackerOne.