They reported several cases, some I have not recreated yet. The one I have recreated is as follows:
Edit a record with a subform for a one to many association. Create a new record in the subform that fails validation. Submit the form and get errors on the subform and the main form. Delete the row in the subform that was in error, note the error message is still there. Michael On Mar 9, 2011, at 8:26 AM, Sergio Cambra .:: entreCables S.L. ::. wrote: > On Miércoles, 9 de Marzo de 2011 16:22:24 Michael Latta escribió: >> My users are complaining about error messages left in the page after a >> clean update. Has anyone tackled cleaning up error messages? Is there a >> reason not to remove error messages prior to a new submit? Because child >> record errors are disconnected from the records they linger, the same >> appears to be the case for top level errors related to child records. >> >> Michael > > I don't know what error messages left are you talking about > > -- > Sergio Cambra .:: entreCables S.L. ::. > Mariana Pineda 23, 50.018 Zaragoza > T) 902 021 404 F) 976 52 98 07 E) [email protected] > > -- > 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. > -- 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.
