Woocommerce 3.0 broke our site

The update notice said to backup your database. So you will have to use the backup of the database pre-3.0 + the older version of WooCommerce. I don’t know another way to go back.

I think it was released before it was tested enough. I have been fighting errors all day without plugins and in 2014 theme as well as Storefront. I literally have a list of stuff I have found. I have yet to see anything “great” about 3.0, yet they took out the item line out of orders which was the nicest feature on the back end. Ugh…I KNEW I shouldn’t have messed with it.

• This reply was modified 7 years, 11 months ago by barbedhook.

I’m having lots of issues as well, it crashed my whole site ! I had it restored to the older version via FTP, but I’m still having countless errors and some plugins are not working now.

I don’t know what else to do, I’m waiting for a return from their support.

Same, noticing a lot of issues, not sure who tested this before deciding to push it live…

I did revert to my back-up and I am still having the same problems. Any other advice? I can not even activate an older version of woocommerce without fatal errors.

Problems here as well. I had to restore my database from a pre-3.0 backup, as well as revert to the previous version of the plugin. After the upgrade, I got the white screen of death on the front end until I ran the “database upgrade” pushed by the plugin on the backend. After that, my site’s functionality was restored, but it was clear that data had become corrupted somehow. I kept getting fatal errors about exhausted memory when I tried to load my product list, and certain products had attribute and variation data that just disappeared and seemed to create bugs. The data upgrade pushed by the plugin did very bad things! I hope the next release solves this issue.

• This reply was modified 7 years, 11 months ago by Kasia.
• This reply was modified 7 years, 11 months ago by Kasia.

Same here. I am receiving email after email of customers telling me they can’t check out or can’t access their download files, are reverted to a ‘internal error’ site, can’t process payment’ page etc.

I am also receiving the notice in my System Status that ‘your store is not using HTTPS’, which is not true. I have a SSL certificate activated. Please fix this. I am losing customers left and right every time a new update comes around. Hate it and am considering switching to Shopify.

i got the white screen of death font and back
it is looking like they took a page out of opencart’s playbook

Hey Folks,

White screen errors, or error 500s, mean *something* is causing a fatal error and stopping the page loading.

To find out what the actual error message is, see: https://www.ads-software.com/support/topic/how-to-debug-issues-after-updates/

Once you have this, it’s fairly easy to narrow down the cause and deal with it. But without knowing the error, it’s impossible to say. 99% of the time it will be an incompatible plugin, but if it’s not we can fix once you have the error message.

thank-you mike

it was a conflict with a plugin

i stand by my comment though,
check out prestashop’s forum right now, check out opencart’s forum
why is there a constant need to roll out unproven updates?

As with all updates, we do have a testing period in which we invite developers and users to try the new version. In the case of 3.0, as we explained in this post:

In total we had 4 beta versions for “2.7” from December; you can check out the Beta 1, beta 2, and beta 3 posts if interested. We then had a “2.7” release candidate before deciding to move to Semantic Versioning and use 3.0.0 instead.

So testing has been happending since December. In additon, we have a set of unit tests and end-to-end tests to catch general coding issues.

Even with all of that in place, it's difficult to account for 3rd party themes and extensions. If developers are following the dev blog they should have ample warning to work on compatibility.

We have seen however that some do not, and leave testing and fixes to the last minute, or worse post-launch. With that in mind, it's still important to check your extensions are compatible before updating. Testing extension compatibility is important, especially with MAJOR releases (2.x.x -> 3.x.x).

We have a guide on preparing yourself for updates here which you may find useful: How To Update Your Site

If you run into problems after updating, we also have a self-service guide with troubleshooting steps: WooCommerce Self Service Guide.

If you do work out that one of your extensions (or theme) is not compatible, first check to see if the developer has a compatible update out, and if not, ask them to release one. You can even pass them this wiki article which has migration steps.

thanks for the detailed reply mike

i was thinking how do you (woocommerce) get so many ducks in a row,
when some of the ducks aren’t yours (plugins/themes)

frustrating when it is recommended to always update wp for security,
then you just click update out of habit and not go a little deeper

good lesson for me

take care

Just wanted to add that after the 3.0.1 update, the automated database upgrade pushed by the plugin worked fine and I no longer experienced data corruption. Still working on sorting through the new version before I go live, but glad to see this issue was solved.