Changelog

Check out the latest releases from the WooCommerce project.
Subscribe to all release posts via our RSS feed.

  • Payment Gateways in WC 2.2 can be improved with the introduction of two new features; being able to store a transaction ID in a standardised format, and being able to programatically handle refunds.

    Storing transaction IDs

    Storing transaction IDs is useful because these will appear in the order interface:

    2014-08-05 at 16.41

    If your gateway makes use of the $order->payment_complete() method, storing your transaction ID is a simple process. Simply pass the transaction ID to the method:

    $order->payment_complete( $transaction_id );

    WooCommerce will then store the ID as post meta.

    If you need to do this manually for any reason, you can set it directly using add_post_meta:

    add_post_meta( $order->id, '_transaction_id', $transaction_id, true );

    Turning the transaction ID into a link

    You’ll notice in the screenshot above, the transaction ID is a link – in this case linking the the transaction on the PayPal site. If you want to do this for your gateway, in your constructor set a “view_transaction_url” property, e.g:

    $this->view_transaction_url = 'https://www.paypal.com/cgi-bin/webscr?cmd=_view-a-trans&id=%s';

    WooCommerce will substitute the %s for the transaction ID during output.

    Supporting refunds

    To support refunds you need to create a process_refund() method in your gateway class. Without showing the refund code itself (which you’ll be writing) your method should look something like:

    public function process_refund( $order_id, $amount = null ) {
  // Do your refund here. Refund $amount for the order with ID $order_id
  return true;
}

    This method should return a bool (true or false, if the refund was successfull or unsuccessfull) or a WP_Error object if something went wrong.

    As well as created this method, you need to define support for refunds. To do this, set the “supports” property in your constructor, e.g.:

    $this->supports = array(
  'products',
  'refunds'
);

    This will let WooCommerce know that your gateway can handle refunds.

  • This week we’re happy to announce WC 2.2 “Prowling Pangolin” beta 1 is available for testing.

    
             ,___,           ╭────────────╮
      ╭╴╴╴╴/ ⏖ ⏖ ╴╴╴╮    ┃  Woo! 2.2  ┃
   ╭╯⏖ ⏖ ⏖ ⏖ ⏖ ⏖ ( ⦿    ╰─y──────────╯
 ↜╯╯    ‴▾▾LL▾▾▾▾▾LL   \   
                           *

    Since 2.1 we’ve had a whopping 1401 commits. You can view the changelog here and see what we’ve been busy working on: https://github.com/woothemes/woocommerce/blob/v2.2-beta-1/readme.txt#L129

    Before going into the features, developers should be aware of the following changes:

    1. Order statuses are no longer taxonomy based – the post status is used. This makes order queries lighter, but custom order queries may need to be updated.
    2. Orders can now be retrieved using the get_order() wc_get_order() function.
    3. Orders can be created using the new wc_create_order() function.
    4. Gateways can now handle refunds by declaring support for the ‘refunds’ feature, and including a process_refund() method (see PayPal Standard in WC core for an example).
    5. Gateways can pass the payment_complete() method a transaction ID to have it stored in a standardized format.
    6. v2 of the API which includes PUT/POST/DELETE methods is included. v1 of the API is still present until v3 is eventually released.

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

    Rest API v2

    Version 2 of the API introduces PUT/POST/DELETE support for Coupons, Orders, Products and customers and will really widen the possibilities of integrating with WooCommerce from external apps. Full documentation for v2 of the API should be ready soon, but it’s there if you want to play.

    Massive props to SkyVerge (Max and Justin in particular) for their contributions to the API.

    Refunds

    Refunds has been a feature we’ve wanted to tackle for a long time, but has been put back due to it’s scope a few times. We’re proud to finally have this feature built.

    Refunds consists of two parts;

    1. An API for Payment Gateways to handle refunds directly though code.
    2. An interface to handle refunds from the orders UI.

    The greatest challenges with refunds were;

    1. Keeping reports accurate after partial refunds.
    2. Having a simple interface to handle the refund process…
    3. …which led us to redesign the order item and order totals panels and combine them.
    4. Modifying our data structures (particulary for line items) to support the above.

    Here is an example of the new UI for order totals and items:

    You’ll notice shipping, taxes, fees are all displayed in the same area which should improve usability.

    This is what the UI looks like when doing a refund:

    2014-08-01 at 10.06

    Unfortunetely, due to the structure of data in 2.1 and below (particulary the way in which taxes were stored, never at line level) we’ve had to sacrifice the tax columns and partial refund functionality for legacy orders – but going forward, all new orders will benefit from the new functionality.

    We’re keen to hear your feedback about refunds in 2.2!

    Improved language file handling

    One thing we started noticing with recent releases was that the filesize for WooCommerce was huge. 2.1.12 was over 8mb. This can make updating difficult for example if there are upload limits.

    The reason for the size; localisation files. Uncompressed we’re talking 32mb of PO and MO files in core.

    To resolve this, 2.2 includes a language pack downloader. PO and MO files will no longer be bundled with the plugin – they will be downloadable from your dashboard if you have the WPLANG constant set, or from a git repository if you wish to grab them manually.

    Give us your feedback and get involved

    We’re happy to hear your feedback about 2.2 and would appriciate any bug reports going directly to Github.

    Download 2.2 Beta 1

    If you find a bug with the beta, please ensure you prepend the ticket title with [2.2] 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.1.12 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 are only a few changes in this release which can be found in the changelog. A total of 22 commits made it into this fix release.

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

  • The WooCommerce 2.1.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 are only a few changes in this release which can be found in the changelog. A total of 6 commits made it into this fix release.

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

  • Whilst work continues on Prowling Pangolin, the team at WooThemes are still fixing bugs for 2.1 as they are reported. Today, the WooCommerce 2.1.10 release is  available via WordPress.org or automatic update in your administration panel. Thanks to all of our contributors who’ve been helping out.

    All the changes are relatively small and can be found in the changelog. A total of 31 commits made it into this fix release.

    Thoughts? Feedback? Tell us on the forums.

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

  • The WooCommerce 2.1.9 release is now available via WordPress.org or automatic update in your administration panel. This fix release is the result of the continued effort of our contributors who provided fixes and bug reports. Thank you for helping out!

    All the changes are relatively small and can be found in the changelog. A total of 38 commits made it into this fix release.

    One thing we did add for the devs out there was an option in System Status > Tools for disabling shipping method/rate caching. Useful when debugging shipping.

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

  • The WooCommerce 2.1.8 release is now available via WordPress.org or automatic update in your administration panel. This fix release is the result of the continued effort of our contributors who provided fixes and bug reports. Thank you for helping out!

    All the changes are relatively small and can be found in the changelog. A total of 55 commits made it into this release, making this a decent fix release.

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

  • The WooCommerce 2.1.7 release is now available via WordPress.org or automatic update in your administration panel. This fix release is the result of the continued effort of our contributors who contribute code and others who have reported issues with the plugin. Thank you for helping out!

    All the changes are relatively small and can be found in the changelog. A total of 73 commits made it into this release, bundling them into one larger release makes it a decent fix release.

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

  • The WooCommerce 2.1.6 release is now available via WordPress.org or automatic update in your administration panel. This fix release is the result of the continued effort of our contributors who contribute code and others who have reported issues with the plugin. Thank you for helping out!

    All the changes are relatively small and can be found in the changelog. A total of 91 commits made it into this release, bundling them into one larger release makes it a decent fix release.

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

  • In the 2.1.4 version we introduced a bug that caused the prices of variations to be hidden when the manage stock field was left empty. Sorry about that. This and a couple other small bug fixes are now available in the WooCommerce 2.1.5 release, available via WordPress.org or automatic update in your administration panel.

    You can find the critical bug fix in the commit details, or the relevant issue on our tracker.

    Just 14 commits in total went in this release, which makes it a really small fix release, but as it solves a big bug we decided to push it out immediately. All the changes can be found in the changelog.

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