Needs work
Project:
Field collection
Version:
7.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
2 Feb 2012 at 15:57 UTC
Updated:
11 Sep 2014 at 13:24 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
drikc commentedThe attached patch skip the validation process for embedded fields when the button "Add another item" is used.
Comment #2
tim.plunkettWhat's wrong with validating there? Not sure that this is a true "bug".
Comment #3
drikc commentedMe neither, but I had a user reporting it as bug; he wanted to add a field-collection item without having to complete the requirement of existing items. Perhaps having the validation at submit is sufficient and having it on "Add another item" isn't necessary.
Comment #4
iLLin commentedYou shouldn't be able to add another collection if the previous one isn't filled out correctly. I think this works as designed. The only slight issue I have found that provides a weird user experience around this is if I click submit and there is an error in the form, errors are displayed at the top. If immediately hit "add another item", then there is another set of errors around the field collection within the form. So essentially it is displaying two error message sets on the form. Bug? No... Weird UX? Yes. I am going to solve that issue with JS as I am using AJAX forms anyway.
As far as this issue being a "bug", I don't agree.
Comment #4.0
iLLin commentedRemoved a dot
Comment #5
jmuzz commentedBoth behaviors have merit. I see no reason to change the default, but validating the form at submission time would be a nice option to have if somebody wants to add an option for it.