I am doing that and it is still giving me the error.

On Mar 4, 12:00 pm, Richtermeister <nex...@gmail.com> wrote:
> Hey Darren,
>
> when you use a form to update a record, make sure you pass the record
> into the form at creation time,
> for example:
>
> $customer = CustomerPeer::retrieveByPk(123123);
> $this -> form = new CustomerForm($customer);
>
> this way the form knows that even if the email is already in the
> system, if it's owned by this customer, it's not a duplicate.
> Hope this helps.
>
> Daniel
>
> On Mar 4, 10:19 am, Darren884 <darren...@gmail.com> wrote:
>
> > Heres the deal, I created an admin generated form in my backend, and I
> > am able to edit my customers easily. However when I try to make a form
> > on the main site for them to update their date I simply cannot do it.
> > The form system makes it so when I try to use the previous form class
> > its impossible to save their data because I have a unique email
> > validator and whenever they try to save it they can't. What should I
> > do? Should I just do validation the old fashioned way? Why is Symfony
> > like this? Why can't I make it as easy as just letting someone update
> > their information? Please someone help I am stuck on this.

-- 
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 symfony-users@googlegroups.com
To unsubscribe from this group, send email to
symfony-users+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/symfony-users?hl=en

Reply via email to