WooCommerce 3.3.1 fix release notes

WooCommerce 3.3.1 is now available. This release fixes conflicts with a handful of themes running template files from 3.2.x that were thus incompatible with the 3.3.0 update.

You may have seen that 3.3.0 was removed from WordPress.org soon after release; this was to give the team time to look deeper into the conflicts being reported and avoid more users running into the same issues.

The issue affected themes with template overrides from 3.2.x that hadn’t been made compatible with 3.3. In general, we recommend that themes use hooks instead of template overrides. Themes such as Storefront (which does not use template overrides) were compatible at launch.

To resolve these issues, we selected a set of the most common themes running on WooCommerce stores and then tested for compatibility with the 3.3.1 release. In addition, some theme authors have tested and released updates to ensure compatibility as well.

Want to read about current best practices around templates and overrides? Read this wiki post.

This has been a learning experience for us, and has highlighted problems in the extensibility of the template system, and a disconnect between our team and theme authors operating on external marketplaces. We hope to find solutions to these problems in the near future.

We’re hopeful the majority of the problems are now resolved and we can push ahead. ~90 commits made it into this release. The full changelog is below.

* Fix - Added `woocommerce_output_product_categories` to replace `woocommerce_product_subcategories` function to prevent outdated theme template files from outputting categories on the shop and category pages in err.
* Fix - Prevented columns from being set to anything lower than 1.
* Fix - Added extra error checking in Webhooks API to prevent notices when deleting Webhooks.
* Fix - Prevented list table classes being loaded multiple times. This also fixes compatibility with Smart Coupons extension.
* Fix - Removed stray debug string from order email template and fixed some typos.
* Fix - Set up the loop when calling wc_get_loop_prop. Fixes compatibility with some themes.
* Fix - Remove multiple application of filter 'woocommerce_order_item_product'.
* Fix - Protect against theme support being defined too late. Fixes some issues with custom themes defining WooCommerce support incorrectly.
* Fix - Add fallback for themes that just get the pagination template.
* Fix - Made the on-the-fly image regen also regenerate missing sizes.
* Fix - Fixed missing user_id in webhook migration script.
* Fix - Allow uncategorized category to be sorted like the others.
* Fix - If theme support changes, we may need to flush permalinks since some are changed based on this flag.
* Fix - Fire hooks for pagination etc only when pagination is enabled.
* Fix - Default HTML in end wrapper template.
* Fix - Prevent regular pagination showing on archives for unsupported themes.
* Fix - Fix shop when shown as homepage in unsupported themes.
* Fix - Fix SKU mapping for placeholders during CSV import.
* Fix - Use CRUD search helper in admin products table so partial SKU search works.
* Fix - Fix bulk sale/regular price percentage handling.
* Fix - More specificity on smallscreen style override for columns.
* Tweak - Add notice for moved store notice setting.
* Tweak - Allow removing coupons on editable orders only.
* Tweak - Extended the background processing library to avoid changing methods in the library.
* Tweak - Do not show row settings if something is managing the number of products per page.
* Tweak - Allow devs to add 'no-link' class to elements to prevent order view link being triggered on row click.
* Tweak - Made woocommerce_resize_images filter more useful by calling it later.
* Tweak - Revert default columns back to 4 so it's consistent with 3.2.

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.

