Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Upgrading from Spree
From Spree 2.0 to 2.1
Spree 2.0 was the last version on rails 3. The 2.1 upgrade includes rails 4 and strong_params, which can require many changes to any custom code. It's recommended to upgrade to Spree 2.1 and then 2.2 before upgrading to solidus.
From Spree 2.1 to 2.2
Spree 2.2 made some major changes to the way adjustments are handled. Taxes and other adjustments are now best handled per-item (line_item/shipment) instead of on the order. This can be a difficult change so we recommend upgrading to Spree 2.2 before upgrading to Solidus.
From Spree 2.2, 2.3, or 2.4
We intend Spree 2.2, 2.3, and 2.4 to be upgradable directly onto Solidus. We've improved the migrations and added fixed a few issues which should make it an easier upgrade.
You may want to start with Solidus 1.4, the last version using Rails 4.2. Solidus 2.0 is the first version using Rails 5.
For more details please read
- Solidus 1.0.0 Release Notes
- Solidus 1.0.1 Release Notes (minor incompatibilities due to ransack security changes)
- Spree 2.3 Release Notes (if you are upgrading from 2.2)
- Spree 2.4 Release Notes (if you are upgrading from 2.2 or 2.3)
From Spree 3.0
Solidus is a fork of Spree 2.4, and has diverged from Spree 3.0, making this a little more difficult than other upgrades. We made some changes in Solidus 1.1 to ease this upgrade. For 3.0 users looking to upgrade we recommend upgrading to Solidus 1.4, the last version using Rails 4.2, as an intermediate step. Solidus 2.0 is the first version using Rails 5, and Solidus 2.1 removes methods which were deprecated in Solidus 1.4.
One major difference is that Solidus doesn't include Spree 3.0's change to a bootstrap frontend and backend.