WooCommerce Core

WooCommerce 2.7 Release Candidate

The release candidate for WooCommerce 2.7 “Bionic Butterfly” is now available!


Shipping a release candidate (RC) means we think we’re done, but with hundreds of thousands of stores and so many plugins and themes which declare WooCommerce support, it’s possible we’ve missed something. We hope to ship WooCommerce 2.7.0 on Tuesday, March 14th but we need your help to get there!

To test WooCommerce 2.7 RC1, you can use our WooCommerce Beta Tester plugin or you can download the release candidate here (zip).

Since 2.7 is now in release candidate stage, only bug fixes will be made. No other changes should take place.

Think you’ve found a bug? Please post in detail to Github.

For more information about what’s new in 2.7, check out the Beta 1beta 2beta 3 blog posts. We also have some compatibility example posts and posts about our new features:

If you haven’t tested WooCommerce 2.7 yet, now is the time!

Developers, please test your plugins and themes against WooCommerce 2.7 as soon as possible. If you find compatibility problems, we never want to break things, so please be sure to post to Github so we can figure those out before the final release. You may also be interested in our known-issues wiki article here.

You’ll also find some new docs on things such as the CRUD in the WIKI here.

And if you’re a theme developer and want to enable the new gallery, see here.

Translators, it is important than we translate 100% of the WooCommerce 2.7 strings so translations are downloaded automatically on update. Your help is most welcome!

Store ownersread this helpful guide on preparing for the update and if you see any deprecation notices after updating don’t be alarmed; read here.

By Mike Jolley

Mike Jolley is a tech hobbyist, astrophotographer, retro gamer, and software engineer who works at Automattic and contributes to open-source projects such as WordPress and WooCommerce.

9 replies on “WooCommerce 2.7 Release Candidate”

The RC1 release download contains a _MACOSX system folder. Don’t expect that’s really a problem unless it is actually present in the github repo tree somewhere.


Comments are closed.