Makes attr_accessible whiny. A monkey patch for Rails 3.1 to raise an exception instead of a warning in the logs when protected fields are mass assigned

whiny_attr_accessible.rb

# Rails edge includes pluggable sanitizers for mass assignment. Really cool is the
# StrictSanitizer which raises an exception instead of a log message, which makes 
# problems easier to spot in development.
# For the time being, there seems to be no way to achieve this in Rails 3.1 via
# configuration. Monkey patching to the rescue!
# Copy the gist into config/initializers and configure the environments in which the
# exception gets raised.

if ['development', 'test'].include?(Rails.env)
  ActiveModel::MassAssignmentSecurity::BlackList.class_eval do
    protected
    def debug_protected_attribute_removal(attributes, sanitized_attributes)
      removed_keys = attributes.keys - sanitized_attributes.keys
      raise ActiveModel::MassAssignmentSecurity::Error, "Can't mass-assign protected attributes: #{removed_keys.join(', ')}" if removed_keys.any?
      super(attributes, sanitized_attributes)
    end
  end

  ActiveModel::MassAssignmentSecurity::WhiteList.class_eval do
    protected
    def debug_protected_attribute_removal(attributes, sanitized_attributes)
      removed_keys = attributes.keys - sanitized_attributes.keys
      raise ActiveModel::MassAssignmentSecurity::Error, "Can't mass-assign protected attributes: #{removed_keys.join(', ')}" if removed_keys.any?
      super(attributes, sanitized_attributes)
    end
  end
end

class ActiveModel::MassAssignmentSecurity::Error < StandardError
end