commerce 8.x-2.0-beta4

Bug fixes
New features
Insecure

Major changes since beta3:

Order receipt emails

Default order receipt email
HTML emails rendered from a Twig template, easy to override and customize.
Enabled per order-type. Supports sending a copy to another email (Receipt BCC setting).
Requires the Swift mailer module or similar alternative, since Drupal core doesn't support HTML emails by default.

commerce 8.x-2.0-beta3

Bug fixes
Insecure

Highlights:

  • Greatly improved permissions
  • Rewritten order refresh process
  • We have started a Code recipes documentation section
  • The underlying commerceguys/intl library has updated the CLDR dataset to v30, bringing many currency formatting fixes
  • Releases of Inline Entity Form (beta1) and State Machine (beta3)

Check the change records for notes on code-breaking changes.

commerce 8.x-2.0-beta1

Bug fixes
New features
Insecure

First production ready release. From this point on an upgrade path is supported between 2.x releases.

Changes since 8.x-2.0-alpha4:

commerce 8.x-2.0-alpha4

Bug fixes
New features
Insecure

Important: Commerce 2.x alphas are NOT production ready. No upgrade path is provided between alphas. A full reinstall is needed each time.

Blog post: https://drupalcommerce.org/blog/44305/commerce-20-alpha4-released
Installation instructions: http://docs.drupalcommerce.org/v2/install.html

Changes since 8.x-2.0-alpha3:

commerce 7.x-1.13

Security update

This is a security release improving the access control of product SKU / title lists returned by the Commerce Product module for use in the product reference field's autocomplete widget. For more information, refer to the SA-CONTRIB-2016-019 security advisory.

commerce 7.x-1.12

Bug fixes
New features
Insecure

This release was a long time in coming and is packed full of bug fixes, great new features, and a variety of performance improvements and API documentation additions.

This release includes a breaking change: because of changes summarized in #2697017: Revert the EntityFieldQuery based product matcher and arbitrary options list limit, product reference fields may not be showing the expected number of options. The solution is to edit the field and supply a sufficiently large number for your site's use case.

