Releases for Drupal Commerce

Release notes

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:

• Reworked the checkout form submission process to use separate validate / submit handlers and notify the customer when error messages appear below the fold on the form.
• Bug fixes and API improvements in the Tax system, particularly for sites where product prices are entered including VAT.
• Additional Rules actions and a default Rule to make the Add to Cart message configurable.
• Better theme support including improved markup for product fields injected into nodes.
• Updates to support the latest releases of Entity API, Rules, and Views.
• Definition of a few missing currencies (AED, MAD, MXN, VND).

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.

Release notes

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.

Release notes

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:

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.

Release notes

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

Release notes

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.

Release notes

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.