Changelog

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

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

    Alongside this release we’ve also clarified the required WordPress and WooCommerce versions for Storefront, to align closely with WooCommerce Core’s L-2 policy.

    Here’s what’s new in 2.5.7 (pulled directly from the changelog):

    * Fix - Edit, reply and author icons are now displayed in comment list. #1319
* Fix - Updated font-weight of the All Products block so it matches the other product grid blocks. #1344
* Dev - Include FontAwesome brands icon set. #1345

    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.

  • It’s been a while since the last release of the WooCommerce Blocks but here we are with version 2.6.0 of the plugin! You can download this from GitHub or WordPress.org.

    Before getting into the changes included in this release, let’s highlight a few housekeeping items:

    We’re returning to a bi-weekly release of the plugin. This will help us get fixes and improvements out quicker for testing and previews so that we can respond to feedback quicker.

    Increased emphasis and positioning in communications around this being a feature plugin. Practically this means that while we aim for the feature plugin being stable for use on WooCommerce stores, it is also the source of bleeding edge features and blocks that we are considering for eventual inclusion in WooCommerce core.

    This effectively means that some new things that show up in the feature plugin might not land in WooCommerce core as is (or ever!) depending on the feedback and results from the increased exposure they get in the plugin release. However, we want to balance that with exposing previews of in progress work so that stores, merchants, and extension developers can try them out and provide us feedback to help inform the direction we take.

    We hope this improved messaging helps guide stores and merchants with making the appropriate decisions for how they use this plugin in their stores.

    With that out of the way, let’s get on to what is packed in this release!

    (more…)

  • We’ve got a few fixes from last week’s WooCommerce 4.1.1 release to include in our release candidate this week. We are still on track for our planned June 2nd release next week!

    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!

  • WooCommerce 4.1.1 is now available! This is a fix release that contains some security improvements for downloadable files and other minor bug fixes.

    Here’s the change-log for this release:

    * Enhancement - Added notice about public uploads directory. #26207
* Tweak - Disallow directory listing in woocommerce_uploads when "Redirect only" is the selected download method. #26399
* Fix - Added correct handling of nonces to database update notice dismissal. #26500
* Dev - Updated WooCommerce admin version to 1.1.3 and Action Scheduler to 3.1.6.
* Dev - Add prop `isEnabled` and a function to dynamically enable tracks. #26493
**WooCommerce Admin**
* Tweak - Onboarding: Add Jetpack flow back to onboarding profiler. #4382
* Fix - Respect tracking opt-in before new page load. #4368
**ActionScheduler**
* Fix - Shutdown deprecated notice changed to a warning when as_* functions called without data store initialization. #546

    We highly recommend updating WooCommerce to this version as soon as possible.

    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.

  • After having had a very smooth beta thus far, we are excited to announce that the release candidate is now available!. We are currently on track for our planned June 2nd release date.

    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!

  • Hello everyone,

    Starting with the release of WooCommerce 4.2, we will be switching to a monthly release cadence! We’ve worked hard over the last year to increase both the frequency and stability of our releases, and we feel confident in taking this next step.

    As of today, WooCommerce 4.2 is available for beta testing. You can either download it directly from WordPress.org or install our WooCommerce Beta Tester Plugin.

    What’s new in 4.2?

    As with our previous release, we have been continuing to focus on stability and performance in this cycle. You can review our changelog for the granular details, but here is a broad overview of what’s new:

    WordPress Support Policy

    Starting with the 4.2 release, we will adapt an L-2 sliding window support policy. What this means is that we are committed to ensuring that WooCommerce Core will work with the current WordPress version, as well as the two previous release branches.

    You can read more about this new policy on our developer blog post.

    New Hooks and Functions

    We’ve added one new hook in this release:

    FilterDescription
    woocommerce_menu_order_countEnables filtering for the count of processing orders shown in the menu.

    We’ve also made some changes to a few hooks:

    FilterDescription
    woocommerce_matched_ratesAdded the customer as a third argument.
    woocommerce_attribute_labelFixed a bug that caused the prefix of global attributes to be removed from the second argument.

    Release Schedule

    Here are our targets for the 4.2 release cycle:

    VersionRelease
    BetaMay 12th
    Release CandidateMay 19th
    4.2 ReleaseJune 2nd

    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.

    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!

  • When it comes to policies regarding support for previous releases of a project’s dependencies, it is important to strike a fair balance between progress and stability. As we look to increase the performance and reliability of WooCommerce, it is necessary that we clearly outline exactly what that policy is, as well as our goals in creating it.

    Starting with the 4.2 release, we will adapt an L-2 sliding window support policy.

    What this means is that we are committed to ensuring that WooCommerce Core will work with the current WordPress version, as well as the latest release from the two previous release branches.

    As an example, when WooCommerce 4.2 is released, it will officially support:

    • WordPress 5.4.1 (the most recent version of WordPress),
    • WordPress 5.3.3, and
    • WordPress 5.2.6 (from the two previous release branches).

    We’d like to outline the three major factors that played a role in this decision, so that everyone can better understand the context behind it.

    Testing Surface

    Over the last year our top priority has been stability. This does not come without a cost, and a great deal of work has gone into thoroughly testing every release. In order for us to be as confident as possible in shipping, we need to make sure that WooCommerce works on every version of WordPress that we support.

    If we try to support too many versions at once either the quality of the testing or the frequency of the releases will suffer. As we view neither of these to be an acceptable loss, we need to adopt a predictable support policy.

    Security & Fixes

    Given the kind of platform WooCommerce is, there is an increased scrutiny in ensuring that shops are secure and stable. The hope is that by more aggressively encouraging users to update, we avoid enabling stragglers that may be unknowingly leaving their shops open to attack.

    Features & Enhancements

    Each successive release of WordPress Core carries with it new features and enhancements that enable us to deliver the best experience to merchants. While in many cases we can use progressive enhancement to enable features in specific versions, the larger the minimum version margin becomes, the more significant the maintenance burden. We feel that this sliding window is large enough to be maintainable while still enabling us to take advantage of the new features.

    We hope that you’ll join us in moving forward with the WordPress platform, and in helping keep all sites running WooCommerce up to date with the latest, greatest, most secure software available.

  • We are very excited to announce that WooCommerce 4.1 is generally available now. It has been in development since March 2020 and has about 400 commits from 28 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. See this guide for more details.

    What’s new in 4.1?

    This release contains lots of performance improvements and stability fixes. Along with these improvements, these are the major features being shipped with 4.1:

    (more…)

  • Storefront 2.5.6 has been tagged for release and uploaded to WordPress.org. This is a small release focused on maintenance and compatibility fixes.

    Here’s what’s new (pulled directly from the changelog):

    - Enhancement - Custom site background color is now used in editor preview. 
