Changelog

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


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


  • This week we’re happy to announce WC 2.3 “Handsome Hippo” beta 1 is available for testing.

              ╭────────────╮
      ^oo^    ┃  Woo! 2.3  ┃
      (..)    ╰─y──────────╯
     ()  ()
     ()__()
    

    Since 2.2 we’ve had a humongous 1389 commits. You can view the changelog here and see what we’ve been busy working on: https://github.com/woothemes/woocommerce/blob/2.3.0-beta-1/readme.txt#L133

    Before going into the features, developers should be aware of the following changes which we’ve been covering in other posts:

    1. Changes to the coupon systemhttp://develop.woothemes.com/woocommerce/2014/12/upcoming-coupon-changes-in-woocommerce-2-3/
    2. Changes that affect theme authorshttp://develop.woothemes.com/woocommerce/2014/11/attention-theme-authors-frontend-changes-ahead-in-woocommerce-2-3/
    3. Changes in Email templateshttp://develop.woothemes.com/woocommerce/2014/10/2-3-emails/
    4. Chosen has been replaced with Select2 – Chosen is still registered in WooCommerce for now, but plugins should migrate to Select2 as soon as possible (select2 has a larger community behind it).

    Aside from the countless fixes and tweaks, here are a few of the key features in 2.3.

    An Overhauled UI

    James Koster has been busy closing UI related issues in 2.3, and UI was the main focus of the release. We’ve updated the user interface on both the front and backend of WooCommerce.

    On the backend, settings have been re-organised and perform better on hand-held devices for an all round improved user experience.

    On the frontend there are several UX enhancements such as the undo-remove-from cart link and responsive table design as well as a fresh, modern look which meshes more fluidly with the current design trends of default WordPress themes.

    Changes to the UI have been covered in more detail in this post.

    A UI for Webhooks

    Webhooks were introduced in our API in version 2.2 but where hidden from view (and only added via the API). Claudio Sanches has been busy fleshing out a UI for the Webhook system in 2.3 which will allow adding, removing, editing and viewing logs for webhooks.

    Webhooks make it easier for 3rd party apps to integrate with WooCommerce so the way should be paved for some interesting new services in the future.

    Geo-Location Features

    Whilst implementing solutions for the infamous EU VAT Changes, it became apparent that some users require that prices be shown to users with their local taxes reflected in the store. Therefore I began work on a geo-location solution for core.

    In 2.3 we’ve introduced a geolocation class which optionally allows you to set the default customer location to their actual location which will affect both:

    • Taxes shown to the user
    • The default state of the country selection box during checkout

    The class uses MaxMind’s geolite database, has fallbacks for several API based geo-location services, and works locally by using some IP lookup services when required.

    Unit Tests

    Although early days, some of our contributors, including new boy Barry Kooij, have been working on adding Unit Tests to WooCommerce. The code coverage should increase over time, but this is a big step forward in 2.3.

    Downloading the Beta

    Download 2.3 Beta 1

    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.

    Also when reporting anything to us:

    1. Describe the issue in detail, with a system status report
    2. Don’t report issues with extensions, only core
    3. Don’t report issues with themes
    4. Report bugs, not feature requests

    Thanks!


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

    This release fixes the ‘stock status issue on quick and bluk edit’ bug and the ‘incorrect clearing of error messages on checkout’ bug both introduced in version 2.2.9. You can view the full changelog here. A total of 8 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.)


  • The WooCommerce 2.2.9 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 several fixes in this release, including sanitizing data correctly during registration and minor tweaks related to taxes. Read more about the fixes in the changelog. A total of 66 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.)


  • For 2.3, aside from UI, we’ve been looking at some long standing issues. One of these issues related to the display of coupons when prices include tax (#4848). Although complex, this issue has been resolved in 2.3 without too much change, however, this also got us looking at this point raised by Samuel Aguilera:

    Apply discounts after taxes is not legal. Discounts must be always applied before taxes, is the law, not user preference.

    If you’re not aware, up to now the coupon system has always had an option at coupon level called “apply before tax” which, as stated, makes sure a coupon is calculated before tax at line-item level. Leaving the box unchecked would take the discount off after all taxes – so in reality we had 2 different types of coupons (before tax – cart, after tax – order) each with their own methods and display related functions.

    In 2.3 we’ve decided to simplify this down, have 1 set of coupons, and always apply them before-tax. See #6830.

    So What Has This Been Changed?

    • Apply Before Tax option removed from coupons
    • WC_Cart::get_coupons() which used to allow you to pass either ‘cart’ or ‘order’ has deprecated the type arg. If you pass in ‘order’ an empty array is returned.
    • WC_Cart::remove_coupons() same as above.
    • Deprecated some coupon methods in the cart and orders class:
      • WC_Cart::get_order_discount_total()
      • WC_Cart::apply_cart_discounts_after_tax()
      • WC_Cart::apply_product_discounts_after_tax()
      • WC_Cart::get_discounts_before_tax()
      • WC_Cart::get_discounts_after_tax()
      • WC_Abstract_Order::get_cart_discount()
      • WC_Abstract_Order::get_order_discount()
      • WC_Abstract_Order::get_cart_discount_to_display()
      • WC_Abstract_Order::get_order_discount_to_display()
    • $discount_total variable in cart class is deprecated (was after tax discount total) and will always be 0.
    • templates/cart/cart-totals.php has been edited to remove the after-tax discounts
    • templates/checkout/review-order.php has been edited to remove the after-tax discounts
    • Removed the edit ‘discount’ row from the edit orders panel in the backend – discounts are applied per line item (before tax!)

    WC_Cart::get_total_discount() should be used if you need to get the discount amount, instead of the deprecated methods. This method exists in 2.2.

    WC_Cart::get_discount_to_display() should be used to display the discount amount. This is a new method in 2.3

    What Theme Developers Need to Update

    Themes will need to update their template files, namely:

    1. templates/cart/cart-totals.php
    2. templates/checkout/review-order.php

    They will need to remove the second coupon/discounts loops (order level coupons). Failure to update won’t break anything however, it will just show a deprecated notice.

    What Plugin Developers Need to Update

    Remove the use of dedicated methods, and avoid accessing properties directly where possible. This update has deprecated methods and thus shouldn’t ‘break’ plugins, but it will render some functionality useless, such as code which checks for after-tax discounts.

    If you do notice something not backwards compatible (in that it causes error) will let us know asap.

     


  • The WooCommerce 2.2.8 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 several fixes in this release, including a minor security fix for nonce check in form handler. Read more about the fixes in the changelog. A total of 25 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.)


  • The WooCommerce 2.2.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.

    There were several fixes in this release, including a minor security fix for an XSS issue when using product notes. Read more about the fixes in the changelog. A total of 58 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.)


  • The WooCommerce 2.2.6 release is now available via WordPress.org or automatic update in your administration panel. This fixes a few small notices and a bug around editing order addresses in the backend.

    You can read more about the changes in the changelog. A total of 10 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.)


  • The WooCommerce 2.2.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.

    There were several minor fixes in this release which you can read about inside the changelog. A total of 130 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.)