Changelog

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.)

The WooCommerce 2.1.6 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 91 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.)

In the 2.1.4 version we introduced a bug that caused the prices of variations to be hidden when the manage stock field was left empty. Sorry about that. This and a couple other small bug fixes are now available in the WooCommerce 2.1.5 release, available via WordPress.org or automatic update in your administration panel.

You can find the critical bug fix in the commit details, or the relevant issue on our tracker.

Just 14 commits in total went in this release, which makes it a really small fix release, but as it solves a big bug we decided to push it out immediately. All the changes can be found in the changelog.

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

We’re still improving the stability of the new WooCommerce 2.1 version since its release and as a result of that, we’ve just made the WooCommerce 2.1.4 fix release available on WordPress.org. You can now also update directly from your WordPress dashboard.

A relatively small set of 44 commits introduces the following fixes (among others):

• We’ve fixed the display of nested categories in the Product Categories widget properly this time, after failed previous attempts. The “Only show children for the current category” option now works as expected.
• The loading of the translation files has been reversed after experimenting with this change in past releases. Read the full scope of this change in issue #5092. We’ve also reversed the loading of bundled translation files and the ones users can use to override (commit details).
• The bug where the horizontal axis of some reporting graphs didn’t work as expected is now fixed. This only happened with large date differences, where we found the limits of integers. 🙂

This fix release will make the WooCommerce 2.1 branch as stable as possible right now and we’re all set to start making scope decisions on what we’re going to do in WooCommerce 2.2.

You can find the full changelog of this release on WordPress.org and review all the changes on GitHub.

Report any issues found

In case you find new issues, please let us know via the GitHub repository issues if it’s a core issue, or make a new support topic on the WordPress.org support forums.

Our list of common issues after updating to WooCommerce 2.1 will still be actively maintained, so please keep an eye on announcements there and via our @DevelopWC Twitter account in case you are still waiting for an issue to be resolved. Thanks for your continued patience.

(The comments on this post are closed because this is not the right platform for support requests. Please use any of the appropriate platforms mentioned in this post.)

Please note that WooCommerce 2.1.4 is available already.

We’ve been continuously improving the stability of the new WooCommerce 2.1 version since its release and have just made the WooCommerce 2.1.3 fix release available on WordPress.org. You can now also update directly from your WordPress dashboard.

A total of 133 commits make this a fairly large fix release and introduces the following fixes (among others):

• There was a bug in our queries that broke a lot of the searches for orders in the administration panel. Not only is this bug now fixed, but it will also improve the performance for those search queries.
• The REST API has received a couple fixes. It has been used in a lot of different setups now and this fix release greatly increases stability.

The other fixes in this release are fairly small, but have been put together in one larger fix release that should make the WooCommerce 2.1 branch as stable as possible right now. You can find the full changelog on WordPress.org and review all the changes on GitHub.

Report any issues found

In case you find new issues, please let us know via the GitHub repository issues if it’s a core issue, or make a new support topic on the WordPress.org support forums.

Our list of common issues after updating to WooCommerce 2.1 will still be actively maintained, so please keep an eye on announcements there and via our @DevelopWC Twitter account in case you are still waiting for an issue to be resolved. Thanks for your continued patience.

(The comments on this post are closed because this is not the right platform for support requests. Please use any of the appropriate platforms mentioned in this post.)

Please note that WooCommerce 2.1.3 is available already.

We’ve been continuously improving the stability of the new WooCommerce 2.1 version since its release and have just made the WooCommerce 2.1.2 fix release available on WordPress.org. You can now also update directly from your WordPress dashboard.

A total of 42 commits in the past day and half introduces the following fixes (among others):

• Removed manual checks for AJAX requests, relying on DOING_AJAX constant now. This will solve the issues some people were having on MediaTemple hosting, where permission errors showed up randomly or administration panels and menus were not loading.
• Update schemas before DBDELTA to fix mysql errors on update. This resolves database errors some users were experiencing during the update to WooCommerce 2.1.

You can find the full changelog on WordPress.org.

Report any issues found

In case you find new issues, please let us know via the GitHub repository issues if it’s a core issue, or make a new support topic on the WordPress.org support forums.

Our list of common issues after updating to WooCommerce 2.1 will still be actively maintained, so please keep an eye on announcements there and via our @DevelopWC Twitter account in case you are still waiting for an issue to be resolved. Thanks for your continued patience.

(The comments on this post are closed because this is not the right platform for support requests. Please use any of the appropriate platforms mentioned in this post.)

