Develop WooCommerce

The official WooCommerce development blog

Storefront 2.5.3 release notes — August 19, 2019

Storefront 2.5.3 release notes

Storefront 2.5.3 has been tagged for release and uploaded to

Here’s what’s changed pulled directly from the changelog:

* Fix - Introduce extra block styles to fix issue with WooCommerce 3.7 blocks.
* Fix - Make Storefront admin notices conform to new theme rules.
* Dev - Add filter to alter credit links.

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

As usual, if you spot any other issues, please log them in detail on Github.

Storefront 2.5.2 was released earlier today, but due to a mistake in the release process, it contained an additional and unused directory. As soon as we noticed the error, we released Storefront 2.5.3 to remove the directory and replace version 2.5.2. Users that updated to 2.5.2 won’t experience any issues.

WooCommerce 3.6.5 security release — July 2, 2019
WooCommerce 3.6.4 — May 27, 2019
WooCommerce 3.5.3 release notes — December 20, 2018

WooCommerce 3.5.3 release notes

WooCommerce 3.5.3 is now available. This patch release fixes an issue affecting stores running WordPress 5.0.2. This new version of WordPress was released yesterday, and changed the default value of a few variables. This modification caused the WooCommerce orders list table displayed in WP Admin to break. More information on this bug can be found in this WordPress core ticket, as well as this WooCommerce issue.

1 commit made it into this release and the full changelog is below.

* Fix - Fix orders list table in the admin after a change introduced in WordPress 5.0.2. #22273 

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.

Performance: Switching to post_author to store order customer IDs — January 15, 2018

Performance: Switching to post_author to store order customer IDs

WooCommerce core uses a post meta called _customer_user to store the customer ID for orders. Since the meta_value field of the wp_postmeta table is not indexed, this means that all the queries that need to filter orders by customer ID are very slow.

To address this, in PR #17895, we are exploring the idea of using post_author, instead of a post meta, to store the customer ID. _ customer_user will still be populated to preserve backward compatibility.

This change will significantly improve the performance of queries that need to filter orders by customer ID.

On a test database with about 2.5 million entries in the wp_posts table and about 100 million entries in the wp_postmeta table running on a local dev machine, the query used by WC core to filter orders by customers in admin dropped from 25 seconds when using _customer_user to 0.0008 seconds when using post_author. Those numbers were retrieved using the plugin query-monitor and the two different queries can be seen in the screenshots below.

Query using _customer_user:

Screenshot from 2018-01-10 16-01-42

Query using post_author:

Screenshot from 2018-01-10 15-53-57

Although WC core doesn’t use the post_author field for orders, before merging this change, we want to make sure that it won’t break any existing extensions that could be using post_author for something else. Hence this post to share our plan with the community and ask for feedback.

Please let us know of any concerns you might have in the comments below or directly in the PR. If there are no objections, we plan to ship this change in WooCommerce 3.4.