- Fix - Ensure mobile sticky footer navigation links are visible when colours are customised (use header/nav colour scheme, consistent with 2.5.4 and earlier releases). 
- Fix – Fix issue where product and category images were not centered on homepage & category pages. 
- Fix – "Reveal password" button (eye icon) is now positioned correctly in new password fields (my account change password and signup). 
- Fix - Fix several mispositioned :focus rings (in Firefox and other browsers). 
- Fix – Ensure product images have appropriate bottom margin. 
- Fix – Buttons blocks now respect the border radius set by the user. 
- Fix - Buttons blocks now respect the border radius set by the user. 
- Fix - Buttons blocks no longer show an underline. 
- Fix – Product page, cart, and checkout layout fixes affecting stores with longer product names on smaller screens. 
- Fix - WordPress 5.4 compatibility – Text inside the Calendar block is now centered, in line with the Calendar widget. 
- Fix – WordPress 5.4 compatibility – Ensure block editor uses theme typography styling. 
- Fix – WordPress 5.4 compatibility – Adapt block editor width if sidebar widgets are present/disabled. 
- Compatibility - Disable the footer bar when used with Checkout or Cart blocks (currently in development). 
- i18n – Use correct direction arrow icons in RTL languages (next, previous and forward). 
- i18n – Fix inappropriate use of disambiguation context in admin notice 'or' string. 
- Tweak – Improve HTML5 compliance for enqueued scripts and styles. 
- Tweak – Removed unnecessary vertical-align css rule for button, select, input and textarea elements. 
- Dependencies – Update Font Awesome icon font to 5.13.0.

    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.

  • We have published another Release Candidate for WooCommerce 4.1 and we invite everyone to test out before final release on May 5. This release includes an updated fix version of WooCommerce Admin and Action Scheduler, along with some minor fixes.

    See this PR for list of commits that we cherry-picked for this release.

    Testing

    To test, you can use our beta tester plugin or download the release from wordpress.org directly.

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

    Thanks to all the testers and contributors!