WooCommerce 3.0.0 RC2

WooCommerce 3.0.0 RC2 is available for testing. This fixes a bunch of issues from 3.0.0 RC1 which we’ve spent the last 2 weeks working on. Notable fixes include:

  • Fixed some edge case gallery issues such as galleries with no images, and zoom image sizes when flexslider is not used.
  • Fixed the 3.0 db updater to correctly set the outofstock term.
  • Fixed double add to cart issue on cart page when querystring contains add-to-cart.
  • Fix coupon removal in cart.
  • Added __sleep and __wakeup methods to data stores and data objects to avoid full object serialisation. Because of this, we were able to remove the special handling in email cron (since this is better), and remove the now defunct object caching in the data stores.
  • Prevent max on qty selectors being set to -1.
  • Improved default column definition in admin screens.
  • Fix to allow custom order item types from 2.6.
  • Fixed some bugs in the legacy API (using incorrect getters).
  • Various docblock/deprecation notice corrections.
  • Various RTL fixes.
  • Various fixes to prevent notices e.g. by casting floats when doing arithmetic.
  • Fixed API to return names instead of slugs in variation API.
  • Various REST API v2 schema and return type corrections (to match docs).
  • Removed timezone guesswork from set_date_prop method so offsets are correctly handled when the WP timezone setting is set to a UTC offset.

The REST API v2 docs are also now live so be sure to check out what is now possible with 3.0.0 and the v2 API if you’re using it.

To test WooCommerce 3.0.0 RC2, you can use our WooCommerce Beta Tester plugin or you can download the release candidate here (zip).

Think you’ve found a bug? Please post in detail to Github.

The final version of 3.0.0 is still due for April 4th 2017. Huge props to everyone who has sent feedback about this release so far or found bugs.

24 responses to “WooCommerce 3.0.0 RC2”

  1. […] WooCommerce team just released the WooCommerce 3.0 Release Candidate 2. This means that we are very close to the final release of this new version of WooCommerce. The […]

  2. […] as you have to know a bit about how coupons are stored (though this is a lot simpler with WooCommerce 3.0+, which is coming […]

  3. […] or Updated Plugins & Themes A second release candidate was announced for WooCommerce 3.0, with the full release on Tuesday. Be sure to […]

  4. bildmanufakturwackernah Avatar

    Hey Mike, how about compatibility of woo extensions for woocommerce with release 3? Is there anywere a listing or do we have to read each changelog?

    1. Changelogs; all should be ready in advance.

  5. Egbert Avatar

    I just noticed that the pagination in 3.0.0.RC2 doesn’t show 1-15, 16-31 etc. but just 1, 16 etc. Did I forget a setting? I show 15 products per page,
    Also: I’ve never been able to change the number of columns to something else than 3. When I set to 5, I get weird display 5 divided over 2 lines.
    Best regards, Egbert Jan, NL

    1. Nothing changed with paging.

  6. Mike, we upgraded from 2.6.14 to 3.0 today. This suddenly threw our order numbers out of sequence, causing large gaps between new order numbers. And when we search for one of those new orders by number on the back-end, it’s pulling up the same order under a different number. Are these known bugs from one of the version updates? Prior to that, everything was butter. We unfortunately had to revert back to 2.6.14 🙁

    1. Order numbers in WooCommerce are not sequencial and never have been, unless you have an extension to handle that.

  7. I installed today the new version of WordPress 3.0.0 and messed up my whole website.
    I had to check all the plugins and found that it caused the problem.
    Product Titles, Sale Prices, Stock Status, EU VAT Assistant (does not work at all), Shipping Rules and I don’t know what else! I had to restore the website through a backup file and I am trying for hours to recover it. Very dissapointed.

    1. This is why we clearly state this is a major update which requires testing in advance. You need to get updated extensions from the developers before updating.

      1. All the other plugin were updated if you mean that. That version was not tested for such many problems? It is first time happening.

        1. Were they updated for 3.0 though? They are third party so it’s down to the author to test once we release beta etc.

  8. sumbalancenemiljones Avatar

    Major issue regarding product gallery images. The Woocommerce prettyPhoto js library isn’t used anymore and even the backend settings were gone for lightbox gallery. I hope it will be fixed in the upcoming updates. Thanks!

      1. hey @mike – For clarity – does that mean that there is no backwards compatibility with the old prettyPhoto lightbox if someone updates to 3.0 and their theme hasn’t yet been updated to support one of the new gallery features? I’m seeing one or two posts on the Advanced WC facebook group from users who are reporting their lightboxes are disappearing. I’m guessing this is because they’ve updated to WC3.0 and their themes don’t yet provide support for the 3.0 gallery features.

        1. PrettyPhoto is no longer included, so unless you have a custom gallery, it will no longer work because the script is not present. Impossible to detect if the old gallery is needed or not.

          1. thanks for the clarity Mike – I can see a few non-technical people getting confused on fb because they don’t understand they have to wait for theme authors to update their themes. I’ll do my best to help point them in the right direction 🙂

  9. I installed today 3.0.0 and now is my page automatic constantly changing…..Do you now this problem? My site is http://www.zoemzz.nl

  10. Are all gallery issues fixed? I have still problems with the product images after the update do version 3.00

  11. Rnz Dev Avatar

    Hi. I want to know how to update JSON-LD. The current updates removed my inline Microdata.

    -Improved structured product data by using JSON-LD instead of inline Microdata.


    1. The JSON LD is filterable. We don’t have docs up for it, but there is a class in the includes folder which handles all of the structured data.

Leave a Reply

Your email address will not be published. Required fields are marked *