29 responses to “WooCommerce 3.3.1 fix release notes”

  1. InfiWebs Avatar

    Just updated to 3.3.1 from 3.3 and getting the following PHP warning all over the site –
    ( ! ) Warning: A non-numeric value encountered in /srv/www/dev/public_html/wp-content/plugins/woocommerce/includes/class-woocommerce.php on line 549
    Looks like this change is conflicting – https://github.com/woocommerce/woocommerce/compare/3.3.0…3.3.1#diff-c49e4a77afbd1a753435a745896942a2R742

  2. InfiWebs Avatar

    Thanks Mike 🙂

  3. Updated to latest and got a Whitescreen of death. Seems that 3.3.1 doesn’t work well with WooSubscriptions? I had to reinstall 3.2.6to get my site back running.

    1. Since a white screen isn’t useful to anyone, see if you have a server PHP error log for more details. We’ve not seen any issues with the official subscriptions extension yet.

      1. Ha — yeah you’re right. It looks like it was a plugin conflict. All good!

  4. Still broken on all Thesis websites.

    1. Not really enough detail to work with, and Thesis is premium. Maybe try their forums and see if they have a 3.3 update coming?

      1. You broke it on one of the most popular themes around and you’re telling them it’s their problem to fix it? Come on.

        1. The user above didn’t even specify the issue and this is the first time i’ve seen thesis mentioned by anyone. Log a ticket if there is a problem. This isn’t the place, and it’s not reasonable to expect us to purchase every premium theme out there because of one vague report. Thanks.

      2. Their theme author is working on a patch I believe. I went to their themes forum to discuss, several uses there trying to roll back. Thesis used to be very popular and so was catered for a lot but these days not so much.

        I am also having this same problem with sites running Genesis, Beaver Builder / Beaver Themer, yes another premium framework, I have also submitted a ticket with them to investigate.

        1. Genesis and genesis connect was one we tested (working) which also had a 3.3 patch shortly after.

          1. Perhaps the issue is with Beaver Builder / Beaver Themer instead then. I use Genesis as a base framework but yes I believe the templating for WooCommerce is handle within Beaver Builder / Beaver Themer. I will check in with them to make sure they are aware and working on something though I did see an update just, I see a couple of mentions of WooCommerce in there.

            1.1 – 02/07/2018

            Added The Events Calendar integration.
            Added Easy Digital Downloads integration.
            Added support for WPML translation of Themer layouts.
            Added support for Polylang translation of Themer layouts.
            Added enhanced select inputs with search for choosing layout locations.
            Added event ticket cost and cart button option to the posts module.
            Added [wpbb-if site:logged_in] conditional shortcode.
            Added [wpbb site:year format=“y”] shortcode.
            Added format parameter to the ACF date shortcode.
            Added value and expression parameters to conditional shortcodes such as [wpbb-if post:custom_field key=”my_key” value=”my_value” exp=”equals”]
            Added fl_theme_builder_woocommerce_template_html_{ $function } filter.
            Added expression support for ACF in wpbb-if shortodes.
            Added URL connections to the Posts module’s custom layout.
            Bug Fixes

            Fixed core templates being applied instead of Themer templates due to incorrect BB 2.0 support logic.
            Fixed issue where the incorrect layout renders on PHP7.
            Fixed empty archives not showing Themer layouts.
            Fixed featured image shortcode showing the size when it’s not needed.
            Fixed PHP warnings when editing a Themer layout and the preview doesn’t return a post.
            Fixed white label issues.
            Fixed misleading tooltip in Page Builder > Settings > User Access.
            Fixed incorrect Themer layouts showing in certain cases on PHP7.
            Fixed author image connection not working on standard builder pages.
            Fixed EDD info not showing in the posts module on standard pages.
            Fixed EDD pricing module text color being overridden by row/column text color.
            Fixed inconsistencies with EDD modules and field connections.
            Fixed event notice text color being overridden by row/column text color.
            Fixed event tickets module button colors not working.
            Fixed event archive not respecting the default view when editing Themer layouts.
            Fixed Polylang issue when using a different domain per language.

        2. Update from the DIYTheme Devs
          “Woo have screwed the pooch on this release and negatively affected a bunch of themes.
          “We’re looking into this right now; it’s pretty lame that they instituted a “non-WordPress standard” behavior on archive pages and are now expecting everyone else to adjust their stuff to accommodate them.
          “Just to reiterate: We are looking into this now (with a lot of disappointment that Woo have chosen to barge ahead with a known issue), but we do not have a specific timeline for a fix.
          “I will let you know when we have something that works for you.
          “For now, the solution is to roll back to WooCommerce 3.2.6 until you hear from us.”

          1. Nice choice of words there from DIYthemes… Feel free to let them know they can reach us over slack if they’d like to discuss or provide a version for testing.

  5. midmichmetal Avatar

    Since updating we now have the previous product and next product shown at the top of the store page and has disabled our breadcrumbs in the store area. Is there a way to disable showing the previous and next product?
    Example below.

    Thank you

    1. If your theme has template files for WooCommerce, ensure it defines WC support https://wordpress.org/support/topic/guide-for-declaring-woocommerce-support-in-themes/

      1. midmichmetal Avatar

        Okay thank you very much for the fast reply.

  6. For who are using self-custom theme and template overide same as me, add the woocommerce support will make it back to alive 😐 and sure, still need to modify a little more to make it back to your theme look. But at least it’s working
    function mytheme_add_woocommerce_support() {
    add_theme_support( ‘woocommerce’ );
    add_action( ‘after_setup_theme’, ‘mytheme_add_woocommerce_support’ );

  7. pearlpoppinwk Avatar

    Seems that 3.3.1 also screwed up international shipping. Even though i have international zones set up it just defaults to US and my international customers can’t order. None to happy here.

    1. I know it’s easy to put all problems to the update, but as there have been no other reports of shipping problems (I’ve seen) and no obvious changes to shipping, it’s unlikely to be related. Use the support area.

  8. Hi, after updating Woocommerce to version 3.3.1, I can’t find order status icon again in my orders list, how can I show them again ?

    1. Icons are replaced with text labels.

  9. Another issue, I can’t search by partial SKU in product admin, if my SKU = FAR-001 , when I enter 001 in the products admin search it’s not return any, but when I enter FAR it’s working.

    1. This is already known and will be resolved in 3.3.2. Use Github to report new issues, not the comments here. Thanks.

  10. Thea Sander Avatar
    Thea Sander

    I’m using the most recent version of Divi from Elegant themes. The Woocommerce 3.3.1 update caused all products to disappear from my shop. Actually all the elements disappeared (except for the fixed banner). I re-saved all the permalinks, but that didn’t fix it. I ended up successfully reverting back to version 3.2.6 of the plugin. I’ll submit a ticket.

    1. The developers of Divi are aware. Both WC and Divi have handling for the shop page (which us a custom post type archive) so we need to work out how both can play nice going forward, because this has been on ongoing source of problems.

      Will update https://github.com/woocommerce/woocommerce/issues/18915 when there is news. If anyone else has Divi questions I’d suggest they go there rather than post more comments here. This is not a support forum.

  11. Hi Mike,

    I’m having issues with the “Uncategorized” category since the update (see screenshot: https://cl.ly/1q0C1X0K1e3O/%5B0825f98c7cae02a97dbc8ee817aee696%5D_Image%202018-02-09%20at%2012.21.47%20AM.png. It attaches itself to the breadcrumbs and also showed up on the Products pages. I only have a handful of Products and the “Uncategorized” breadcrumb is unnecessary. Any way to disable this part of the breadcrumbs and hide the “Category: Uncategroized” at the bottom?


    1. You can rename the Uncategroized category, or assign the products to other cats. All products have a category in 3.3+