Notable updates include:

  • A new Views filter to restrict the results of line item Views to line items that are actually still referenced by orders. (In other words, no more accidentally including "orphaned line items" in such Views.
  • A new Views field handler that finally lets you edit product attributes in the cart! It's about time, eh? : D
  • Interface improvements / tokens to include an order's selected payment method on the review page and in e-mails / other communications.
  • New hooks including: (read more for the full list)

commerce 8.x-2.0-alpha3

Important: Commerce 2.x alphas are NOT production ready. No upgrade path is provided between alphas. A full reinstall is needed each time.

Blog post: https://drupalcommerce.org/blog/44226/commerce-20-alpha3-released
Installation instructions: http://docs.drupalcommerce.org/v2/install.html

Changes since 8.x-2.0-alpha2:

commerce 8.x-2.0-alpha2

Bug fixes
New features
Insecure

Blog post: https://drupalcommerce.org/blog/43978/commerce-20-alpha2-released

Reminder: Commerce 2.x alphas are NOT production ready. No upgrade path is provided between alphas, a full reinstall is needed each time.

Changes since 8.x-2.0-alpha1:

commerce 8.x-2.0-alpha1

Initial alpha.

Read the release announcement, and follow the installation instructions to try it out.

Note: Make sure to use the latest -dev version of Drupal 8, cause 8.0.1 has known bugs that affect Commerce.

commerce 7.x-1.11

Bug fixes
Insecure

Includes a critical bug fix (#2407319: commerce_customer_field_widget_form() must set #parents before calling field_attach_form()) that was breaking the address form on the order add/edit page under Addressfield 1.0-rc1 and later.

commerce 7.x-1.10

Security update
Bug fixes
New features
Insecure

Drupal Commerce 1.10 is primarily a bug fix release that addresses the vulnerability described in SA-CONTRIB-2014-087 - Drupal Commerce - Information disclosure and a variety of smaller bugs. The information disclosure fix includes an update hook that cleans usernames created by a default checkout completion rule to remove the host name from e-mail addresses used as usernames.

commerce 7.x-1.9

Bug fixes
New features
Insecure

As of this release, Drupal Commerce on depends on Drupal 7.22 or greater for its field_info_field_map() function. Drupal 7.24 and 7.26 were security releases anyways, so upgrading is a Good Idea (TM).

commerce 7.x-1.8

New features
Bug fixes
Insecure

Drupal Commerce 7.x-1.8 is primarily a bug fix release, though it brings with it new features and UI improvements related to internationalization and our Views integration. Thanks in large part to bojanz, it is now possible to translate interface text configured via settings forms and field forms using i18n. For more information, follow his meta translation issue.

To update, simply replace your existing version of Drupal Commerce with the 7.x-1.8 release and run update.php.

Changes since 7.x-1.7 (27 commits):

  • #2046841 by rszrama: update the docs for the back_value parameter of hook_commerce_checkout_page_info() to clarify that it's specifically for going back to previous pages, not exiting from the checkout process via the cancel button.
  • #1940794 by jonhattan: remove unnecessary Rules dependencies from the Product and Price module .info files.
  • #1850642 by facine: correctly use the hidden value for symbol and code placement keys in currency info arrays.
  • #2046449 by zterry95: fix the currency formatting for CNY.
  • Add some missing parameter documentation to commerce_cart_add_to_cart_form().

commerce 7.x-1.7

Bug fixes
Insecure

This is a minor maintenance release primarily pushed to fix the regression in Commerce 7.x-1.6 that prevented product image fields injected into node displays from linking to their node displays (as opposed to the product admin URLs). The release also addresses minor issues in the checkout pane settings form and checkout form validate / submit handlers.

Changes since 7.x-1.6 (10 commits):

commerce 7.x-1.6

New features
Bug fixes
Insecure

Note: if your site has non-required multi-value product reference fields that contain empty values, you may see notices when they render. If so, this has been patched here. Apply the patch or update to 7.x-1.x-dev to watch the notices magically disappear.

API changes

There are a few new functions available to use in this release noted below, but worth special mention are two very minor API changes that may require you to update code. They are:

  1. As part of #1361562, we changed commerce_field_activate() to not automatically clear the field cache if it enables a previously disabled field. If you were depending on it to flush the cache before, you should now examine its return value and clear it yourself if need be.
  2. In #1863776, we reduced the footprint of the Add to Cart form by no longer storing the entire entity in the form arguments in whose context the Add to Cart form is being rendered. Per the patch, we instead only store the entity ID and leave it up to functions interacting with data in the entity to load it themselves.

Changes since 7.x-1.5 (54 commits):

commerce 7.x-1.5

New features
Bug fixes
Insecure

As of the previous release, Drupal Commerce depends on Drupal >= 7.15.

Drupal Commerce 1.5 is a maintenance release incorporating 42 patches from 21 contributors around the world. This includes 14 new contributors to the project, some of whom scored their first commits as Drupal contributors. : )

These patches fixed a variety of bugs, improved performance, and added new features to the core of Drupal Commerce, including:

  • Improved Rules integration! We fixed a longstanding issue where conditions on pricing rules that loaded orders caused recursion in the calculation process. We also added a condition to compare against the quantity of products of a particular product type on an order.
  • Product revisions are now integrated with Views, including a tab on product admin URLs to view the revision history and a relationship to include revision information in product Views.
  • Customer order view pages now have local action links for administrators to quickly jump to the order edit form for the order.
  • Improved entity access control, including the resolution of a longstanding issues pertaining to line item access.

See the full list of changes in the notes below.

commerce 7.x-1.4

New features
Bug fixes
Insecure

Drupal Commerce now depends on Drupal >= 7.15.

Drupal Commerce 1.4 is a maintenance release incorporating 87 patches from 40 contributors around the world. These patches add a variety of new features to the core of Drupal Commerce and make it more performant and suited to international usage. The release notes summarize some of the main changes in the new version and includes a full changelog for the curious.

New features

The Add to Cart form and checkout form have both seen improvements. Most notable on the checkout form is the new setting to allow copying of fields from one customer profile to another. This feature was a part of the Commerce Shipping module but was moved to core and designed to work server side across multiple checkout pages and even between customer profile types that may have different fields. The Account information checkout pane was also updated to support e-mail address verification through double entry.

We included a variety of Views integration improvements, including adding a missing handler, updating area handlers for Views 3.5, supporting redirect destinations on our entity operation links, and adding a node filter to only show product display nodes.

Finally, we added a few features to make it simpler for site builders to build product pricing rules. Foremost among these is a new Price comparison condition that supports multi-currency price comparisons and accepts input in major currency unit decimal values instead of minor unit integer values (i.e. compare in Dollars or Euros instead of Cents). We also added a read only computed property allowing you to use the generic Data comparison condition against these major unit decimal values.

commerce 7.x-1.3

New features
Bug fixes
Insecure

I'll update this node to include a summary of changes in a bit. For now, just be sure to run update.php after updating to the new version.

Change log

Changes since 7.x-1.2 (64 commits):

commerce 7.x-1.2

Security update
New features
Bug fixes
Insecure

Drupal Commerce 1.2 represents the efforts of 25 credited contributors and many others who reported bugs and usability improvements and helped test the solutions. This release primarily improves Drupal Commerce's performance and usability while including a variety of minor bug fixes, API improvements, and a minor security fix as described in SA-CONTRIB-2012-014 - Drupal Commerce - Cross Site Scripting (XSS).

Read on for a brief description of the changes since Drupal Commerce 1.1, notes on updating from previous versions, and a full change log of commits.

commerce 7.x-1.1

New features
Bug fixes
Insecure

Drupal Commerce 1.1 is here! This release contains 95 commits credited to 30 different contributors that fix a variety of bugs and make some minor feature and API improvements.

Drupal Commerce 1.1 details

Drupal Commerce 1.0 has proven to be very stable overall, with no critical showstoppers arising in the last three months that would have forced a point release. This is thanks in large part to the automated testing systems set up by Damien Tournoud and rfay and the variety of core automated tests contributed and maintained by the community.

Instead we get to release a 1.1 on our own schedule the brings improvements to a variety of areas at once, including:

The full list of changes can be viewed in the changelog below. Some items represent minor API changes or additions, and these are noted in the notes below. The changes to the theme layer should not affect existing CSS, as classes were preserved even where an improper span was changed to a div.

commerce 7.x-1.0

New features
Bug fixes
Insecure

At long last, the final 1.0 release is here! We've been supported by so many contributors and other community members, and we couldn't be happier. Thanks so much to everyone who helped with patches, bug reporting, support, and documentation. We're extremely happy with the way things have turned out, and it was a lot of fun to roll the release "live" with a screencast and pictures at DrupalCon London.

commerce 7.x-1.0-rc3

Bug fixes
Insecure

This release simply fixes a regression introduced by #1223046 in the RC2. See the previous release notes for what's substantively changed since the RC1.

commerce 7.x-1.0-rc2

New features
Bug fixes
Insecure

Note: We rolled an RC3 to fix a regression introduced by #1223046.

This release incorporates a number of very helpful bug fixes for developers. We're paying special attention to mitigating as many errors as possible for developers working with the EntityMetadataWrapper, and we wanted to get these fixes out to you as soon as possible. The full list of changes are below, but the primary things for you to take note of are:

  • Products with NULL prices will no longer cause wrapper errors. They will instead be treated as disabled products and will therefore be unpurchasable.
  • When entities referenced by other entities are deleted, we no longer use the entity metadata wrapper to avoid a majority of the errors that were being reported. We're now doing a direct deletion ourselves, which is just as well since we want to ensure references are deleted from every language in a reference field.
  • Our entity access function has been seriously cleaned up, meaning all entity permissions should actually work properly now. This does mean you need to ensure your users have access to view their own orders if you want them to have access to them on their account Orders tab.

commerce 7.x-1.0-rc1

New features
Bug fixes
Insecure

With this release, we're moving forward in our development cycle to the release candidate phase. While in release candidate, we're doing aggressive testing and bug fixing on any issues that pop up. If all goes well over the next few weeks, we'll call it a 1.0 in preparation for DrupalCon London. We may or may not have additional release candidates depending on whether or not any serious bugs get reported or database updates are required.

Update instructions:

If you are updating from a previous release, you should first test the new release in a development environment. Do not attempt to update initially on your live site in case something goes wrong!

You should start the process by updating all of your Drupal Commerce dependencies to the latest tagged releases. This includes Address Field 1.0-beta1, Ctools 1.0-beta1, Views 3.0-rc1, Entity API 1.0-beta10, and Rules 2.0-beta2. Then update to the latest version of Drupal Commerce and run your site's update.php.

If you're updating from a version prior to 1.0-beta4, you should also review the notes associated with that release. There were reported API and Rules integration changes that you must take into account.

Additionally, since beta4, three changes will require manual intervention:

commerce 7.x-1.0-beta4

New features
Bug fixes
Insecure

Notice: if you are updating to beta4 from a previous version, you should use instead the latest dev version to ensure your permissions are automatically updated when you run update.php. If you have already updated straight to beta4, you just need to re-enable permissions for your roles manually.

Key points:

  • Token names and Rules parameter / variable names have changed to uniformly use the commerce prefix.
  • Permission names have been unified around a single entity access control system.
  • This release (as those before it) still requires the latest dev versions of our dependencies; as soon as Views and Rules have new releases, we'll be pegging our release compatibility against actual releases for those projects.
  • You must run update.php for your custom Views / Rules to be updated and for your role permissions to be converted to the new names.
  • You should NOT update until any contributed modules you're using specify they are compatible with this release or later.

commerce 7.x-1.0-beta3

New features
Bug fixes
Insecure

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.

commerce 7.x-1.0-beta2

Insecure
Some files were missing on the Drupal Commerce 1.0 beta1 release, because of a technical issue in the Git-to-CVS. This beta2 release is the exact same release, but includes the missing files. See the original release announcement of beta1 for details.

commerce 7.x-1.0-beta1

New features
Bug fixes
Insecure
Some files were missing in this release because of a technical issue in the Git-to-CVS export. The updated beta2 release includes these files with no other changes.

The full release announcement will come in the morning, but it is indeed finally here. A tremendous amount of work has gone into this release, and we're excited to offer it up for your consumption. The more eyes on the code and functionality the better. As this first beta is about function over form, you may find areas where the UI is in need of some love (particularly the order view page). However, there are open issues addressing these and other issues, so please feel free to join in with a patch or post an issue if you find a new bug.

Demo site: http://demo.commerceguys.com/dc/

The big new features to look for are of course sales tax / VAT support and the new dynamic order total field. In the checkout form, we also have Rules powered anonymous checkout, so you can finally decide how to handle user account creation through the UI. This release also includes various API enhancements recommended by developers who are already trying Commerce out in some very challenging scenarios.

That said, the next thing to happen will be you giving Commerce a try and building those magic contributed modules based on the core systems / APIs to provide essential non-core features. There are already several payment methods supported in contrib, and we'd love to see even more before 1.0.

Please note that to run the beta, you do need the latest dev versions of all of our dependencies. To get up and running quickly, you can follow the directions in my pre-beta blog post, replacing the version of Commerce linked there with this beta. : )

