As you may have seen, 3.3.0 was removed from WordPress.org soon after release on Wednesday; this was to give the team time to look deeper into some theme conflicts being reported and to avoid more users running into the same issues.
The severity of the issue was relatively low, however, the volume of users running the impacted themes was potentially high, so we chose to take this safer approach.
The issue affected themes with template overrides from 3.2.x which 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.
If you’re unsure if your theme was affected, users have shared their experiences with various themes on the WordPress.org forum around this issue.
Why does WordPress.org list 3.2.6 and not 3.3.0?
To prevent further users downloading 3.3.0 as an automated update from WordPress admin, we reverted the stable version back to 3.2.6.
When 3.3.1 is released, the auto update will be available again for all users.
What should I do if I updated to 3.3?
If you’re running 3.3 already and your theme is compatible, you don’t need to make any changes.
If you have upgraded and saw issues with your theme, check to see if a compatibility update was released – these updates will likely fix issues on your site. For example, Genesis Connect for WooCommerce was affected and has since released a fix.
If you have upgraded, are seeing issues, and no compatibility updates have been released, you have three options:
-
- Just wait for 3.3.1 to be released officially: This path makes sense if you’re not too concerned about the issues you’re seeing.
- Update to our pre-release version of 3.3.1 available here: We only recommend this route if you’re comfortable with pre-release versions. More below on what’s already gone into 3.3.1.
- Downgrade to 3.2.6 using the WP Rollback plugin: We only suggest going this route if you’re seeing issues you’re concerned about and don’t want to take the risk of a pre-release version.
Aside from the theme issues mentioned above, 3.3 is looking pretty stable. We are running it ourselves on woo.com without problems, so please only downgrade if absolutely neccessary.
How do I install the pre-release of 3.3.1?
3.3.1-rc.1 can be found on GitHub.
- Download the new zip file.
- Unzip of your computer.
- Upload the
woocommerceplugin folder to your site manually following any of these instructions:
Using this pre-release or downgrading should not affect your WooCommerce data as long as you never ‘uninstall’ via admin.
What are you doing to resolve this issue?
To resolve the 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. We’ve already tested with more than 40 themes, and we believe 3.3.1 is relatively stable, but are taking the extra time to test more thoroughly.
The fixes already made to 3.3.1 can be found here on GitHub.
When will 3.3.1 be out?
Subject to our continued testing, we’re aiming to have 3.3.1 out early next week (the week of the 5th Feb, 2018). Any further updates or deviations from this will be added to this post as needed.
Thanks for your support.
37 responses to “WooCommerce 3.3.1 status update”
Great work!
> We’ve already tested with more than 40 themes
Do you have a list of the tested themes? (Personally, I’d be interested if Virtue / Virtue Premium is among them, would give me more confidence. But generally it would be of interest to many which themes serve as input for testing, also for transparency) A link to github or similar maybe.
Virtue is one of the ones we’ve looked at.
thank you for this explanation
Has Flatsome theme been tested with this?
We’ve checked the category issue is resolved, but afaik Flatsome authors themselves have not tested or released any 3.3 specific updates.
A new update for Flatsome is available from today which has all changes needed for WC 3.3. and 3.3.1
I had a full blow out on an Elegant Themes Divi theme. Thoughts?? I had to remove the whole woocommerce system from the site. It brought the site down.
Not really much I can say with that volume of detail. In testing, Divi is no affected by the bug we pulled 3.3 for, so it could be anything.
Mike, I did the update on my site and then there was no site, would not open anything, blank screen. I called the hosting company and they were able to get in. I was not able to get into the cPanel, but that was another issue. They turned off the woocommerce plug in and the site came back up. Once I got back into the system, I turned on woocommerce and the site again disappeared. I was able to get back in and deactivated the woocommerce plug in and the site was available. I did not make any modifications to woocommerce, just out of the box and added our information. I have not changed anything in the Store for over a year. Just normal updates. I can try to reinstall the woocommerce plug in and go from there.
Thank you.
Find the php error log if possible.
Will work on that.
Thanks!
We are using the Divi Theme and it is bady broken. We had a custom Shop page built using the DIVI builder and now all we have is a messed up product category page. The update also seems to have played total havoc with our WPML plugins and we have had to disable this completely.
Sounds like you’re still on 3.3.0 so follow the advice above. Divi theme already had a compat update. Thanks.
I also have a custom shop page built with Divi Builder — which broke upon updating straight to the 3.3.1 fix. That is, 3.3.1 is not fixing the problem.
Hi,
Start Directory theme are in your list?
No, we’re only going through the top themes according to our opt-in tracker data.
Ok!
I do the downgrade and i´ll wait for a stable version that works with Start Directory Theme.
Tks
Start Directory theme will need to add support for WC 3.3, if it doesn’t already. Not the other way around.
HI Mike,
I forward your message to GeoDirectory supoort, tks for explain.
Updated to 3.3.1 and using Storefront. No product images on single product page. Thumbs seem to be fine.
Also seeing:-
PHP Error: A non-numeric value encountered
Location = woocommerce/includes/class-woocommerce.php:549
Call Stack =
1. do_action(‘init’)
wp-settings.php:450
2. WooCommerce->add_image_sizes()
wp-includes/class-wp-hook.php:286
Think I’ve found the issue. 3.3.1 and Averta’s Master Slider Pro seem to stop product images. Disable the slider and all seems fine.
Still getting the PHP error though
Ideally hide warnings in production. You can hide it that way or with https://github.com/woocommerce/woocommerce/pull/18833 which will prevent it in PHP 7.1 if encountered.
Ok I think I got my self into a bit of trouble. I was having issues with the 3.3.0 upgrade so I downgraded to 3.2.6 with the WP rollback plugin, but now the my shop page won’t display any products. I even tried the Storefront theme and the problem still persists. I can see the products in other pages so they are there. Something seems to be broken with my store page now. I tried inserting short-codes, changing setting, using the tools under status and so on. I even upgraded back to the latest version but no luck. I deleted and reinstalled WooCommerce several times and no luck. There is a box in my shop stating: No product matching your selection? Can anyone please help me? Please I beg this is way beyond my skills 😦
Are you running this plugin? https://wordpress.org/support/topic/wc-3-3-1-no-products-showing-in-shop-with-woocommerce-products-per-page-plugin/ Post on the forum if stuck.
Yes I am running this plugin do you think that is the issue? But I have just deactivated it and the issue continues. Pardon my ignorance but what forum should I post on?
Wait it just got fixed! OMG thank you sooo much! And what is even crazy is that I am not having the issues I was having after the upgrade (with the categories showing in the shop page). THANK YOU!!
Using theme Timber v1.5.2
WP 4.9.4
Woocommerce 3.3.1
Single product images no longer show up, however product thumbnails are working. Also unable to remove the new zoom and gallery theme features via:
remove_theme_support( ‘wc-product-gallery-zoom’ );
remove_theme_support( ‘wc-product-gallery-lightbox’ );
remove_theme_support( ‘wc-product-gallery-slider’ );
Nevermind, found a workaround.
$img = wp_get_attachment_image_src( get_post_thumbnail_id(), ‘shop_single’ );
if( $img ) {
echo ”;
}
i have an issue with 3.3.1 and not displaying the shop. it was find with 3.2.6. is there any how to fix with my shop page. i use eleganthemes/divi. Thank you. https://www.korindotravel.com/shop/
Divi builder are working on a fix – the woocommerce class is being removed from the body. It’s required for styling.
Problems with layout of new order labels and content not aligning in 3.3.1. All plugins disabled and still the same errors. Running WP 4.9.4 and Porto Theme 4.1.5
https://imgur.com/a/T1X5f
https://imgur.com/a/IMRPd
I have an issue with a site that’s not using the correct template hierarchy after latest upgrade to 3.3.1, product category pages are not using the woocommerce archive page anymore (taxonomy-product_cat.php).
https://wordpress.org/support/topic/guide-for-declaring-woocommerce-support-in-themes/
Hi, I am seeing a lot of issues with 3.3.1,
I wanted to ask if this upgrade has been tested with the Brigsby theme.
I know is a long shot but I really know nothing about tech so I would appreciate the help on this one.
With the last upgrade 3.3.0 the only thing that I noted was that categories were appearing on the shop page… and couldn’t be removed
I downgrade and it was ok again, and now I want to do the last upgrade 3.3.1 but I am reading that there are being problems with pictures sizes and images disappearing… and when they try to downgrade again it isn’t possible…
I would love a recommendation on this, sorry if I am asking something that should be clear.
Help a lady in distress?? Thanks
The issue you speak of was the thing patched in 3.3.1. We’ve not tested with Brigsby, only the top 20 most popular. If it’s a WC theme really this should be tested by the author. Can you not try on a staging site for piece of mind?
For what it’s worth, I *was* able to successfully downgrade from 3.3.1.
Everything is not well with 3.3.1, depending on your theme — there remain serious problems with Divi, for example, which Divi is supposedly fixing — so I would check a Brigsby forum first, if I were you.
For future reference, this plugin has worked perfectly for me, for rolling back:
https://wordpress.org/plugins/wp-rollback/