WooCommerce 4.4 Release Candidate

After releasing the beta version last week we found a few issues that needed fixing. We squashed these and made a few other improvements as well, therefore, we are moving ahead according to the plan and are excited to announce that the release candidate is now available! We are also on track for our planned August 18th final release date.

Fixes and improvements

  • The fix for the visibility of partially out of stock variable products when using the layered nav widget (#26260) was a somewhat complex change that broke a couple of things in the beta, these have been sorted out in the RC (#27190, #27175, #27166).
  • We have added/updated documentation of some deprecated functions (#27054).
  • We have updated WooCommerce blocks yet again to a new version offering further improvements.
  • We have fixed a couple of issues that surfaced when using the upcoming version 5.5 of WordPress: removed new meta box arrows (#27173) and fixed the “product type” dropdown from product’s data meta box (#27170).
  • After clicking to update WooCommerce, the user will now stay in the same page instead of being redirected to the “Settings” page (#27172).
  • Improved order details UI to highlight “Paid” and “Net Payment” sections (#27142).
  • We removed the JETPACK_AUTOLOAD_DEV define (#27185).


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!

6 responses to “WooCommerce 4.4 Release Candidate”

  1. I have kind of got out of the loop with WooCommerce Blocks. I have had the plugin installed for a while and I use it to display specific ‘hand picked’ products on certain pages – such as the home page. I have not used it for the cart page, for example.

    I just went to look at the improvements to the plugin that you mention here in your post, and I see it says “Use this plugin if you want access to the bleeding edge of available blocks for WooCommerce. However, stable blocks are bundled into WooCommerce, and can be added from the “WooCommerce” section in the block inserter.”

    That leads me on to my questions, which are:
    1. Which are the ‘stable blocks’ that are built into WooCommerce now?

    Assuming that ‘hand-picked’ products are ‘stable blocks’ – what would happen if I were to deactivate the WooCommerce Blocks plugin?

    1. Peter Fabian Avatar
      Peter Fabian

      Hi David,

      Great questions, thanks! We recently recognized this problem ourselves, so the Blocks team is currently deciding on the best way to communicate this to the customers. Generally speaking, blocks that are active with WooCommerce core are considered stable, the ones that are only available when you install a separate plugin are more experimental.
      So if you want a stable Blocks experience, I’d recommend using those available with WooCommerce core. If, on the other hand, you’d like to use some of the Bloakcs that are going through more rapid development (like Cart and Checkout blocks), feel free to install WooCommerce Blocks plugin.

      Hope it makes sense.

      1. Thanks. I deactivated the Blocks plugin and everything still worked because the features I was using are now in the WooCommerce plugin. The next step is to activate the plugin on a test site and find my way around the Blocks for the cart.

        1. Peter Fabian Avatar
          Peter Fabian

          Sounds like a good plan. Please let us know if you run into any problems!

  2. Hi

    Any news on this blog item?


    Great performance but not working 100% with the REST API.

    1. Peter Fabian Avatar
      Peter Fabian


      We don’t plan to work on this immediately. We’d be happy to accept community contributions, though.

Leave a Reply

Your email address will not be published. Required fields are marked *