I have just released a *new* version of *sfPokaYokePlugin* client side validation plugin. It previously looked for validation rules that matched the current module/action as the form was displayed. This required you to modify your actions and create form that submitted to the same action or duplicate you action_name.yml validation rules for the create and update actions created by propel-generate-crud. sfPokeYoke has now been greatly updated to identify the action the form submits to and look for validation rules that match that action. You can now also use named routes i.e. '@sfGuard_signin'.
I have also added a number of configuration options that can be added to your app.yml file. This allows you to define the JavaScript events that will trigger the validation and also how the errors will be displayed. I have updated the plugin documentation on the wiki with all the configuration options. http://trac.symfony-project.com/trac/wiki/sfPokaYokePlugin sfPokaYoke is now more closely matched the server side validation so much so that it should be transparent to the user. It uses the same template hooks and also integrates the error_prefix and error_suffix values form the settings.yml file. I would really appreciate your feedback! Please let me know if you have problems with the plugin or if you have improvement suggestions. Thanks Ali --~--~---------~--~----~------------~-------~--~----~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/symfony-users?hl=en -~----------~----~----~----~------~----~------~--~---
