With WooCommerce 4.0 now comfortably behind us, it’s time to begin our next release cycle.
What’s new in 4.1?
The primary focus of this minor release is stability and performance. If you’d like to dig into the details, take a moment to review the changelog for a more granular breakdown of everything included. In addition, keep an eye out for another blog post soon containing developers notes for this release.
Here’s a broad overview of what’s new.
New Setup Wizard
With this release we’ve finished our roll-out of the new setup wizard. All new shops will be directed through this new setup flow, so if you haven’t checked it out yet, you should!
This release requires a database update, as we’ve added a new table to the WooCommerce database structure. This table is critical to processing orders and checkout and is installed automatically after updating.
Nudge for WordPress Version
Note that there is no change in the minimum requirements for this version.
However, sites not currently running on WordPress 5.2 will see a notification to upgrade to the latest and greatest. Why?
In WooCommerce 4.2, the next release, we are scheduled to update the minimum version of WordPress to 5.2 (now 5.0) to keep up with changes in the WordPress ecosystem.
New Hooks and Functions
We’ve added several new hooks and functions in this release:
|Returns an array of all registered currency symbols|
|Before an email is run through emogrifier|
|Prevents stock from being increased by refunds|
|Enables filtering of the location that an order should be taxed for|
|Allows for filtering of the heading text for product upsells|
Template File Changes
The following template file has been updated:
|Wording of this notice|
Here are our targets for the 4.1 release cycle:
|Release Candidate||April 21st|
|4.1 Release||May 5th|
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.
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!