Changelog

Orders can have several statuses in WooCommerce; completed, processing, on-hold, pending to name a few.

In WooCommerce 2.1, statuses were associated with orders via a taxonomy called shop_order_status. The shop_order_status taxonomy is no more in 2.2.

Instead, 2.2 uses post_status for the order status. In terms of usage, this makes more sense – regular post statuses are of little use for orders (since when did you have a non-published order?). For performance, using post status has several benefits, particulary to queries and reporting which can now contain less table joins.

How does this affect developers? If you query shop_order posts via a get_posts() function, or DB query, you will need to modify your code to fully support 2.2. Otherwise you’ll either get a notice, or no results.

If you are calling get_posts() for the shop_order post type

Here is an example of a 2.1 order query:

$orders = get_posts( array(
        'post_type'   => 'shop_order',
        'post_status' => 'publish',
        'tax_query'   => array( array(
                'taxonomy' => 'shop_order_status',
                'field'           => 'slug',
                'terms'         => array( 'processing', 'completed' )
        ) )
) );

This query uses shop_order_status which will no longer work in 2.2 without throwing a notice. For 2.2 you’d change this to be:

$orders = get_posts( array(
        'post_type'   => 'shop_order',
        'post_status' => array( 'wc-processing', 'wc-completed' )
) );

If you wanted to get all orders, of any status, 2.2 has a function wc_get_order_statuses() which returns all registered order statuses:

$orders = get_posts( array(
        'post_type'   => 'shop_order',
        'post_status' => array_keys( wc_get_order_statuses() )
) );

If you are doing $wpdb queries on shop_order posts

Like above, you’ll need to change the taxonomy part of your query. Here is an example from 2.1:

$sales = $wpdb->get_var( "SELECT ID FROM {$wpdb->posts} as posts
            LEFT JOIN {$wpdb->term_relationships} AS rel ON posts.ID=rel.object_ID
            LEFT JOIN {$wpdb->term_taxonomy} AS tax USING( term_taxonomy_id )
            LEFT JOIN {$wpdb->terms} AS term USING( term_id )
            WHERE   posts.post_type     = 'shop_order'
            AND     posts.post_status   = 'publish'
            AND     tax.taxonomy        = 'shop_order_status'
            AND     term.slug           IN ( '" . implode( "','", array( 'completed', 'processing', 'on-hold' ) ) . "' )
        " );

In 2.2, this becomes:

$sales = $wpdb->get_var( "SELECT ID FROM {$wpdb->posts} as posts
            WHERE   posts.post_type     = 'shop_order'
            AND     posts.post_status   IN ( '" . implode( "','", array( 'wc-completed', 'wc-processing', 'wc-on-hold' ) ) . "' )
        " );

Direct queries on the database will need to be updated, or no results will be returned.

The WooCommerce 2.1.12 release is now available via WordPress.org or automatic update in your administration panel. Thanks to all of our contributors who’ve been helping out.

There are only a few changes in this release which can be found in the changelog. A total of 22 commits made it into this fix release.

(As always, the comments on this post are closed because this is not the right platform for support requests.)

The WooCommerce 2.1.11 release is now available via WordPress.org or automatic update in your administration panel. Thanks to all of our contributors who’ve been helping out.

There are only a few changes in this release which can be found in the changelog. A total of 6 commits made it into this fix release.

(As always, the comments on this post are closed because this is not the right platform for support requests.)

Whilst work continues on Prowling Pangolin, the team at WooThemes are still fixing bugs for 2.1 as they are reported. Today, the WooCommerce 2.1.10 release is  available via WordPress.org or automatic update in your administration panel. Thanks to all of our contributors who’ve been helping out.

All the changes are relatively small and can be found in the changelog. A total of 31 commits made it into this fix release.

Thoughts? Feedback? Tell us on the forums.

(As always, the comments on this post are closed because this is not the right platform for support requests.)

The WooCommerce 2.1.9 release is now available via WordPress.org or automatic update in your administration panel. This fix release is the result of the continued effort of our contributors who provided fixes and bug reports. Thank you for helping out!

All the changes are relatively small and can be found in the changelog. A total of 38 commits made it into this fix release.

One thing we did add for the devs out there was an option in System Status > Tools for disabling shipping method/rate caching. Useful when debugging shipping.

(As always, the comments on this post are closed because this is not the right platform for support requests.)

The WooCommerce 2.1.8 release is now available via WordPress.org or automatic update in your administration panel. This fix release is the result of the continued effort of our contributors who provided fixes and bug reports. Thank you for helping out!

All the changes are relatively small and can be found in the changelog. A total of 55 commits made it into this release, making this a decent fix release.

(As always, the comments on this post are closed because this is not the right platform for support requests.)

The WooCommerce 2.1.7 release is now available via WordPress.org or automatic update in your administration panel. This fix release is the result of the continued effort of our contributors who contribute code and others who have reported issues with the plugin. Thank you for helping out!

All the changes are relatively small and can be found in the changelog. A total of 73 commits made it into this release, bundling them into one larger release makes it a decent fix release.

(As always, the comments on this post are closed because this is not the right platform for support requests.)