Sorry. Yes, it's just plain old 'initialize' that shouldn't be overloaded, which you're not doing ... Ignore me :-)
Top-posted from Android On Jun 11, 2011 2:37 PM, "ddoherty03" <ddohert...@gmail.com> wrote: Pavling, Thanks for the comment. If I understand it, though, I don't believe that's what's going on here. I am not redefining the after_initialize method, just using it to add a callback into the object creation stream. This is pretty standard. But when the validation test is run, it seems the attribute methods suddenly go missing. I spent several hours trying to trace this in the debugger, but I found myself in a deeply-nested call stack of AR code and could not tell what was going on. I decided to create a whole new minimal Rails app to see if I could reproduce it. That's what this silly greeting app is all about. I've posted all the code in the entire app: just a migration, a simple model class, a fixture, and a unit test. That's why I think it might be a Rails bug, but I wanted to run it by the gurus here. Hope this this helps. Regards, Dan -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk... To view this discussion on the web visit https://groups.google.com/d/msg/rubyonrails-talk/-/cD7QR0b2juYJ. To post to this group, send email to rubyonrails-talk@googlegroups.com. To unsubscribe from this gr... -- 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 rubyonrails-talk@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-talk+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
