Bastian, you're exactly right. This is a known issue with embedded forms in symfony 1.4. But changing it at this point would break backwards compatibility in sf1.4, which is something the core team is not willing to do in a point release.
Check out this ticket about this exact issue: http://trac.symfony-project.org/ticket/5867 And specifically this ticket comment, which should fix the issue, but you must apply the fix manually: http://trac.symfony-project.org/ticket/5867#comment:21 John Kary On Mar 15, 10:47 pm, bkuberek <[email protected]> wrote: > symfony 1.4.10-DEV > sfFormObject.class.php : line ~ 229 > > I have pasted an excerpt here > > http://pastebin.com/dD6NGAd0 > > My questions is, in short, why not to call > > $form->save($con); > > Instead of > > $form->saveEmbeddedForms($con); > $form->getObject()->save($con); > > The later skips all the $form->save() and $form->doSave() methods > which could have important code. Calling $form->save() will eventually > call $form->saveEmbeddedForms() and $form->getObject()->save(); > > Is there a reason why this is done this way? > > Thanks -- If you want to report a vulnerability issue on symfony, please send it to security at symfony-project.com 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
