Closed (fixed)
Project:
Clientside Validation
Version:
7.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Reporter:
Created:
5 Apr 2012 at 05:02 UTC
Updated:
11 Sep 2012 at 10:58 UTC
Jump to comment: Most recent file
Comments
Comment #1
attiks commented1/ you mean this isn't working
2/ go to admin/config/validation/clientside_validation
Comment #2
modulo49 commentedI'm using 6.x-1.30+2-dev. I have the problem, too, but it's the opposite of the pictures. Clientside validation is requiring fields that are not required. I am using Webform 6.x-3.17+7-dev and Webform Validation 6.x-1.5.
Comment #3
modulo49 commentedUpdate: This only seems to be a problem in 6.x-1.30+2-dev if you have it validate on submit.
Comment #4
attiks commented@modulo49 so in D7 all is fine?
Regarding the D6 problem, "... if you have it validate on submit" can you clarify a bit more, when does it work, doesn't it work?
Comment #5
modulo49 commentedI don't know about d7, I don't use it. But, I'd guess that the code is similar and causing the same problem. If in my Clientside validation settings I have selected to "Validate fields on submit" it treats all fields as required. If I choose not to "Validate fields on submit" then it works properly.
Comment #6
modulo49 commentedEven with "Validate fields on submit" turned off, it a user types something into a non-required field and then removes the text, it treats the field as required. But does not have this behavior if the field is simply passed through using tab key.
Comment #7
attiks commented@modulo49, you're right, i was able to reproduce the error on the optional fields, will have a look.
Comment #8
attiks commentedFixed in 6.x-1.x (dev version), can you please test it and let me know if everything still works
Comment #9
modulo49 commentedhey, that works great. Each validation is working just fine (key-up, blur and submit). It's a great module, by the way. Hope that will eventually lead to whatever smilne23 was having issues with.
Comment #10
attiks commentedmoving back to D7
Comment #11
barwonhack commentedHi everybody.
So hey, love the module and appreciate the around this little defect.
Hey Attiks,
re comment 1 part A, The mandatory checkbox is located on the webform editing form (see attached image).
re comment 1 part B, I understand the idea behind excluding specific forms, but having review the jquery.validate documentation, it occurred to me that that the module could possibly offer the ability to exclude specific fields based upon their DOM ID. As I understand it, the module currently only supports excluding specific forms.
Comment #12
attiks commented@smilne23
A/ so the validation isn't working for you: is it always or never validated?
B/ can you open a new feature request for this?
Comment #13
barwonhack commentedA) Validation is always validating non-mandatory fields - they are treated as mandatory.
B) Sure - more than happy to do this. I guess I see it as an alternative, more direct, approach to controlling what does (&doesn't) get validated.
Comment #14
attiks commentedA/ I'm not able to reproduce it, did you try the latest dev version?
Comment #15
barwonhack commentedI'm on 1.30. Will try 1.31 or dev shortly.
Comment #16
barwonhack commented1.31 fixed the defect.
Thanks Attiks. LOVE your work!
Comment #18
boazr commentedhas this been broken again in 1.32 ???? (d6)