spree_i18n | I18n translation files for Spree Commerce | Ecommerce library

There was no need for special ability after all in this case. The Spree::BaseController sets the correct permissions to grant the aimed access, unlike Spree::Admin::BaseController. To keep the CSS style consistent, an explicit layout statement is required.

I think you missing dev library of mysql:

On ubuntu

Make sure your Gemfile have ruby and rails version. Also, you should've .ruby-version file on the root of your project.

Try these commands in the following order:

This fixed the problem for me: I just removed the line

I removed spree_globalize from my Gemfile.lock file and then removed spree_globalize Error stopped occurring.

The problem you're encountering now is a common one with versioning of Spree add-ons. They tend to be pinned to one version of Spree, so when you upgrade you often end up having to fork the add-ons, modify the dependency requirements, test, maybe fix, then use it, upstream it. It's a bit of a hassle but it ends up working so that there's good support of add-ons compatible with every version of Spree.

In the world of Spree there's a consistent format to versioning. Spree and add-ons tend to have branches matching the version of Spree. For example, 3-1-stable for Spree and all add-ons. Unless you require something from Spree 3.2, I recommend sticking with 3.1 since it's been out for months and most of the commonly-used add-ons have been updated and tested for it. Regardless of the version you go with, make your add-ons use the same version as Spree!. Life will be a lot easier that way. (Sidenote: I tend to hang at least one minor version back to wait for add-ons to be updated, bugs to be sussed-out before upgrading)

Here's what I do in my Gemfile to enforce consistency. You'll notice I'm request versions 3.1 of the add-ons and pointing to their 3-1-stable branches.