This project is archived and is in readonly mode.
Don't try to log protected attribute removal if there's no logger defined
Reported by Jeffrey Hardy | September 2nd, 2009 @ 05:14 PM
When mass-assigning protected attributes, AR will log a warning. This causes an error if there's no logger defined. In other places where we use AR::Base.logger, we check to make sure it exists. This patch makes #log_protected_attribute_removal follow suit.
Comments and changes to this ticket
-
Repository September 2nd, 2009 @ 05:21 PM
- State changed from “new” to “resolved”
(from [e870e24887e829547abdb6592d614c52f5412132]) Don't try to log protected attribute removal if there's no logger defined [#3135 state:resolved]
Signed-off-by: Joshua Peek josh@joshpeek.com
http://github.com/rails/rails/commit/e870e24887e829547abdb6592d614c...
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile »
<h2 style="font-size: 14px">Tickets have moved to Github</h2>
The new ticket tracker is available at <a href="https://github.com/rails/rails/issues">https://github.com/rails/rails/issues</a>
People watching this ticket
Jeffrey Hardy
Attachments
Tags
Referenced by
-
3135
Don't try to log protected attribute removal if there's no logger defined
(from [e870e24887e829547abdb6592d614c52f5412132])
Don't t...