WC 2.3 Release Candidate 1


WC 2.3 (Handsome Hippo) Release Candidate 1 has today been tagged. If all goes well, the final release will be tuesday. You can compare the changes since beta 3 here.

If you have not tested your theme or plugin yet you have a week to do so if you want to beat the release of the new version.

You can download the release candidate here: https://github.com/woothemes/woocommerce/archive/2.3.0-RC1.zip

If you are testing plugins and they are not showing up, ensure you name the plugin folder ‘woocommerce’ (removing the -2.3.0-RC1) when moving it into your plugins directory.

Thanks to everyone who has contributed to this release so far!

8 responses to “WC 2.3 Release Candidate 1”

  1. Hi, Mike Jolley.

    Looks WC 2.3 assets/css source used .scss not .less method?

    Did you will includes .less source as before WC 2.2 used method? Because of we already used less for theme as before you used. Please tell us about it so that we can test the 2.3 version. I think more user all have the same question as .scss replace .less.


    1. If your CSS is separate it shouldn’t affect you at all – WP only looks at the CSS files, not the less, scss source files.

      1. Because of we use less.php to use your .less css automatic generation new css when user change setting through WP admin options.

        We used your .less control like button default color etc variables … If have no .less file just css file will very difficult global change wc style variables.

        Thank u understand me and add .less for user global change variables.

  2. Glenn Martin Avatar
    Glenn Martin

    Do the commits after RC-1 become a part of the official 2.3 release? (i.e. Feb 4-9 commits)

  3. Please bring back the option to disable enhanced select boxes. This is breaking my theme and causing no end of headaches. Why on earth would you remove this option?

    Woocommerce is a great plugin, but it seems every new version breaks something for no good reason.

    1. Themes can disable the selects with a filter. End-users should not need to.

    2. can’t say this is the proper way to do this…but it worked for me. wish that option was still there in the admin though. silly to remove in my opinion.

      function my_dequeue_script() {

      add_action( ‘wp_print_scripts’, ‘my_dequeue_script’, 100 );

Leave a Reply

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