Comments on: Release: Validation Plugin 1.6

By: Jörn

Jörn — Thu, 04 Mar 2010 18:18:57 +0000

@Jatinder: Just include one of the messages_xx.js files on your page. Either just one, or write a routine to select the right file based on the user’s locale.

By: Jatinder

Jatinder — Thu, 04 Mar 2010 18:13:40 +0000

I have been using jquery-validation plug-in for small validations. In my new project I am planning to use localization feature that is available in the plug-in. But I have not found any documentation on how to use this functionality that comes with the plug-in. Any sample code would be really helpful. Tip/Suggestion/Hint would work as well

By: Steven Black

Steven Black — Tue, 02 Mar 2010 02:36:52 +0000

Yep, I can confirm that the Validate plugin doesn’t work with 1.4.2 because of this conflict with $.fn.delegate()

By: Charles

Charles — Sat, 27 Feb 2010 04:54:01 +0000

Now that 1.4.2 has it’s own delegate() function, this plugin is no longer compatible. It overwrites the jquery core version and the syntax (parameter order) is also different. You mighr consider tweaking the official version to be compatible with 1.4.2

By: Aaron Kreider

Aaron Kreider — Thu, 28 Jan 2010 21:25:46 +0000

Firebug 1.5.0 (and Firefox 3.5.7) give a warning on the demo and also for my own forms. This affected both plugin versions 1.5.5 and 1.6

http://jquery.bassistance.de/validate/demo/

Warning:
The ‘charCode’ property of a keyup event should not be used. The value is meaningless.

It’s annoying because it happens once per keypress and fills up the console.

By: James

James — Sat, 26 Dec 2009 01:54:53 +0000

Great Plug-in Jörn. We finally went live today and we are using your plug-in in all our forms at http://www.recarded.com if you want to add us to the Documentation Wiki / Sites That Use It section.

~james

By: Pluggd

Pluggd — Thu, 10 Dec 2009 16:31:17 +0000

Das Validator-Plugin kommt mir grad sehr gelegen, vielen Dank dafür.

By: Jess

Jess — Thu, 10 Dec 2009 00:27:34 +0000

I haven’t seen it documented anywhere, but are type=’password’ fields considered required, even when not set as such?

This is causing problems in a profile update page, where a user need only enter a password if they wish to change it. Setting the field to newpassword: { required: false} fixes it, but I was surprised to not find it documented.

I think this is also causing an issue with a confirm password field (where required:”#newpassword”), but I’m still playing with it.

By: Zoe

Zoe — Thu, 03 Dec 2009 23:56:29 +0000

Yay! This update has fixed an issue I was seeing validating email addresses with Validate 1.5 and JQuery 1.3.2 (but worked fine with 1.2.3). You’re a star Jörn.

By: Jörn

Jörn — Thu, 03 Dec 2009 07:18:36 +0000

Check the full list of localizations.