Hi, in fact you don't need a validator anymore :P or maybe just for the type, but not for the choices.
and then you can add the object in updateObject(), and it will be created in save() On Apr 1, 5:33 am, J_Wesker <j_chave...@hotmail.com> wrote: > Hi symfony community! > > I have searched on several posts related to this widget for several > days, but until now I haven't found a lead about how to accomplish > what I need in a form. > > The situation is like this: > > The form is using several autocomplete fields, and everything is > working great! But it can always be better, right? Cool > I want to alter the validator used for the widget so that, if no match > is found, it can create the referenced object by the value typed on > the field, and then create the relationship with the widget, allowing > to save the form using the new autocomplete value even if it didn't > existed before on the DB. > > I am not sure if I should extend the validator (until now I suppose > it's sfValidatorChoice), or if other technique should be better. > > I have seen this behavior in some web apps, but I have no solid idea > how to achieve this. (like for example google's kind of autocomplete > search). > > If anyone can point me in the right direction, I'll be grateful! > > Best regards -- 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 To unsubscribe, reply using "remove me" as the subject.
