clientside_validation 7.x-1.20

List of commits for this release:

• Issue #1241366: disable on all admin pages by igorik: Added disable on all admin pages.
• Added support for number HTML5 element + setting to replace HTML5 validation with clientside validation
• moved html5 support to seperate submodule. Added possibility for other modules to add custom javascript rules
• added html5 url support, see also #1174630: Add new HTML5 FAPI element: url
• added validate options + added support for html5 email field, see also #1174620: Add new HTML5 FAPI element: email
• added support for HTML5 range element. see also #1174646: Add new HTML5 FAPI element: range
• support html5 pattern element, see also #1174766: Support the #pattern FAPI property for native HTML5 pattern attribute
• support html5 telephone and search, see #1174634: Add new HTML5 FAPI element: telephone and #1174628: Add new HTML5 FAPI element: search
• support #maxlength for html5 elements
• Added HTML5 color support
• new version of jquery.validate.js and jquery.validate.min.js
• cleaner way to disable default rules, https://github.com/jzaefferer/jquery-validation/issues/165#issuecomment-...
• Issue #1270566: clientside_validation_webform does not work because the by yang.wilby, attiks: Fixed clientside_validation_webform() does not work.
• Issue #1281494: Extending Client side validation to build custom form validations. by sarav.din33: Extending Client side validation to build custom form validations.
• Added api documentation files
• Issue #1270996: Control placement of error container by mjpa: Added Control placement of error container.
• allow custom javascript function for error placement
• override default behaviour for validating hidden fields, (https://github.com/hdragomir/jquery-validation/commit/eef5109f89f6eaae4e...
• added theme function for clientside error messages
• fixed bug with webform validation of numbers
• fixed fapi validation numeric bug
• Issue #1270566: clientside_validation_webform does not work because the by yang.wilby: Fixed clientside_validation_webform() does not work because the .
• Issue #1289168: Numeric Webform Validation does not work without defining a range by beefheartfan: Fixed Numeric Webform Validation does not work without defining a range.
• Issue #1291026: Cant arrange fields when "Clientside Validation Form submodule" is enabled by mibfire, attiks: Fixed Cant arrange fields when Clientside Validation Form submodule is enabled.
• Issue #1298362: Cannot "Save Draft" by primus: Cannot "Save Draft".
• new implementation of the theme function, see Issue #1304512: How to customize an error message when the user doesn't fill out a mandatory field by yang.wilby: Added How to customize an error message when the user doesn't fill out a mandatory field.
• Issue #1308304: In CCK User reference, Node reference field our validation not working due to Jquery update module. by sarav.din33: Fixed In CCK User reference, Node reference field our validation not working due to Jquery update module.
• Issue #1305512: Notice: Undefined index: #year_start by opteronmx: Fixed Notice: Undefined index: #year_start().
• support date min and date max besides date range
• support date fields in fieldsets etc., see Issue #1305512: Notice: Undefined index: #year_start by opteronmx: Notice: Undefined index: #year_start().
• Issue #1251394: wysiwyg problem with client side validation by igorik: Fixed wysiwyg problem with client side validation.
• Issue #1316678: Field validation not working by mropanen: Fixed Field validation not working.