By mistake I posted the message twice. The structure of the validation yml is now clear after studying the code.
The problem was caused by sfFormValidation plugin which did not support the alternative definition of the yml. I found an other problem of the plugin and have prepared a patch which fixes both. What I fixed is: 1:Support the alternative definition of the validation yml 2:If the module does not have a validation file for the action do not attempt to parse the file (which would cause a runtime error) 3:If the cache is off, the old implementation would regenerate the php configuration file for each call of function get_validation_tag_options. This was a huge overhead when the form contained a lot of fields. The new implementation might need a revision because it by-passes the cache mechanism completely. What it does is to compare the last modified time of the yml file with that of the generated php file. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "symfony developers" 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-devs?hl=en -~----------~----~----~----~------~----~------~--~---
