Install

Works with Drupal: 7.x

Using Composer to manage Drupal site dependencies

Downloads

Download commerce-7.x-1.0-beta3.tar.gztar.gz 273.18 KB
MD5: e4da46e99b11fb772e386a0db242b5e2
SHA-1: dc37f169e024987193ec077bc3e41530661e4793
SHA-256: 9ed4220a40bf1f48cf852af77b2f09bbc66f2dc56ed64909edaae39ba27e9a9a
Download commerce-7.x-1.0-beta3.zipzip 382.99 KB
MD5: 442e1a6ec13ee20b32582015a11891fb
SHA-1: 0a01e76e0d838aef1130d0ed4bd9d518ba6610aa
SHA-256: b4c25f14d6f4bb2473fbe5b5c0f70b5b61b4aa1b0566d27042c8649bdaad3edb

Release notes

Drupal Commerce 7.0-1.0-beta3 comes almost two months after the initial beta releases (beta2 being a quick release to address missed files). A lot of work has gone into ferreting out some bugs as more developers put the Commerce modules to the test in varying situations. Even though a majority of the commits for this release are one-off bug fixes and feature improvements, this release does represent focused efforts in the following areas:

  • bojanz updated our Views integration to accommodate the new UI improvements in Views after participating in the Views UI sprint himself.
  • We've improved our Rules integration with support for Rules' "unchanged" entity parameters and additional actions and conditions. Of particular note is the new "Order address component comparison" condition that simplifies the process of configuring a rule to be contingent on some aspect of an order's address.
  • Usability improvements were contributed from several new contributors, standardizing interface elements and removing some unnecessary items. Combined with the new address condition, the Tax system has received particular UX attention. It still has a ways to go, but the situation is much improved over beta2.
  • We've made changes to better accommodate ongoing development in a few more contributed modules: Features, Entity translation, and Title.

Dynamic Pricing Fixes

Finally, and most significantly, we resolved a deep underlying issue that was manifesting itself in a variety of bugs pertaining to product prices. This involved changing our approach to handling price amounts, which we've stored in the database as integers and converted to decimals upon load and presave. Instead we now handle the price amount as an integer until the point of display. Developers should take note that they may need to update their price handling, particularly when communicating prices to payment gateways. The most common change involves using the API function commerce_currency_amount_to_decimal() on price amounts when transmitting them to a payment service to convert them to the decimal values commonly expected by payment APIs. Additionally, payment transaction amounts should be set as integers, converting decimal values using commerce_currency_decimal_to_amount() as necessary. See this commit to Commerce CyberSource for examples.

Run update.php

To deal with some legacy data that may exist in price field data arrays, there are several update functions that you'll need to run. If you have large amounts of products, line items, and/or orders, please be warned that there are updates for each of these entities loading and resaving them all 50 at a time.

For more information, refer to: #1124416: Revise the way we handle price amount values

It's exciting, too, that for the time being our "needs review" and "reviewed and tested by the community" queues are completely empty. Yay!

All 83 commits since the beta2 release are listed here:

Created by: rszrama
Created on: 23 Apr 2011 at 06:29 UTC
Last updated: 1 Aug 2018 at 23:53 UTC
New features
Bug fixes
Insecure

Other releases