Recent Updates Toggle Comment Threads | Keyboard Shortcuts

  • Mike Jolley 12:53 pm on March 18, 2015 Permalink
    Tags:   

    WooCommerce 2.3.7 Fix Release Available 

    The WooCommerce 2.3.7 release is now available via WordPress.org or automatic update in your administration panel. Thanks to all of our contributors who’ve been helping out.

    This release just fixes some minor issues. Read more about the fixes in the changelog. A total of 16 commits made it into this release.

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

     
  • Mike Jolley 1:53 pm on March 13, 2015 Permalink
    Tags:   

    WooCommerce 2.3.6 Fix/Security Release Available 

    The WooCommerce 2.3.6 release is now available via WordPress.org or automatic update in your administration panel.

    This release includes fixes for several minor issues, including some edge case issues such as redirect loops when using memcache, and 2 potential security issues within admin. Read more about the fixes in the changelog.

    A total of 215 commits made it into this release.

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

     
  • patrick 6:43 pm on March 5, 2015 Permalink | Reply  

    How to Test Your Extensions the WooThemes Way 

    There seems to be a bit of confusion in our community about how and when you should test your extensions against a new version of WooCommerce. There is no right or wrong way to test extensions so I’ll tell you what we do here at WooThemes.

    1. Subscribe to this blog and pay attention to the big changes as they come out. Ex. in 2.3 the coupon system was refactored. If you have an extension that deals with coupons then it’s advisable to test right then and make any updates you have to make.
    2. When the first beta is announced on the develop blog it’s time to test your extension. Betas are usually very similar to the final release. In rare exceptions features are added or deleted here but usually after the first beta there are only bug fixes.
    3. When the first release candidate is announced do another quick test to make sure your extension works. If something did make it into the beta to affect your plugin this is where you catch it. The release candidate is strictly bug fixes. If it works during the release candidate phase it should work when the new version of WooCommerce is released.

    We do all of our development on the master branch so whenever you want to test WooCommerce it’s best to use the master branch.

    There are a couple of our extensions that are quite large and extra testing goes into these plugins. Plugins like Subscriptions for example usually has several weeks or months of testing to make sure that everything will work against the newest version of WooCommerce. If you have a very large or complex extension then it’s worth testing as we add features into WooCommerce before we release the first beta.

    I hope this clears up how we do our own testing and hopefully it should help you do yours. :)

     
    • Caspar Hübinger 12:34 pm on March 6, 2015 Permalink | Reply

      We do all of our development on the master branch so whenever you want to test WooCommerce it’s best to use the master branch.

      Awesome! I had been told the direct opposite during development of 2.3. Good to know which branch to pull for early testing now. ;)

      • claudiosmweb 2:32 pm on March 6, 2015 Permalink | Reply

        Use the master branch just for now. Soon the master will be for 2.4 and will have a lot of issues. But will have the 2.3 branch, where you can test the current support and master will be stable just close to a beta version as I said before.

  • claudiosmweb 4:44 pm on February 20, 2015 Permalink  

    WooCommerce 2.3.5 Fix Release Available 

    The WooCommerce 2.3.5 release is now available via WordPress.org or automatic update in your administration panel. Thanks to all of our contributors who’ve been helping out.

    This release just fixes some minor issues. Read more about the fixes in the changelog. A total of 45 commits made it into this release.

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

     
  • Mike Jolley 4:54 pm on February 17, 2015 Permalink
    Tags:   

    WooCommerce 2.3.4 Fix Release Available 

    The WooCommerce 2.3.4 release is now available via WordPress.org or automatic update in your administration panel. Thanks to all of our contributors who’ve been helping out.

    This release fixes some errors on certain server setups, and other minor issues. Read more about the fixes in the changelog. A total of 82 commits made it into this release.

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

     
  • Mike Jolley 3:29 pm on February 11, 2015 Permalink | Reply
    Tags:   

    Hey, Thats a Handsome Hippo 

    slack-imgs.com

    Today we’re proud to announce that the latest and greatest version of WooCommerce has been released; v2.3, codename Handsome Hippo.

    2.3 has been in active development for around 5 months and has seen around 1800 commits from 22 contributors.

    Top Contributors

    Top Contributors

    What’s New?

    As the codename Handsome Hippo (hopefully) suggests, a lot of attention in this release has been paid to WooCommerce’ appearance / UI, on both the front and back end.

    • On the frontend we’ve added several little usability enhancements such as:
    • A more simplistic ‘flat’ design (for themes without a specific WooCommerce integration) and updated email design
    • The ability to remove products from the cart via the cart widget
    • Classes / markup for responsive tables (see the orders table on ‘my account’)
    • Moved the ‘Proceed to checkout’ button to a more appropriate location
    • An ‘undo’ option when removing products from the cart

    We’ve also removed a couple of features:

    • The +/- quantity increment buttons – `input type=”number”` is well supported making this feature redundant.
    • The style settings (button colors etc).
    • The ability to create non pre-tax coupons, read full post here

    Both of these features can be replaced using their plugin counterparts:

    The WooCommerce colors plugin will automatically detect any previous settings when you activate it so the transition will be smooth should you still need that functionality.

    It’s inevitable that some sites/themes will be affected by these changes. If you build WooCommerce themes you are hopefully already up to date with these developments. If you’re a store owner running a third party theme, be sure to read the section on how to upgrade WooCommerce further in this post to make sure you’re prepared. You may even consider reaching out to your theme author directly.

    If you’re a developer working with WooCommerce, here are a few other key changes in 2.3:

    1. Template debug mode will now remove all template overrides for template loading functions. This is handy if you’re building (or using) a theme which overrides core templates and run into issues. There’s now an easy way to simply turn those templates off to help locate the source of a problem.
    2. We’ve switched from LESS to Sass as a CSS pre-processor of choice, and included bourbon giving us access to a whole load more useful mixins. If your theme or extension imports any of our .less files, now would be a good time to make the switch to sass.
    3. The order summary and payment section of the checkout have been decoupled making it possible for you to move each component independently via theme/plugin modification. Please note that if your theme currently overrides any of these templates, you will need to update them. See https://github.com/woothemes/woocommerce/tree/master/templates/checkout for the latest.
    4. We’ve migrated away from chosen in favour of Select2 for our form enhancement needs. Select2 is the more actively developed script and has been adopted by WordPress core which helps make WooCommerce that little bit more efficient. Chosen is still registered as a script within WooCommerce but if you use that functionality we recommend adopting Select2 asap as chosen will be removed altogether in a future release.
    5. We’ve included a new Geolocation class and changed the way taxes are displayed to customers on the frontend. Customers will now see taxes based on their address, and you have the option to enable their location to be geolocated when they visit your store.
    6. If you’ve played with the Webhooks API in 2.2 you’ll know that previously they could only be created via API calls. 2.3 includes a Webhooks UI which will allow users to create them via the settings page. For instructions on using Webhooks see: http://docs.woothemes.com/document/webhooks/

    How to Upgrade

    As always, we recommend making backups, and using a staging environment to test major updates with your themes and plugins prior to pulling the trigger. See our post here for best practices:

    http://docs.woothemes.com/document/testing-updates-using-a-staging-environment/

    We don’t anticipate major issues with extensions, but themes that override template files (such as those on the cart and checkout pages) should be checked or updated to ensure they are not affected by the UI changes.

    How to Report Issues and Contribute to Future Updates

    Issues and contributions should be made via Github:

    https://github.com/woothemes/woocommerce/issues/new

    See our contribution guide here:

    https://github.com/woothemes/woocommerce/blob/master/CONTRIBUTING.md

    If you are reporting a 2.3 issue, please include steps to replicate the issue and mark your issue [2.3] so they stand out.

    How to Contribute the Localizations

    If you spot any missing translations, please join us on Transifex:

    https://www.transifex.com/projects/p/woocommerce/

    It’s free to join and easy to translate strings. Translation updates made through Transifex will be made to all other users

    Another huge thankyou to our translators!

    The Road to 2.4…

    We’re going to be discussing the roadmap for 2.4 in a few weeks, but rumour has it we’ll be looking at the onboarding process specifically to improve usability. Stay tuned!

    Edit: We’ve released 2.3.1 to fix some conflicts a few users were finding after using the geolocation features. This prevents some errors if the geolocation DB cannot be downloaded too.

     
    • Pieter 3:36 pm on February 11, 2015 Permalink | Reply

      Welcome handsome hippo! :)

    • Mud Life LED 6:56 pm on February 11, 2015 Permalink | Reply

      Hopping over to Happy Hippo now. Hope all goes without a Hitch.

    • Jens 9:58 am on February 12, 2015 Permalink | Reply

      Thanks for the great release!

      > “We’re going to be discussing the roadmap for 2.4 in a few weeks, but rumour has it we’ll be looking at the onboarding process specifically to improve usability. Stay tuned!”

      This is nice but I think you should really focus on better stabilty and long term support of releases.

      That is, a better test coverage and hence less regression bugs with each release. Even minor 2.1.x, 2.2.x, 2.3.x releases very often break things.

      That is, better support for security fixes for the last two recent mayor releases (currently 2.2 and 2.3). Professional shops do not want to deploy new releases every few months, having a release every year or two is enough for most. Especially since each (even minor) upgrade means, due to often regression bugs, a full test cycle if all the functionality and customization done to the shop are still working.

      • Mike Jolley 10:18 pm on February 12, 2015 Permalink | Reply

        We are adding unit tests gradually to improve regression testing. Keep an eye on github.

    • Becky 8:13 pm on February 12, 2015 Permalink | Reply

      I completely concur with Jens. This past year of changes has been pretty brutal on active stores. I have had to grit my teeth with each release and not only test on my end but hope my client doesn’t start screaming about missing shipping addresses in the notifications. It would be nice if you guys would focus on some long term stability and give developers and the clients who have to pay for all this deployment testing a break.

      • Mike Jolley 10:16 pm on February 12, 2015 Permalink | Reply

        This release has been pretty quiet in terms of issues in support – we do however see the usual 3rd party theme/plugin breakage, but this is largely due to lack of testing. This time round Patrick reached out to marketplaces (themeforest for instance did a post on it), and we’ve been actively blogging here to keep devs in the loop!

        The main issues I’ve been seeing breaking stores are old extensions using functions deprecated in 2.1 – devs have had 12 months to fix those issues.

        • Glenn Martin 8:21 pm on February 14, 2015 Permalink | Reply

          I like the aggressive Woo release cycles. I never had an upgrade problem, and just upgraded 3 sites to WC 2.3.3 without a hitch.

          For those concerned about the upgrades cycles, just follow 3 simple rules:
          (1) wait 2-3 days after big releases till you upgrade to allow for the bugs to get worked out (I went from 2.2.11 to 2.3.2; I skipped 2.3.0, 2.3.1).
          (2) use quality plugins.
          (3) use a staging site to test before deployment.

          Great job, WC team!

          • Jens 7:23 pm on February 17, 2015 Permalink | Reply

            I am not saying that I am against quick release cycles, by no way. I am saying that I do not like the idea of being forced to upgrade and test a shop every half a year, or whenever a security release is done (including all regression bugs).

            Same reason as for using Ubuntu LTS (long term support), there I only have the hassle of upgrading every few years. This applies for bigger shop websites that have release plans on their on, and usually there is no reason to uplift a running shop system except every 2 years. Whoever, want to upgrade (and test) with every minor and mayor release every few weeks can still do so – it is the point of being forced that makes it impractical.

            • Willem 7:12 pm on February 18, 2015 Permalink

              I have to agree here. Perhaps a LTS version of woocommerce every year (with security releases) would be ideal. I have a lot of customisations and upgrading Woocommerce every time because of security concerns also means a lot of unnecessary work on my end.

              I think I may have to skip this release entirely. Its completely breaking some of my front end stuff.

            • Stefano 9:15 pm on February 18, 2015 Permalink

              Agree at 100%

      • sarah 12:33 am on February 20, 2015 Permalink | Reply

        Please remember that we’re not all developers. I’m a small business owner and its all on me if it goes wrong. I don’t even have a test environment to try it out on first! One of the reasons i chose woocommerce was that it presented as great for small business but i too grit my teeth with every update.

    • Aurélien Debord 2:07 pm on February 13, 2015 Permalink | Reply

      Welcome Hippo. Nice work everyone :)

    • Kent Routen 12:38 am on February 21, 2015 Permalink | Reply

      Hi there, one of my client websites no longer displays the +/- quantity increment buttons when we use the latest version of chrome. http://www.nzbinding.com/

      The arrows do display for firefox. However we would like to have the exact styling which displayed in the previous woocommerce version or can you fix the bug so the arrows display for chrome.

      How do we fix this as my client is not happy at all? Kent.

    • Kent Routen 12:52 am on February 21, 2015 Permalink | Reply

    • Dan Goldstein 10:40 pm on February 24, 2015 Permalink | Reply

      Does putting quantity plus and minus into a separate plugin mean you’re not supporting Internet Explorer anymore? Those buttons aren’t in any version of IE, even 11.

      http://caniuse.com/#search=number

  • Mike Jolley 5:11 pm on February 3, 2015 Permalink | Reply
    Tags:   

    WC 2.3 Release Candidate 1 

    slack-imgs.com

    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!

     
    • aven 1:29 am on February 6, 2015 Permalink | Reply

      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.

      Thanks.

      • Mike Jolley 7:04 pm on February 7, 2015 Permalink | Reply

        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.

        • aven 1:13 am on February 8, 2015 Permalink | Reply

          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.

    • Glenn Martin 1:21 pm on February 9, 2015 Permalink | Reply

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

    • Jonathan 10:42 pm on February 10, 2015 Permalink | Reply

      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.

      • Mike Jolley 10:08 am on February 11, 2015 Permalink | Reply

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

  • Mike Jolley 4:09 pm on January 30, 2015 Permalink | Reply
    Tags:   

    2.3 Handsome Hippo Beta 3 

    Today we put out WC 2.3 Beta 3 which fixed several issues and oversights in beta 2. This should hopefully be the final beta before release.

    Changes Since Beta 2

    You can view a comparison between beta 2 and master here, but notable changes include:

    Help Translate 2.3

    The latest 2.3 POT files have been pushed to Transifex meaning you can get involved in the translations here: https://www.transifex.com/projects/p/woocommerce/

    Download the Latest Beta

    We’re happy to listen to your feedback regarding 2.3 and would appreciate any bug reports going directly to Github.

    Download 2.3 Beta 3

    If you find a bug with the beta, please ensure you prepend the ticket title with [2.3] when submitting the issue to GitHub, or at least mention what version you are using in the ticket description.

    Thanks again.

     
    • IshYoBoy 9:05 am on February 2, 2015 Permalink | Reply

      Dear WooCommerce Team,

      Will you post an official blog post with the final date when the 2.3 version will be live once you know it?
      Will you give authors a few days/week in advance to make final tests with the latest release candidate?

      Cheers

      • Mike Jolley 3:00 pm on February 2, 2015 Permalink | Reply

        These betas should serve as your warning. When the RC is out (this week) the final release will follow in a matter of days.

    • Jason Rhodes 5:09 pm on February 3, 2015 Permalink | Reply

      Looking forward to rolling out the final release of 2.3 to some new clients that are very excited by the new changes.

  • claudiosmweb 3:55 pm on January 29, 2015 Permalink  

    WooCommerce 2.2.11 Fix/Security Release Now Available 

    The WooCommerce 2.2.11 release is now available via WordPress.org or automatic update in your administration panel. Thanks to all of our contributors who’ve been helping out.

    There were some fixes in this release, including escaping urls before display in admin and frontend to avoid XSS and minor tweaks. Read more about the fixes in the changelog. A total of 6 commits made it into this release.

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

     
  • Mike Jolley 3:29 pm on January 26, 2015 Permalink | Reply
    Tags:   

    2.3 Handsome Hippo Beta 2 

    Work continues on 2.3 and we’re getting closer to the final release. We’re expecting to have a release candidate out within a week, so don’t forget to test your extensions and themes!

    Changes Since Beta 1

    You can view a comparison between beta 1 and master here, but notable changes include:

    • Added the WC Tracker (opt-in usage tracking)
    • Added additional filters/args to wc_price function and added functions to get things such as the decimal separator (wc_get_price_thousand_separator, wc_get_price_decimal_separator, wc_get_price_decimals)
    • Fixed issues showing variation prices when free
    • wc_format_content() function to work around some theme conflicts
    • PDT vs IPN option in PayPal standard

    We’ve also updated the API docs here: http://docs.woothemes.com/wc-apidocs/

    Help Document the REST API

    We now have a Github Repo for the REST API Docs where you are welcome to make contributions. We’re using Slate to generate the actual documentation from this repo.

    The generated REST API Docs can be found here: http://woothemes.github.io/woocommerce-rest-api-docs/

    Help Translate 2.3

    The latest 2.3 POT files have been pushed to Transifex meaning you can get involved in the translations here: https://www.transifex.com/projects/p/woocommerce/

    Download the Latest Beta

    We’re happy to listen to your feedback regarding 2.3 and would appreciate any bug reports going directly to Github.

    Download 2.3 Beta 2

    If you find a bug with the beta, please ensure you prepend the ticket title with [2.3] when submitting the issue to GitHub, or at least mention what version you are using in the ticket description.

    Thanks again.

     
    • Jami Gibbs 5:59 pm on January 26, 2015 Permalink | Reply

      Stoked! :)

      Just a head’s up that wooocommerce.php is still showing version as: 2.3-beta-1

    • Cyndi 4:14 pm on February 5, 2015 Permalink | Reply

      Can’t even freaking tell you how happy I am to find this. My perma-links were busted to hell. I had imported 350 products, trashed wordpress three times and got no help on my support ticket. Then I find the most obscure google search result that led me here………… SAVED MY SANITY. <3 xoxoxo

c
Compose new post
j
Next post/Next comment
k
Previous post/Previous comment
r
Reply
e
Edit
o
Show/Hide comments
t
Go to top
l
Go to login
h
Show/Hide help
shift + esc
Cancel