Needs work
Project:
Clientside Validation
Version:
7.x-1.x-dev
Component:
User interface
Priority:
Normal
Category:
Bug report
Assigned:
Issue tags:
Reporter:
Created:
29 Jun 2012 at 10:40 UTC
Updated:
10 Jul 2014 at 15:02 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
attiks commentedDid you try it?
Comment #2
akamaus commentedYes, I enabled clientside_validation_field_validation. It helped for regular fields, but didn't work for fields inside field collections. After your question I decided to double check it and enabled clientside_validation_form. Surprisingly for me, it worked!
I guess the documentation should reflect this.
Comment #3
attiks commentedComment #4
jelle_sFixed in latest dev by adding a dependency to clientside_validation_form
Comment #6
dimitrov.adrian commentedNot fixed in latest version.
Problem occurs when we have field collection with required fields but the collection is not required by itself.
Comment #7
attiks commented"Problem occurs when we have field collection with required fields but the collection is not required by itself" so what has to happen then, do we need to check the fields or not?
Comment #8
dimitrov.adrian commentedThere is two cases IMHO
1) and easy is just to skip them, because if we get the collection as single field it is not required itself.
2) which seems to be more complicated but more reliable is, to check if there is something filled in the collection, if there is something, then to validate the collection, in case it is "empty", skipping it.
Comment #9
jmuzz commentedI think "2)" is the only correct way to handle it. The fields should all be checked and validated if there is any data entered in any of them. If the field collection item is completely empty and not required then don't validate it.