1.3 to 2.0
This guide covers upgrading a 1.3.x Spree store, to a 2.0.x store.


This guide has been written from the perspective of a blank Spree 1.3.x store with no extensions.
If you have extensions that your store depends on, you will need to manually verify that each of those extensions works within your 2.0.x store once this upgrade is complete. Typically, extensions that are compatible with this version of Spree will have a 2-0-stable branch.
Given that this is a major release, you may want to read through the 2.0.0 release notes to see what has changed before proceeding with this upgrade.

Upgrade Spree

For best results, use the 2-0-stable branch from GitHub:
gem 'spree', github: 'spree/spree', branch: '2-0-stable'```
Run `bundle update spree`.
## Bump jquery-rails
This version of Spree bumps the dependency for jquery-rails to this:
gem 'jquery-rails', '3.0.0'```
Ensure that you have a line such as this in your Gemfile to allow that dependency.
## Remove middleware
The two pieces of middleware previously inserted into `config/application.rb` have now been deprecated. Remove these two lines:
config.middleware.use "Spree::Core::Middleware::RedirectLegacyProductUrl"
config.middleware.use "Spree::Core::Middleware::SeoAssist"```
## Rename assets
In Spree 2, assets have been renamed.
In `store/all.css` and `store/all.js`, you will need to rename the references from `spree_core` to `spree_frontend`. Similarly to this, in `admin/all.css` and `admin/all.js`, you will need to rename the references from `spree_core` to `spree_backend`.
Additionally, remove references to `spree_promo` from these files. That component of Spree has now been merged with the Core component.
## Copy and run migrations
Copy over the migrations from Spree (and any other engine) and run them using
these commands:
rake railties:install:migrations
rake db:migrate
## Read the release notes
For information about changes contained with this release, please read the [2.0.0 Release Notes](http://guides.spreecommerce.org/release_notes/spree_2_0_0.html).
## Verify that everything is OK
Click around in your store and make sure it's performing as normal. Fix any deprecation warnings you see.
Last modified 11mo ago
Copy link
Edit on GitHub