Upgrading to Spree 1.2.0

[Maxoos]

When upgrading from 1.1.2 to 1.2.0, do i need to do anything else other than updating the gem file and running bundle install?

Thanks,

[Trung LE]

you do need to run rake task to install new migration files

Trung LE

Sent with Sparrow

On Wednesday, 5 September 2012 at 11:10 PM, Maxoos wrote:

When upgrading from 1.1.2 to 1.2.0, do i need to do anything else other than updating the gem file and running bundle install?

Thanks,

--

You received this message because you are subscribed to the Google Groups "Spree" group.

To view this discussion on the web visit https://groups.google.com/d/msg/spree-user/-/bgcfrinAANIJ.

To post to this group, send email to spree...@googlegroups.com.

To unsubscribe from this group, send email to spree-user+...@googlegroups.com.

For more options, visit this group at http://groups.google.com/group/spree-user?hl=en.

[Michael Sevestre]

Well I ran into a few issues updating from 1.1.2 to 1.2.0
1 - has_role? has been renamed to has_spree_role? So if you have some custom logic using has_role?, that need to be updated as well
2 - Don't forget to specify which User class should be used in your spree.rb initializer
3 - Installing the new migration with the rake task did not do the trick for me. It did not copy the migration from spree_core which I finally had to copy by hand.

Hope that helps,
Michael

[Maxoos]

Thank you!

About 2. Where is that written? In the release notes?

About 3. Rake db:migrate yes?

Thanks!

[Michael Sevestre]

2: Here
3: rake spree:install:migrations

--
You received this message because you are subscribed to the Google Groups "Spree" group.

To view this discussion on the web visit https://groups.google.com/d/msg/spree-user/-/-7d919ycV-kJ.

[Maxoos]

Thanks!

[Maxoos]

I have another issue, I seem to be missing JS in the admin section, everything is working in regular mode. Do I need to recompile assets or something?

On Wednesday, September 5, 2012 7:06:53 PM UTC+3, Maxoos wrote:

Thanks!

[German Garcia]

hopefully by now you've solved it, but just incase, this is mentioned here https://github.com/spree/spree/issues/1854

[ayupmeduck]

Recently did a upgrade and only found on deployment that a few users that had uppercase letters in their email addresses could no longer sign in. It seems that Spree, or perhaps spree_auth_devise, now sets the Devise case_insensitive_keys = [:email], though I have not yet located where this happens. If you have this problem then you will need an initializer to set it back to false like seems to have been pre 1.2.x:

# config/initializers/devise.rb
Devise.setup do |config|
  config.case_insensitive_keys = false
end