17488 Posts in 4473 Topics by 1978 members
|Go to End|
10 October 2007 at 12:53am
Doing on Requirements::clear(..) doesn't help, as the js will always be included when using 'new requiredfield'.
10 October 2007 at 5:53am
the trick is to clear requirements as close to rendering as possible:
in your case of form-validation, this would be YourCustomFormClass->forTemplate()
but you're right, there should be a switch to disable client-side validation...
28 April 2008 at 12:41pm
dio5, did you sort this out and get Requirements::clear() to work correctly?
15 May 2008 at 3:39pm Last edited: 15 May 2008 3:39pm
Perhaps we should add a couple of useXXValidation() methods on the form, to turn this on / off?
If we can make a patch for this on trunk, then Dio5 / Blackdog can apply it to their own branches before the next release.
22 May 2008 at 10:14am
Dio5, I never could get the clear() to work even if I targeted the individual files.
23 May 2008 at 7:27am
Sam, that sounds like a good idea.
23 May 2008 at 3:43pm
For example, I use jQuery, so it totally sucks to have prototype imported and used to validate forms when there is an excellent jQuery Validitor plugin that is very easy to template and would add very little overhead to my existing pages. If the hooks were available, devs could produce jQuery/Mootools/YUI ports to perform these common tasks.
If someone is already doing this, or there is a workable solution already, please let me know. Otherwise I'm interesting in helping produce such a framework if someone wants to point me in the right direction.
|Go to Top|