Closed (fixed)
Project:
Clientside Validation
Version:
7.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Support request
Assigned:
Reporter:
Created:
1 May 2012 at 20:57 UTC
Updated:
28 May 2012 at 09:20 UTC
I have enabled the Clientside Validation FAPI module but it does not seem to be firing.
I have not changed any of the default settings. Based on the documentation, I am under the impression that the module should interpret my currently implemented validation rules and convert them to client-side rules but this does not seem to be occurring. The form validates correctly on submit.
I am happy to provide more information but I am not sure what is pertinent based on the fact that the documentation says it should just work.
Comments
Comment #1
markdorisonThe validation seems to be working as expected for fields on node edit forms.
Comment #2
attiks commentedSo this is fixed?
Comment #3
attiks commentedif not re-open
Comment #4
markdorisonThis is not fixed. It works correctly for node edit forms, but not on a custom FAPI form that I created.
Comment #5
attiks commentedCan you post the form code?
Comment #6
markdorison@attiks: Absolutely.
Comment #7
attiks commentedI tried your form, but what isn't working for you?
If you use emailfield as type, there's no need to add a rule for email, the following works as well:
The latest dev version now also supports custom rules on email, phone and link field
Comment #8
markdorisonThe validation gets fired on POST instead of on the client end. When I compare this to a node form, I can see that on the node form the client-side validation occurs on submit with no POST, whereas the form I posted in comment #6 posts back in typical Drupal core fashion before it presents the validation results.
Comment #9
attiks commentedDo you get any javascript errors? Did you change the settings?
Comment #10
jelle_sClientside validation was not fired because we didn't have support for 'required' on the phone and e-mail fields.
fixed in the latest dev version