Devise从1.1.5升级到1.4.5导致错误的参数数量错误 [英] Devise upgrade from 1.1.5 to 1.4.5 causes Wrong Number of Arguments error
本文介绍了Devise从1.1.5升级到1.4.5导致错误的参数数量错误的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!
问题描述
我刚刚从Devise 1.1.5升级到1.4.5,用于Rails 3.1(1.1.5似乎造成bcrypt gem版本问题)。
I just upgraded from Devise 1.1.5 to 1.4.5 to use with Rails 3.1 (1.1.5 seems to cause a bcrypt gem version problem).
现在user_signed_in?抛出错误的参数数(1为2)
Now user_signed_in? throws " wrong number of arguments (1 for 2)"
Stack trace is:
devise (1.4.5) lib/devise/models/authenticatable.rb:89:in `serialize_from_session'
devise (1.4.5) lib/devise/rails/warden_compat.rb:27:in `deserialize'
warden (1.0.5) lib/warden/session_serializer.rb:31:in `fetch'
warden (1.0.5) lib/warden/proxy.rb:182:in `user'
warden (1.0.5) lib/warden/proxy.rb:278:in `_perform_authentication'
warden (1.0.5) lib/warden/proxy.rb:90:in `authenticate'
devise (1.4.5) lib/devise/controllers/helpers.rb:48:in `current_user'
devise (1.4.5) lib/devise/controllers/helpers.rb:44:in `user_signed_in?'
app/controllers/main_controller.rb:24:in `index'
actionpack (3.1.0) lib/action_controller/metal/implicit_render.rb:4:in `send_action'
actionpack (3.1.0) lib/abstract_controller/base.rb:167:in `process_action'
.....
?
解决方案
我运行 rake tmp:clear
并更改了我的会话名称,在 session_store.rb
I ran rake tmp:clear
and changed the name of my session in session_store.rb
Woodhack :: Application.config.session_store:cookie_store,:key => '_NEW_NAME_HERE_session'
这篇关于Devise从1.1.5升级到1.4.5导致错误的参数数量错误的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!
查看全文