Please note that WooCommerce 2.1.2 is available already.

In the past 48 hours, we’ve smashed a total of 57 commits in the now available WooCommerce 2.1.1 fix release. The new version is now available and can be downloaded from the WordPress.org repository, or updated via the automatic updates in your WordPress install.

Among other fixes, this release includes:

• All endpoints, shop pages, category pages and other pages resulting in 404 errors after the 2.1 update will now have their permalinks flushed correctly. This solves all the issues with pages not loading.
• Fixed all language country codes to reflect WordPress standards, so all translations will work again.
• Fixed issues where stock status wasn’t properly set so new products didn’t show on archive pages.
• Fixed when add_to_cart is called, ensure the correct product_id is set for variations.

The full changelog can be found on WordPress.org.

Showing outdated bundled templates files in themes

We have also introduce a notice that will show in your administration panel when your theme is bundling outdated WooCommerce template files. This problem causes a lot of trouble for webshops using third party themes. This list of outdated template files will enable you to quickly find the template files that might cause issues and give you a clear list to communicate to the developer of your theme.

Report any issues found

This fix release solves the most important and annoying issues for our users and makes it easier to detect outdated templates in themes. In case you find new issues, please let us know via the GitHub repository issues if it’s a core issue, or make a new support topic on the WordPress.org support forums.

Our list of common issues after updating to WooCommerce 2.1 will still be actively maintained, so please keep an eye on announcements there and via our @DevelopWC Twitter account in case you are still waiting for an issue to be resolved. Thanks for your continued patience.

(The comments on this post are closed because this is not the right platform for support requests. Please use any of the appropriate platforms mentioned in this post.)

We have just tagged the final WooCommerce 2.1 release on GitHub, made it available on WordPress.org and announced it on our woothemes.com blog. WooCommerce 2.1 is live!

I’d like to thank all our contributors, translators and bug reporters. We really appreciate all your help and couldn’t have done these awesome releases without you guys.

This release ends the 2.1 development cycle and we’re in the grace period before WooCommerce 2.2 development officially starts. We did setup the maintenance branch for 2.1.x fix releases already and also made the master branch the development branch for 2.2. We’ll be closely monitoring any possible issues and fix them on the maintenance branch as soon as possible.

WooCommerce 2.2 development officially starts in March, so we’ll be focussing on fixes only for a couple weeks. There are a lot of issues already assigned to the 2.2 milestone, so there is plenty to work on should you want to contribute to this new release. 🙂

We have just tagged the second release candidate of WooCommerce 2.1. This marks the final stage of the new version and we’re certain it’s as stable as it gets. Just to make sure we haven’t missed anything, we’re going to leave it for everybody to test during the weekend and release the final right after.

Yes, you read that right! The final release of WooCommerce 2.1 is going to be available within 72 hours from now. If we don’t find any show stopping bugs in the next few days, the final will be tagged and made available on WordPress.org around noon UTC on Monday.

If you want to help testing in these final hours, pick up a copy of the code and open an issue if you find anything out of the ordinary. Please always be as detailed as possible about version numbers, steps to reproduce and other information that helps in getting an issue solved as quick as possible. You can also still contribute translations, through our Transifex project, to be included in the final release.

Note for developers: I hope this applies to nobody, but if your plugin or theme relying on WooCommerce is still not made compatible with WooCommerce 2.1, this is the last weekend you can do something about it. Read our beta 1 announcement for all the details that you probably want to check.

Have a great weekend, prepare for an exciting Monday! 🙂

We’re approaching the final release of WooCommerce 2.1. Today we have tagged the first release candidate, which is available for testing now. If you haven’t tested your extension or theme relying on internal WooCommerce code with this new version, this is your last chance.

Release candidates are the final stages of a new version. We think this new version is done, we’ve done a lot of testing and have fixed all the bugs that were reported in the beta phases. Now we need you to make sure we didn’t miss anything and that we can release WooCommerce 2.1 with as little bugs as possible.

If you need a recap of what has been changed, go read our beta 1 announcement. That post includes all changes you’ll want to check to make sure your plugin or theme is compatible with this new release.

In case you find a bug, please report it as an issue on GitHub and give us all the required information to be able to reproduce this issue. Things like version numbers and plugins and theme active at the time are essential to a good bug report.

We want to release the final version next week, a little over our planned deadline but still very close to ‘late January’. We’d like to thank everybody for testing, contributing fixes and all other ways you’ve helped out in making this new release happen.