The before_create_save and before_update_save aren't hacks, they're part of the design of the system.
-Mike [email protected] wrote: > Thank you for your reply Kenny. > > I thought of a few hacks too, but I was hoping for a solution in AS. > I guess I will have to wait for the next version or move to another > product. > > Again, thanks for your help. > > On Feb 13, 9:54 pm, Kenny Ortmann <[email protected]> wrote: > >> The issue isn't about mis-configuring. I could help you with ways around >> this but all of them are "hacks" >> >> The issue is that active scaffold creates the children with out knowing what >> their parent is. When you create it's only creating the parent from the >> parameters that you ask for in the form. >> >> One way you could solve this is that every time you create a child have java >> script add to a hidden tag that contains the id's of all the children and >> then when you create the object the associate the child records with the >> parent. >> >> Now you also have an issue though, because if someone decides to cancel the >> course those child records are still hanging around in the data base. >> >> > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
