-
Notifications
You must be signed in to change notification settings - Fork 528
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Gem Load Error is: uninitialized constant ActiveModel::ForbiddenAttributesProtection #381
Comments
|
2.2.0 |
@marcosserpa maybe try adding the |
@BenMorganIO I already resolved all the problems of strong_parameters. And the problem is not at the application, but at the Gem Load, as you can see. :) It's at the line 208 of paranoia.rb. That has
if replace by
this problem does not happen anymore. Seems that the problem is because |
Hmmm... Can you try using master for me? gem 'paranoia', github: 'rubysherpas/paranoia' |
We had this guy get merged back in December: https://github.com/rubysherpas/paranoia/pull/371/files?w=1 |
Actually, should be core, correct? gem 'paranoia', github: 'rubysherpas/paranoia', branch: 'core' |
Yeah, I keep forgetting this guy is core and not master :p |
Resolved! ❤️❤️❤️❤️❤️❤️ |
KK, let me get a tiny version out for 2.2.1 so you don't have to rely on Github for this. |
Great! +1000 to you and ❤️ *1000! |
When Travis is finished, I'll merge and release: #382 |
Great! Really really thanks, pal! |
Guys, I'm trying to upgrade an application from Rails 3.2.22 to 4.0.13 and I'm getting
Gem Load Error is: uninitialized constant ActiveModel::ForbiddenAttributesProtection
when trying to load Paranoia gem. The gem was suppose to be ready for Rails 4.0.x. That error was not suppose to be happening.The error trace:
My Gemfile:
Rails is already in 4.0.0. Ruby, 2.1.8.
Thanks! <3
The text was updated successfully, but these errors were encountered: