Robert Pankowecki wrote in post #972837: >> ...and this is why attr_protected sucks so bad. There oughta be an easy >> way of saying "reject these attributes, but only for certain actions". >> Unfortunately, Rails doesn't, and perhaps can't, work that way, so we're >> stuck with clumsy hash merges in the controller. >> >> I wonder if a better way is possible. Hmm. > > http://api.rubyonrails.org/classes/ActiveModel/MassAssignmentSecurity/ClassMethods.html#method-i-attr_accessible > > http://railscasts.com/episodes/237-dynamic-attr-accessible > > It's much more flexible and simple system in rails 3.
They fixed this in Rails 3? Squee! That's really cool. (I'm just starting to work with Rails 3, and I don't use attr_protected that often, so I hadn't found that out yet.) > > Robert pankowecki Best, -- Marnen Laibow-Koser http://www.marnen.org [email protected] -- Posted via http://www.ruby-forum.com/. -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
