Issue with Rails 4.2 (beta)

[trinode]

Hi there,

I'm not sure what has changed / will be changing in 4.2 but it looks like merge! is no longer available on some objects:-

if I have
devise_for :users
I get the following errors:-

NoMethodError: undefined method `merge!' for #<ActionDispatch::Routing::Mapper::Scope:0x000000062cded0>
/usr/local/rvm/gems/ruby-2.1.2/gems/devise-3.3.0/lib/devise/rails/routes.rb:457:in `ensure in with_devise_exclusive_scope'
/usr/local/rvm/gems/ruby-2.1.2/gems/devise-3.3.0/lib/devise/rails/routes.rb:457:in `with_devise_exclusive_scope'
/usr/local/rvm/gems/ruby-2.1.2/gems/devise-3.3.0/lib/devise/rails/routes.rb:248:in `block (2 levels) in devise_for'
/usr/local/rvm/gems/ruby-2.1.2/gems/devise-3.3.0/lib/devise/rails/routes.rb:351:in `block in devise_scope'
/usr/local/rvm/gems/ruby-2.1.2/gems/actionpack-4.2.0.beta1/lib/action_dispatch/routing/mapper.rb:932:in `block in constraints'
/usr/local/rvm/gems/ruby-2.1.2/gems/actionpack-4.2.0.beta1/lib/action_dispatch/routing/mapper.rb:808:in `scope'
/usr/local/rvm/gems/ruby-2.1.2/gems/actionpack-4.2.0.beta1/lib/action_dispatch/routing/mapper.rb:932:in `constraints'
/usr/local/rvm/gems/ruby-2.1.2/gems/devise-3.3.0/lib/devise/rails/routes.rb:350:in `devise_scope'
/usr/local/rvm/gems/ruby-2.1.2/gems/devise-3.3.0/lib/devise/rails/routes.rb:247:in `block in devise_for'
/usr/local/rvm/gems/ruby-2.1.2/gems/devise-3.3.0/lib/devise/rails/routes.rb:223:in `each'
/usr/local/rvm/gems/ruby-2.1.2/gems/devise-3.3.0/lib/devise/rails/routes.rb:223:in `devise_for'

[Fudoshiki]

#3153

[trinode]

Ahh, thanks, I looked for open issues, I didn't see the pull request! I'll track that pull request. I'm not sure if I should close this or leave it open so that other's see the pull request.

[Fudoshiki]

waiting for merge, then close

[wafcio]

I have found another issue with devise and rails 4.2 on branch lm-rails-4-2 devise should have dependency for https://github.com/plataformatec/responders because without this gem devise doesn't work.

[lucasmazza]

Everything should be handled over #3153, so just track that Pull Request and if you are testing the 4.2 branch please report any problem that wasn't discussed before on that thread. Please do not open duplicated issues regarding Rails 4.2+.

[trinode]

@lucasmazza I came here because I'm a user of devise, I had an issue so I checked open issues, there was none, so I opened one. I can imagine another one getting opened shortly, normally the issue stays open until it's fixed and Your commit would mention the fix in the commit, which should automatically close the issue when it's actually fixed ie "Add Rails 4.2 compatibility - fixes #[issue_no]".

https://help.github.com/articles/closing-issues-via-commit-messages

It's not my repo and you can run it the way you choose, of course. I just think that's confusing for people like myself who came to check if the issue was being worked on / reported.

[nextbase]

Still doesn't work for me.

[jaythaceo]

Add this to gem file instead. run bundle install, rake db:migrate.. worked for me
" USE IN PRODUCTION at OWN RISK"
gem 'devise', :git => 'https://github.com/plataformatec/devise.git', :branch => 'lm-rails-4-2'

[rafaelfranca]

@jaythaceo or you can just use devise 3.4.1

[jaythaceo]

Thanks a lot

[tunsmart]

wow, thanks @rafaelfranca , 3.4.1 worked perfectly

[amritdeep]

Thanks Guys, It help me lot. Devise 3.4.1 work perfectly for rails 4.2.5.2.