Devise Routing Error on Gem Update (Rails 3, Devise + Omniauth)?

You can hack it by changing line 338 in devise-1.4.2/lib/devise/rails/routes. Rb to: match "#{path_prefix}/:action/callback", #:action => Regexp. Union(mapping.to.

Omniauth_providers. Map(&:to_s)) Be warned that this is only an ugly hack not a final solution to the problem! Make sure you have set devise :omniauthable, :omniauth_providers => :twitter in your devise model (e.g. User).

You can hack it by changing line 338 in devise-1.4.2/lib/devise/rails/routes. Rb to: match "#{path_prefix}/:action/callback", #:action => Regexp. Union(mapping.to.

Omniauth_providers. Map(&:to_s)), Be warned that this is only an ugly hack not a final solution to the problem! Make sure you have set devise :omniauthable, :omniauth_providers => :twitter in your devise model (e.g. User).

Upgrade to forgery-0.4.0 if you're using it with with Devise/Omniauth. We were extending some base ruby classes (always a great idea, I know) and this somehow caused issues in Devise. Version 0.4.0 no longer extends any ruby base classes and should be completely safe to include.

Let us know if you have any issues at github.com/sevenwire/forgery. Thanks!

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.