Develop WooCommerce

The official WooCommerce development blog

WooCommerce Admin v0.15.0 — July 13, 2019
WooCommerce Admin v0.14.0 — July 2, 2019
WooCommerce Admin v0.13.0 and Revised Merge Plans — June 19, 2019
WooCommerce Admin v0.12.0 release notes — May 17, 2019

WooCommerce Admin v0.12.0 release notes

We are happy to announce the availability of a new build of the WooCommerce Admin feature plugin! If this is the first time you have heard about WooCommerce Admin, it is a new JavaScript-driven interface for managing your WooCommerce stores that is focusing on creating new and improved reports, and a dashboard to monitor all the important key metrics of your site. You can read more about the background of the project in our Alpha announcement post – or watch the keynote from WooSesh.

Continue reading
WooCommerce 3.6.1 release — April 18, 2019

WooCommerce 3.6.1 release

Greetings all once again! While WooCommerce 3.6 was just launched less than a day ago, we received reports via GitHub and the Support Forums that some of the new functionality shipped in 3.6 was causing issues with some hosting environments.

As such, we have opted to revert the code that was determined to be causing issues back to the version that exists in 3.5.x. We have taken that one revision, and packaged it up in version 3.6.1 to allow sites affected to easily apply the fix.

3.6.1 Changelog

With just one pull request shipped in this fix release, the changelog is quite short:

* Fix - Remove calls to 'header_register_callback' to prevent conflicts with some hosting providers and PHP versions.

This change will fix the issue users on WPEngine hosting were experiencing on logging in to wp-admin, and remedy the issues reported around add-to-cart URLs in 3.6.

Download the latest release of WooCommerce here or venture over to Dashboard → Updates to update your plugins from WordPress.

As usual, if you spot any other issues in WooCommerce core please log them in detail on Github, and to disclose a security issue to our team, please submit a report via HackerOne here. Comments on this post are closed.