I found a solution in the forums. http://forum.symfony-project.org/index.php/m/71159/?srch=The+item+has+not+been+saved+due+to+some+errors.#msg_71159
On Feb 26, 6:24 pm, zabbasi <[email protected]> wrote: > I am running sfGuard 3.1.3 and symfony 1.2.2 with propel currently and > see this Bug.Hasthe bugbeenfixed? If yes what version should I > upgrade to? > > I don't see any activity on the > tickethttp://trac.symfony-project.org/ticket/5469 > > Thanks > Zain > > On Jan 2, 3:32 am, fredlab <[email protected]> wrote: > > > I think the bug you are encountering is similar to this one > > :http://groups.google.com/group/symfony-users/browse_thread/thread/8f7... > > I spent a few hours on it on finally wrote 2 patches. I still need to > > submit them for approval. > > > Note that you should also upgrade to 1.2.2 dev as a few things were > > corrected with the generator. > > > Regards, > > > Frédéric --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
