write_inheritable_attribute replacement
Reported by schwabsauce | July 14th, 2008 @ 06:33 PM
I forked the merb_xss_terminate plugin and made some adaptations for dm. The plugin uses write_inheritable_attribute, which isn't in my gems, although it is here: http://github.com/wycats/merb-co...
I am confused by this discrepancy. Am I missing something about git or github? Shouldn't that page show the same code as would be in my gems after sake merb:gems:refresh? Otherwise, if write_inheritable_attribute has been removed, is there a replacement for it?
my plugin is at http://github.com/schwabsauce/me...
I'd be happy to help track down more detail about what is going wrong and try to patch it but first I want to know what is up with the discrepancy between the hub and the gem.
Comments and changes to this ticket
-
schwabsauce July 14th, 2008 @ 06:38 PM
http://pastie.textmate.org/priva...
(the class.rb that I, and probably you, have in my gems)
-
Michael Klishin (antares) July 16th, 2008 @ 09:56 PM
- → Assigned user changed from “” to “Yehuda Katz (wycats)”
- → State changed from “new” to “open”
-
Yehuda Katz July 16th, 2008 @ 09:58 PM
there were some issues in the old inheritable_accessors that made write_inheritable_accessor necessary.
If the old way was:
write_inheritable_accessor(:foo, "bar")
the new way is:
self.foo = "bar"
-
Yehuda Katz (wycats) July 20th, 2008 @ 05:49 AM
- → State changed from “open” to “invalid”
Since this is not a merb-core issue, I am closing this as invalid. If it's still an issue, please reopen with more details.
Please Login or create a free account to add a new comment.
You can update this ticket by sending an email to from your email client. (help)
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile »
