Changelog

Check out the latest releases from the WooCommerce project.
Subscribe to all release posts via our RSS feed.

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

  • Today we tagged WooCommerce 2.1 Beta 3 which has seen 174 commits from 29 contributors since the previous beta. Things are looking quite stable and no bug reports remain open, so if all goes to plan this will be the final beta before the release candidate later this month.

    Again, we encourage everyone (especially those with extensions and themes in the wild) to test, ensure their work is compatible, and report any core issues directly to us on Github.

    You can grab the latest tag release here. Thanks to everyone who’s been involved in the testing so far.

  • Two weeks after the first beta, I’ve tagged the second beta of WooCommerce 2.1 today. It’s been a pretty smooth ride so far, with very few critical bugs being reported. We did manage to get 123 commits in since the first beta, so no doubt there were some issues still present. 🙂

    If this continues to be such a smooth ride, we’re going to enjoy our holidays in the beta phase still and release the first Release Candidate in early January. We don’t want to do this before or during the holidays, since everybody is going to be spending time with family and friends.

    This is the moment to get active in testing. We’re pretty confident this second beta is stable enough, but it might contain a couple conflicts or hidden bugs that we haven’t discovered so far. We can’t fix bugs that we’re not aware of, so if you can squeeze in a couple minutes testing and report any issues you might find, that would be great. We really appreciate all the feedback we’ve got so far!

    All this also means that we’re on schedule for releasing the WooCommerce 2.1 final in January. 🙂

  • Without further ado, we’re please to announce “Peppy Penguin” Beta 1 is available for testing.

        ╭────────────╮
    ┃  Woo! 2.1  ┃
(o< ╰─y──────────╯
//
V_/_

    2.1 has pretty much been developed in parallel with our 2.0 fix releases for several months now, with major changes being added to 2.1 whilst fixes were rolled out in 2.0. Since 2.0 there have been over 1,318 commits which shows how busy we’ve been 🙂

    The plan is to allow the beta(s) to run through Christmas, with a release candidate early Jan quickly followed by a stable release. So 2.1 will be released in January, so long as WordPress 3.8 is out.

    That gives theme and plugin developers at least a month and a half for testing. You have been warned 🙂 (more…)

  • With only a couple open issues left in our GitHub repository, we’re closing in on the first beta release. It’s time to start reviewing the issues and have a closer look at what still needs to be done.

    Patches, feedback and testing is very welcome in all these issues. It will take a bit of a team effort to get everything done in time. We still have the end of this month as a target for the first beta of WooCommerce 2.1, so every bit of help is welcome these coming weeks. (more…)