rails3 branch: protected attributes turned on about audited HOT 5 CLOSED

        options = {:protect => accessible_attributes.nil?}.merge(options)

If I'm looking at this right, accessible_attributes is never nil, but might be empty. Without acts_as_audited loaded:

ruby-1.9.2-p0 > Email.accessible_attributes
=> #<ActiveModel::MassAssignmentSecurity::WhiteList: {}> 
ruby-1.9.2-p0 > Email.accessible_attributes.nil?
=> false 
ruby-1.9.2-p0 > Email.accessible_attributes.empty?
=> true 
ruby-1.9.2-p0 > Email.accessible_attributes.count
=> 0 

from audited.

Have you got a fix for this yet? This happens to me as well: Rails 3.0.3
With acts_as_audited loaded, I get the audit_comment in the whitelist (which means everything else is blacklisted, I guess).

If it is not loaded, the white list is an empty hash and I can save my models fine.

from audited.

Just swapped

acts_as_audited :protect => false
for
acts_as_audited :protect => true

and the mass-assign error is gone. The whitelist hash stays empty, even with a_a_a loaded.

from audited.

This was an issue I fixed in the pull request in issue 36 - I hadn't specified any accessable or protected attributes but got this error. I discovered that the list was always defined, but empty, so the code needs to check empty? instead of nil?

from audited.

Closing this one since it has been resolved in #36 and is in the current RC.

from audited.