I was going to write a nasty blog post in my frustration since I burned about about two hours trying to figure out wondering why error_messages_for was completely ignoring everything option I threw at it, but ActiveScaffold has saved me about two or three hours on my backend, so I guess it all evens out. Also, it's late and I can't summon anything more than a muted squeal of irritation.
Is it really necessary to completely gut error_messages_for? The monkey-patch deal AS has going on in there means it's lacking some of the features that have been added over various Rails releases. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "ActiveScaffold : Ruby on Rails plugin" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/activescaffold?hl=en -~----------~----~----~----~------~----~------~--~---
