Install

Works with Drupal: 7.x

Using Composer to manage Drupal site dependencies

Downloads

Download tar.gz 20.31 KB
MD5: 5147c42fa6f5f2f60517d3d3d745a24d
SHA-1: 59d5c568d42b2c67e240b23f30d61c42dce7c923
SHA-256: e65bd92fda4f645bfa311c028598bd2fd222f0f73ab14042872bdd1082c45e9a
Download zip 28.36 KB
MD5: d9da1ab94f225f44a8cac0c4a8bf5b86
SHA-1: a3cbc588e18d536c5a56afddc35b933abfc9206c
SHA-256: d97754d131e4a4e9cde0454613806e00e02eefa4a70b9c1d42fa8f64f0c477f6

Release notes

It's been about a year since I started working on shipping for commerce.

I had hoped that the work Ryan has made on the 2.x would have made the 1.x branch obsolete, but after all the work put into the 2.x branch some key features/hooks possibilities that makes the 1.x branch very flexible to work with from a developer's point of view, has still not been completed.

Thus I'm now creating the official 1.0 release, as commerce shipping has all the features I originally envisions when I started working with this and then some, and I haven't been seeing any bug reports lately.

There isn't much new since rc3, the main thing is the addressfield plugin that makes it possible to copy billing address to shipping and a few bug fixes.

So should all be using the 1.0 release?

Probably not. While the 2.x branch has not yet delivered what I want for a shipping module as a developer, it is where the future of the project lies. It has a lot cleaner architecture that with time should make it possible to make better Rules integration, customize contrib shipping modules and use several instances of the same shipping method/service. The naming convention is a lot clearer and the flat rate module is more flexible. All of these things are a great asset, but one thing that's currently lacking is the ability to select shipping method along with inputting your address and getting the calculation right. This is currently not possible with the 2.x feature set, and is the most important thing missing for it to take over the 1.x spot as the recommended release. Site builders will not have any join of the API flexibility that the 1.x branch provides, and as such, they are most likely better of with the 2.x branch.

So while we get the missing things sorted out with the 2.x branch, you are free to choose either 2.0-beta1 or 1.0.

Created by: googletorp
Created on: 31 Dec 2011 at 16:14 UTC
Last updated: 11 Feb 2017 at 15:00 UTC
New features
Bug fixes
Unsupported

Other releases