Last call for testing, WooCommerce 2.0 coming March 4th

Written by Coen on February 22, 2013 Product News.

If you haven’t tested WooCommerce 2.0 yet, or haven’t prepared your website yet, now it really is the time to start doing that. Today we have tagged the second Release Candidate in our version control (you can now download it from GitHub) and this marks the last week of testing. If is it as good as we think it is (and no critical bugs are found), the final version of WooCommerce 2.0 will be released on March 4th.

This second Release Candidate also marks the moment where our support ninjas will start helping you resolving issues with WooCommerce 2.0 on your test installs. As with the previous beta and RC releases, we still do not recommend you run this version of WooCommerce 2.0 on a live website though, so please only use it for testing purposes.

Please test our extensions and themes

The second Release Candidate of WooCommerce 2.0 is also the first version where all extensions and themes are fully compatible with. So if you are using some payment gateways, or your website is powered by one of our premium themes, please check everything still works after updating to WooCommerce 2.0.

Although we think WooCommerce 2.0 is ready now, we still do not recommend you using this version on a live website. Please use a test environment for all your testing and wait updating the live website until we release the final version. Bugs with the main WooCommerce plugin can be reported via our GitHub repository. If you find a bug in one of our extensions or themes, please report them via our support portal.

Known issues with WooCommerce 2.0

Before you report any issues, please check the list of issues on GitHub to see if it hasn’t been reported yet. Also, there are a couple smaller issues with our themes that we are aware of and are currently fixing. These issues are:

  • Pagination will lack styling when themes are used with WooCommerce 2.0
  • Some themes don’t have add_theme_support( 'woocommerce' ) yet so there might be an incompatibility notice
  • Canvas is not compatible with WooCommerce 2.0 yet

Please do not report these issues. We are aware of them and they will be fixed before we release the final version of WooCommerce 2.0.

See you March 4th!

Mark it in your calendars, March 4th is going to be an important day for WordPress and eCommerce, of course especially for everything WooCommerce. The Daring Dassie (our code name for WooCommerce 2.0) is almost ready to go and it is eager to help you make your online stores even more awesome!


