Kris, This is the issue I described to you the other day. It is a real issue I think.
- Jon On Mon, Feb 9, 2009 at 10:13 AM, Paolo Mainardi <[email protected]>wrote: > > > > On Feb 2, 8:37 pm, Kris Wallsmith <[email protected]> > wrote: > > Hi Michael, > > > > I believe the ->updateObject() method is called on embedded forms. You > > might also use a validator or post validator to handle this logic. > > > > -- > > But, howto handle M-M (admin generated) relationship saving without > call the doSave() on embedded forms ? This is a big issue, without a > solution. > > See here: > > http://groups.google.com/group/symfony-devs/browse_thread/thread/d4f5679d35ebfb41?hl=en > http://trac.symfony-project.org/ticket/5445 > http://trac.symfony-project.org/ticket/4850 > > Using the updateObject() it's impossible save correctly the > relationship because the main embedded form it's not save at this > stage, so we don't have the ids of we need. > > Yes we can save nested forms automatically with admin generator, but > we can't save linked M-M relationship, without patching the core. > > Someone have a solution for this ? > > Thank you very much :) > Paolo > > > > > -- Jonathan H. Wage Open Source Software Developer & Evangelist http://www.jwage.com http://www.doctrine-project.org http://www.symfony-project.org --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "symfony users" 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/symfony-users?hl=en -~----------~----~----~----~------~----~------~--~---