commerce 7.x-1.0-alpha5

New features
Bug fixes
Insecure

The alpha 5 release benefited from the efforts of many contributors at the Paris Drupal Commerce sprint from July 17-21, 2011. A lot of the volunteer effort went into providing more complete Token / Entity / Rules / Views integration for the various modules. As a result, we were able to remove the anonymous checkout settings form in favor of an entirely Rules based account creation process. We also were able to turn the shopping cart form into a View through the use of some tricksy post-processing.

The shopping cart saw other improvements as well. Line items in shopping cart orders will now "refresh" as expected if the price of any product on the order changes. We also fleshed out the cart API to make it easier to manipulate the cart contents and determine when an order is actually considered a shopping cart.

commerce 7.x-1.0-alpha4

New features
Bug fixes
Insecure

The last week has seen a flurry of activity that accounts for about half of the commits for the last 6 weeks. This is due in large part to the great number of patches contributed from other developers, giving me plenty to review and build on. This release contains more solid Entity / Rules / Views integration and an improved shopping cart workflow. It also contains my first uses of EntityFieldQuery and the Entity Metadata Wrapper, two critical APIs for building Fieldable Entity based systems. Once again all our SimpleTests pass, too, though we're still in need of a lot more.

The pièce de résistance of alpha 3 was the dynamic Add to Cart form, which has seen bug fixes in this release to address inconsistencies in the dependent attribute display. I'm not sure if I can top the awesomeness of that form in this release, but the Rules powered dynamic pricing system at least comes close.

