Develop WooCommerce

The official WooCommerce development blog

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 WPEnginge 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.

WooCommerce 3.6 has arrived! — April 17, 2019

WooCommerce 3.6 has arrived!

Today we are excited to announce the availability of WooCommerce 3.6. The latest release of WooCommerce has been in development since November 2018, and during that time, 3.6 has had 2279 commits from 122 contributors.

3.6 is a “minor” release; this version should be backwards compatible with sites running versions of WooCommerce greater than or equal to 3.0. We do of course recommend ensuring your extensions and themes are compatible before upgrading, and making backups for peace of mind —please see this guide for more details.

Continue reading
WooCommerce 3.6 RC3 — April 16, 2019

WooCommerce 3.6 RC3

Greetings all! WooCommerce 3.6 RC2 was released last week, and since then a few small bugs have been discovered. Also with the security updates released in 3.5.8 today – we wanted to bundle up one last Release Candidate prior to the official planned launch of WooCommerce 3.6 tomorrow – April 17th.

What’s New

In addition to the security fixes in 3.5.8 – the following items have changed since RC2:

  • Fix: Product search may fail to return valid results when using the ‘include’ flag to search within a limited set. #23246 Props @franticpsyx
  • Dev: Update Action Scheduler library to 2.2.4 #23306 Props @JPry
  • Fix: Logic in link all variations #23304
  • Fix: Remove total revenue from usage tracking #23302
  • Fix: error in /wc/v2/system_status endpoint #23295
  • A11y: Change aria-labelledby to aria-label on quantity input #23186 Props @zacchaeusluke
  • A11y: Updates to labels in checkout #23303 Props @pojke
  • Fix: Replace update_woocommerce_term_meta with update_term_meta #23308 Props @webdados

Testing

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

Since 3.6 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.

Developers, 3.6 is a minor release, so it should be fully backwards compatible. Despite this, it’s still a good idea to test your plugins and themes and help us catch any issues we may have missed before the final release.

WooCommerce 3.5.8 security release —
WooCommerce 3.6 RC2 — April 10, 2019

WooCommerce 3.6 RC2

On March 28th we announced the availability of the first Release Candidate for WooCommerce 3.6. During the RC1 testing period, a number of bugs were reported by RC testers in the community, and during additional internal testing. As such we just published a second release candidate for WooCommerce 3.6. To see all the new features being shipped in 3.6, please check out the Beta 1 post for all the details.

Due to the addition of a second Release Candidate, we are anticipating the final release of WooCommerce 3.6 to happen on April 17th. We apologize for the added delay to this release cycle. Our number one priority is to ship a stable release, and we believe the extra time is needed to deliver on that priority.

What’s New

In addition to the changelog and feature list that was included in the Beta 1 Announcement – the following items have been fixed since RC1:

  • Fix BC break by allowing wc_product_gallery to be called without any arguments. props @superdav42 #23191
  • Fix strpos arguments order #23175 props @quasilyte #23175
  • Fix results from wp_term_counts when sorting by menu_order #23194
  • Fix: backwards compatibility issues for wc_get_template function #23197
  • Fix: Remove end date for Facebook in on-boarding wizard #23210
  • Fix: Usage tracking logic. #23231
  • Fix: Prevent removal of the wc- prefix from non core order statuses #23203
  • Fix: For conflicting webpack build processes #23244

Marketplace Suggestions and Usage Tracking Feedback

Beyond the fixes listed above, we also made some changes to the Marketplace Suggestions feature. It is often only when the release candidate actually comes out that we get certain kinds of feedback. Thanks to the many developers, end users, and the plugin review team for all their help.

Now, with the 3.6 RC1 live, we have specific feedback from the community and plugin review team that we can take into consideration and act on:

  • Fix: Remove Product Listing suggestions. #23211
  • Fix: Add setting to turn off Marketplace Suggestions #23218
  • Fix: Add icon to Product Metabox Suggestions #23230
  • Fix: Add link to manage Suggestions #23229
  • Fix: Update text explaining opt-out and details of usage tracking. #23216

Testing

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

Since 3.6 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.

Developers, 3.6 is a minor release, so it should be fully backwards compatible. Despite this, it’s still a good idea to test your plugins and themes and help us catch any issues we may have missed before the final release.