[symfony-devs] RE: [symfony-users] Validation: grouped fields problem

[Gert Vrebos]

In addition, the new validation syntax seems not to support the group parameter… it tries to load ‘group’ as if it was a validator.   Gert.   From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Gert Vrebos Sent: donderdag 9 november 2006 17:43 To: [EMAIL PROTECTED] Subject: [symfony-users] Validation: grouped fields problem   Hi folks,   At validation, if one of the fields in a set of grouped fields is not empty, the other fields are tested for emptiness, independent of their required property.   This makes it impossible to run a validator on an empty field (which I need because the field is optional depending on some criteria), but it also differs from the documented behaviour:   From the sf book, the example ‘Execute validator on an empty field’: If Password1=foo and password2=null, the required_message (in this case the default, not very descriptive ‘Required’) is shown instead of the passwordValidator error message.   If others consider this as a bug, I will create a ticket with patch.   In addition to the group feature, it would be nice to have an option to execute a validator on an empty field as well.  The current dirty workaround I would use is grouping the possibly empty field with a non-empty field, but this is also made impossible by the problem above.  The only solution left now is to validate in the action but I want to avoid that.   Gert. --~--~---------~--~----~------------~-------~--~----~  You received this message because you are subscribed to the Google Groups "symfony developers" group. To post to this group, send email to symfony-devs@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/symfony-devs?hl=en -~----------~----~----~----~------~----~------~--~---