commerce 7.x-1.0-alpha3

New features
Bug fixes
Insecure

Alpha 3 includes various updates to unify language and fields across the user interfaces, with a much improved order edit form that is actually useful now (using vertical tabs, no less). The customer profile reference widget was improved to actually be usable on order edit forms, but it still needs a little bit of love to avoid creating duplicate profiles when it's not necessary.

We also fixed currency handling in relation to the different types of Price field widgets and managed to get every currency defined with much better currency formatting thanks to das-peter. He also helped get our Entity API and Rules integration a little more up to date with more issues pending review in the queue. : )

Work begun last release cycle on the Payment system was pushed forward, with a lot of work done to support credit card payments on-site. A proof-of-concept module was released in the form of Commerce Authorize.Net that you can use as a guide to developing integration with other payment gateways.

commerce 7.x-1.0-alpha2

New features
Bug fixes
Insecure

Alpha 2 represents a ton of work on the systems in general and on the Payment module specifically. Contributed modules may actually begin to integrate payment components into the checkout process, as Commerce PayPal does for PayPal WPS. Transactions can actually be created and associated with orders, and are visible on an order's Payment tab in a View that includes a form for adding new payments. There's still work to be done, but it is now ready for some outside eyes to take a serious look at the way modules will have to integrate with checkout and the payment terminal.

I've recently made an effort to document all the info hooks int he Commerce modules in the Specification handbook on drupalcommerce.org. This work turned up some API inconsistencies that have been addressed. Additional attention still needs to be paid to the Entity and Field implementations to detect similar issues and develop a working specification.

The last couple of days have also seen bug fixes to get Commerce running on Drupal 7.0-beta1. Similar work was done on the Address Field module, so I rolled that into an alpha1 release for some serious testing and bug reporting as well.

commerce 7.x-1.0-alpha1

This marks the first point release of Drupal Commerce, an alpha that includes all of the major core systems, some more mature than others. The product, product reference, line item, order, cart, and checkout modules have received a fair amount of attention but are by no means perfect. The payment and customer modules are more recent additions and could use a greater bit of love. The shippable product module is non-existent but will really just be a matter of implementing new fields for products and is not centrally important.

There is a brand new demonstration site that includes all the front-end features, including product display within the node context, the shopping cart, and checkout forms. This will be followed by an admin demo shortly, but in the meantime those at DrupalCon Copenhagen who want to give the backend a test drive can come by the Commerce Guys booth.

Pages

Subscribe with RSS Subscribe to Releases for Commerce Core