CODEWITHSUNDEEP
ruby-on-rails-3ruby-on-rails-4strong-parameters
user938363
user938363

Reputation: 10358

config.active_record.whitelist_attributes = false in Rails 4.2 App

Our rails 4.2 app consists of several rails engines with or without gem 'protected_attributes'. What we find out is that in app's application.rb, it has to be:

config.active_record.whitelist_attributes = false

Otherwise, any create/update can not be carried out because the params can not be assigned to instance variable. Our question is that, if there is no gem protected_attributes in rails app, do we still need config.active_record.whitelist_attributes = false in application.rb? Is this for Rails 3.x or app with gem protected_attributes?

Upvotes: 1

Views: 1415

Answers (2)

cianmce
cianmce

Reputation: 494

This comes from the protected_attributes gem.

When whitelist_attributes = true it causes attr_accessible(nil) to be added by default for all models meaning you ca not mass assign any attributes for any models unless it has its own attr_accessible or attr_protected

This can be seen in an older version of the README.md

As of version 1.1.2 this is now depreciated and does nothing other than log a depreciation warning

So if you are on a Rails 4+ application and do not have the protected_attributes gem then you can safely remove it

Upvotes: 1

Mohammad AbuShady
Mohammad AbuShady

Reputation: 42889

I've looked through several rails 4 apps I have, none of them contained that config, and when I googled the config name, the protected_attributes gem came in the results, so I think you could assume that it's only related to the protected_attributes gem and that you don't need it

Upvotes: 3

Related Questions