Release: Validation Plugin 1.6

Update update: Files are now availble via Microsoft’s AJAX CDN.

An update for the jQuery validation plugin is available. There are five new localizations (now at 26 in total), including Arabic and Farsi (both right-to-left). Validation of selects is now more interactive, click events are properly handled to provide quicker feedback (also a bug related to selects in IE8 is fixed). The equalTo-method is now aware of changes to the target field, so a change to a password field will be reflected in a confirm-password field. And more…

Download this release.

The only not fully backwards-compatible change (if you spot anything else, please report it as a bug): The dateDE and numberDE methods were replaced with a localization/methods_de.js file, with localized versions of both the date and number methods. There are also localized methods for the NL and PT locales. The goal is to gather more localized versions of these, similar to the localized messages.

The full changelog:

As usual, support is available via:

  • Please post questions to the jQuery discussion list, putting “(validate)” into the subject of your post, making it easier to spot it and respond quickly. Keep your question short and succinct and provide code when possible; a testpage makes it much more likely that you get an useful answer in no time.
  • Please post bug reports and other contributions (enhancements, features, eg. new validation methods) to the bug tracker (requires registration).



No more comments.
  1. 1. December 2009 |09:05

    Boy, you’ve been keeping busy.

    Can’t wait to take it for a spin!

  2. 1. December 2009 |13:37

    Will this be updated on Microsoft’s CDN soon? Thanks for your hard work!

  3. 1. December 2009 |13:48

    @Elijah: I’ve pinged my contact at Microsoft about it. I’ll update the plugin page as soon as its up, and if it takes a while, post another update.

  4. Lec
    3. December 2009 |02:04

    This is great, does it support simplified Chinese? I seen in the change log only traditional (just minor variations). Thanks.

  5. 3. December 2009 |08:18
  6. Zoe
    4. December 2009 |00:56

    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.

  7. Jess
    10. December 2009 |01:27

    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.

  8. 10. December 2009 |17:31

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

  9. 26. December 2009 |02:54

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


  10. Aaron Kreider
    28. January 2010 |22:25

    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

    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.

  11. Charles
    27. February 2010 |05:54

    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

  12. 2. March 2010 |03:36

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

  13. Jatinder
    4. March 2010 |19:13

    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

  14. 4. March 2010 |19:18

    @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.