Closed (cannot reproduce)
Project:
Field collection
Version:
7.x-1.x-dev
Component:
User interface
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
12 Oct 2011 at 12:46 UTC
Updated:
8 Jan 2015 at 14:47 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
rnyberg commentedSince there has been no replies, I worked around the bug by implementing a node_presave hook to delete field collections that are "Empty" (created a new select option for that). Since with this bug, every time you'd save a node, you'd get an extra empty field collection appear on the bottom due the "None" choice not being selected for the last "Add another item" row.
Comment #2
jenesis commentedImho quite critical.
Temp workaround is to use taxonomy link field instead of select field.
Comment #3
mropanen commentedQuite critical indeed.
Attached are: picture of a newly-created select list in the field collection settings (select_default.png) where you can see that the default value can be set to "- None -". However, in the actual node form (select_in_form.png) no such option appears.
This means that the field collection is never truly empty, and will be saved on submit unless the user manually removes it (thank you for that button!)
Comment #4
tim.plunkettIs your individual field required?
Is the field collection field required?
Comment #5
jmuzz commentedIt is no longer possible to set defaults through the manage content section, it must be done through the manage fields page of the field collection itself now.
Please reopen if I'm wrong but I think this is no longer an issue.