I was actually expecting an array that would have the 'text' key when I discovered this. I have no issues with using the sfValidatorString class on objects derived from sfForm, just with objects that are based on sfFormFilterDoctrine. That's where I'm confused. I also noticed that classes generated by the symfony command-line in the filter directory use sfValidatorPass for table fields that are strings; while those in the form directory were actually using sfValidatorString.
I'm not sure if it matters but I'm actually using something along the lines of $filterForm['afield']->render() to render the text boxes. Are there any differences in how sfForm-derived objects handle validation that's different from sfFormFilterDoctrine-derived objects? Thanks On Thu, Sep 30, 2010 at 8:15 AM, Gustavo Adrian <comfortablynum...@gmail.com > wrote: > I think it might be because the widget used for the text fields on a filter > form contains an array with a "text" element, which contains the value > entered by the user. The validator is not prepared to receive an array, but > a plain value. That's why you receive the "array" string instead of the > value itself. > > You could override the sfValidatorString so you can return the value > instead of the array itself. > > > > Cheers. > > On Thu, Sep 30, 2010 at 11:07 AM, Keith Mendoza <panthe...@gmail.com>wrote: > >> It literally returns the string Array instead of what was entered by the >> user in the text box. >> >> Sent from my android >> >> On Sep 29, 2010 11:19 PM, "Tom Ptacnik" <to...@tomor.cz> wrote: >> >> What is in this array? >> >> On 28 zář, 18:49, pantherse <panthe...@gmail.com> wrote: >> > What I want to do is replace the validator for a field to >> > sfValidatorString instead of the sfValidatorPass in the base form >> > filter class. However, when I do that the field's value becomes the >> > text "Array" instead of the actual cleaned array that I'm getting on >> > form classes. >> >> -- >> 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<symfony-users%2bunsubscr...@googlegroups.com> >> For more options, visit this group at >> http://groups.google.com/group/symfony-users?hl=en >> >> -- >> 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<symfony-users%2bunsubscr...@googlegroups.com> >> For more options, visit this group at >> http://groups.google.com/group/symfony-users?hl=en >> > > -- > 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<symfony-users%2bunsubscr...@googlegroups.com> > For more options, visit this group at > http://groups.google.com/group/symfony-users?hl=en > -- 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
