Woocomerce new version is not ready for production

All 3 of the issues mentioned are already addressed as you can see the sticky post at the top of this support forum.

Please go through those to get your answers.

Sorry,I have no time to read hundred of post in the time the site is down .
Do you think I like experiments in a production site?
Great mistake, I don’t like it at all. I repeat again this release is an experimental code joke with nonsense.
I updated Drupal Commerce with a lot of dev modules and customizations and never fails like this Woocommerce release that is only one plugin with a theme doing by the same people.
Please give us a better update process for Woocommerce, everybody appreciate it.

This seems like a deliberate attempt to ruin peoples current themes and make them switch to a WooTheme…seems like everything has to work around WooThemes instead of it working around everyone else’s wordpress themes?

I agree – one update from one plugin causes so much grief for so many people – WooCommerce is a great plugin but this update release is a complete mess.

As cesarmenes says – we don’t have time to test everything every single time a plugin has an update. Perhaps if it’s labelled as a major release, perhaps.

Please WooCommerce – make sure your releases aren’t going to cause so much time wasting for so many people just fixing things that shouldn’t be broken.

I found the combination of the woocommerce update and WP Minify REALLY screwed layout up. I deactivated wp minify and all is good with theme compatibility.

I think the lesson to learn here is they should still keep the old version updated (i.e. 2.0.20) for a while (e.g. 6 months) instead of forcing everyone to upgrade to a version which has so much incompatibilities. Actually this also happened during the upgrade from 1.6.x to 2.0, but of coz this time is more serious.

@tszming so you don’t think a 3 month beta period is enough time for developers to get their products checked, after countless announcements and and completely open development cycle? BS. What you are suggesting just delays the problem.

Please can anyone tell me how I can reinstall 2.0.20 without loosing data (such as products)?? The update 2.1.1. was a major mistake ?? lots of bugs.

@mikejolley, I fully understand you guys are under super high stress during the 2.1 release but I am not complaining anything to you (did I?) as I know it is just an opensource and FREE project, what I am suggesting is a more conservative release approach – maintaining the legacy version for a while after the new version is officially released (not beta) and keep old version fixed for critical bug/security, lot of other software projects release like this.

The reason why stability is important because people count on WC to make money, and this is the reason why some people are very angry since they think 2.0 to 2.1 is a minor upgrade but then their site are broken. I am not saying they don’t have the responsibility, but there are ways to give them less surprise, otherwise people will leave WC eventually.

Disclaimer: I am not affected by 2.0 to 2.1 upgrade, so there are no reason I am angry, just my two cents ??

@tszming The thing is, even if we maintain a .20 branch, WP still offers updates. People will still upgrade and run into issues with themes/plugins not being updated. So really, keeping .20 going for longer makes no difference in the real world, even if maintained.

And @mvdw don’t hijack other peoples topics. As long as you don’t click ‘uninstall’ you won’t lose data. Install the old version via FTP.