48 Responses

  1. thenbrent
    February 22, 2013 at 4:27 pm #

    Exciting times ahead!

  2. raison
    February 22, 2013 at 4:55 pm #

    Canvas not compatible with 2.0 yet. Blimey!

    • Ryan Ray
      February 22, 2013 at 6:47 pm #

      It will be updated very soon. 🙂

      • znagle
        February 25, 2013 at 5:42 pm #

        Any ETA on the Canvas update?

  3. samuelmaes
    February 22, 2013 at 4:56 pm #

    ‘The second Release Candidate of WooCommerce 2.0 is also the first version where all extensions and themes are fully compatible with’

    @coen, dynamic pricing isnt fully compat with WC 2.0 =(

    • Coen Jacobs
      February 22, 2013 at 5:02 pm #

      Please report all issues you know of through the channels listed above. I’m sure there will be some bugs in extensions, so please let us know. If there are already posts on those channels, we will get to them as soon as possible.

  4. Phil Johnston
    February 22, 2013 at 6:18 pm #

    Hey guys,

    If you have changed CSS classes it would be best – and IMO necessary – to provide a list of each class name that has changed. That way I can go through my themes and update each class name.

    The same goes for migration in general. Is there a migration instruction manual?

    • James Koster
      February 22, 2013 at 7:07 pm #

      Here you go, Phil.

      • Phil Johnston
        February 22, 2013 at 10:04 pm #

        Beautiful – thanks!

      • Phil Johnston
        February 22, 2013 at 10:05 pm #

        P.S. I think there some spelling mistakes in the classes there. They are written as “woocomemerce-“

        • James Koster
          February 22, 2013 at 10:48 pm #

          Phew, thought you meant in WooCommerce itself for a sec. Will fix that :p

  5. Justin
    February 22, 2013 at 6:42 pm #

    Can’t wait! Keep up the good work!

  6. krbvroc1
    February 22, 2013 at 8:09 pm #

    Good job, certainly a major milestone!

  7. markluchauer
    February 22, 2013 at 8:27 pm #

    Can’t Wait!!! The biggest thing I am looking forward to is the ability to create a new Customer and give them Downloadable Product Permissions for Variations of downloadable products on their account. I will test that function next week and let you know if there are any bugs.

  8. KC
    February 22, 2013 at 11:44 pm #

    Do I still have to be 1.6.6 as active plugin? RC1 & RC2 got installed as separate plugin. When I deactivated 1.6.6, whole formatting was messed up. Right now I have both 1.6.6 and RC2 as active and things seem to working fine.

    • James Koster
      February 23, 2013 at 3:01 am #

      You should only have one version active.

      There shouldn’t be anything catastrophic on the front-end, but it’s worth have a read of this (assuming you’re not using a WooTheme).

      • KC
        February 23, 2013 at 4:51 pm #

        I am using 2.0 compliant version of Maya theme. Everything looks good with 1.6.6 and RC 1 or 2 being activate. As soon as I deactivate 1.6.6, the content between header and footer gets messed up. Sidebar goes under shop content instead of being on the side. Pretty weird.

        • Coen Jacobs
          February 23, 2013 at 8:04 pm #

          Please contact support for this issue, post comments are not suitable for support requests like this. You should only run the latest version of the WooCommerce plugin and it should be in the ‘woocommerce’ folder. All other should be deleted.

          • KC
            February 24, 2013 at 5:16 am #

            Found the root cause.

            >>it should be in the ‘woocommerce’ folder

            RC1 or 2 got installed in a separate directory which caused this weird problem.

  9. Mehmet Balsever
    February 23, 2013 at 12:12 am #

    Getting closer and closer !

    • Ryan Ray
      February 23, 2013 at 1:51 am #

      Mark your calendar!

  10. Robert
    February 23, 2013 at 3:27 am #

    Only two more months to go. So excited that I can’t even sleep at night (just kidding). But I believe that WooCommerce 2.0 is a worth waiting product.

    • cubewebsolutions
      February 23, 2013 at 5:25 am #

      Pretty sure you meant 2 weeks 😉

    February 24, 2013 at 12:17 am #

    Is there a reason that the Status under the Order dashboard was changed to a simple minus/checked icon rather than keeping the status text? I have added in custom color coded status es and find the minor change very confusing to keep track of just the icons/colors. I also find that it doesn’t streamline the process for me as I have to always hover over the icon to remember what Status it is. Just looking for an explanation, but besides that kudos to 2.0!

    • James Koster
      February 24, 2013 at 1:11 pm #

      It’s cleaner, saves a bunch of space and should be just as easy to scan. Take a look at the orders screen on a smaller browser window to see why that’s so important 😉

      Hopefully the icons / colors are self explanatory… you may have to hover a couple of times to make sure, but seeing as you’ll be spending a lot of time on this screen I’d expect you’d pick them up very quickly.

  12. ckubs
    February 24, 2013 at 10:29 pm #

    It’s not really woocomerce related but I have something to ask. Do you have something personal with bloggers?
    I want to try one of the newest free themes or maybe buy one but, all your newest themes are woocomerce dependent and since I don’t have an online store or online-blogging store I’m pretty confused.

    • Michael Krapf
      February 24, 2013 at 10:39 pm #

      Sorry for any confusion. Our themes are WooCommerce compatible not WooCommerce dependent. WooCommerce is a separate plugin and isn’t a requirement of the themes.

      • ckubs
        February 25, 2013 at 5:23 pm #

        Since I didn’t know that to buy one of the premium themes I tested Mystile a while back and I couldn’t do a single thing with it because I was getting a warning to install WooCommerce.
        I’ll look again before making up my mind and thanks a lot! You should state somewhere in a little note that themes could work both with or without WooCommerce 🙂

        • James Koster
          February 26, 2013 at 7:16 pm #

          Sounds like an old version. The latest version should work just fine without WooCommerce activated 🙂

  13. Daniel
    February 25, 2013 at 11:17 am #

    Is there a mail editor coming with woocommerce 2.0?

    I have to change the mail texts and layouts in the backend, cause in the themefiles it is very complicatetd.


    • James Koster
      February 26, 2013 at 7:17 pm #

      Not from the backend, but there’s an easy way to automatically move email template files directly to your theme. So you no longer need to worry about getting the files into the correct directory etc.

  14. Trey
    February 27, 2013 at 5:56 am #

    Will the new version work in responsive websites?
    What is the planned launch date?

    • Alexbangkok83
      February 27, 2013 at 10:18 am #

      Of what i have read, the 4th of March, only 5 days to go!

      I am so looking forward to this update, and I will probably need to talk with my client about delaying the project and wait for the 2.0 version to be released before starting with his new shop.. 🙂

  15. R.Bhavesh
    February 27, 2013 at 12:18 pm #

    “Canvas is not compatible with WooCommerce 2.0 yet”

    Does this mean woocommerce supported themes needs to be upgraded/changed as well? If yes, is there a guide on this that we can refer to?

  16. Elijah Jock
    February 28, 2013 at 6:45 pm #

    Great blog! Good consumer content. Its great to see informative blogs! Keep up the good work.

  17. AnyDog
    February 28, 2013 at 7:42 pm #

    I’m almost finsihed test WC 2.0 and congrats for making great plugin even greater ! 🙂
    I have on issue, though – I’m trying to dequeue prettyPhoto scripts and styles (because my theme has a lot other dependencies on Fancybox ), but haven’t been able to dequeue them.

    Here’s the code I used, in theme’s functions.php:

    function prettyPhoto_dequeue () {
    if ( version_compare( WOOCOMMERCE_VERSION, ‘2.0’, ‘>=’ ) ) {


    Any ideas ?
    Thanks … 🙂

    • AnyDog
      March 2, 2013 at 2:57 pm #

      Found it:
      to make dequeue script instead of ‘wp_enqueue_scripts’ action that executes later should be used, like – ‘wp_print_scripts’.
      So instead of:
      I hope this will help someone … Cheers

  18. CBBMaster
    February 28, 2013 at 11:30 pm #

    I’m pretty much disappointed with all things Woo at the moment. The new website is a mess, a lot of the documentation lands on a 404, I get 502 gateway issues, and in general, Woo Commerce is a hassle.

    First, there is no easy way to adjust the way the cart displays, I can’t use subscriptions with the AIM plugin that I have installed, and this whole thing is pretty darn brittle and funky when using and Chase Paymentech.

    Used to love Woo, but the waste of time these days trying to find info on the site and the snarky responses to support requests suck.


  19. David
    March 1, 2013 at 4:27 am #

    has anyone tested this with gravity forms addon?

    • oslpag
      March 1, 2013 at 1:50 pm #

      Yep, I have tested it with gravity forms and product add-on. It semi works, biggest problem is that any orders made using the product add-on for options the options do not come through on the order so it is impossible to see what options have been selected.

  20. Christopher Anderton
    March 4, 2013 at 2:16 pm #

    Waiting eagerly.

    • Alexbangkok83
      March 4, 2013 at 2:59 pm #

      So am I!

  21. bjornsennbrink
    March 4, 2013 at 2:24 pm #

    When is it due?

  22. Bryant Willis
    March 4, 2013 at 6:16 pm #

    FYI: WooTheme Definition is giving me the incompatibility notice.

  23. Tondo Susanto
    March 5, 2013 at 11:25 am #

    I used woocommerce 2.0 on my other site and use Artificer theme, I have the problem with pagination, even I disabled the pagination from theme option it shows on front page vertically and not horizontally.. need help

    • zao3d
      March 9, 2013 at 7:27 pm #

      I have the same problem with the pagination. It shows vertically. Anyone know how to fix that problem?

  24. prodigy27
    March 9, 2013 at 7:53 pm #

    same issue, not sure where in the theme i can fix this. been searching blogs for hours…nothing works.