The choice to set a Select box to default "None" when clicking Edit Field Collection at Manage Content types is missing. I think this happened after we set the actual Select Field to required. Afterwards, setting the Select Field back to optional revealed the "- None -" option in the actual fields config, but looking at field collections edit page still only shows the manually set "Allowed values list".

Only local images are allowed.
Only local images are allowed.

http://dl.dropbox.com/u/2188345/fc.png
http://dl.dropbox.com/u/2188345/fc2.png

Images not displaying properly for some reason even if allowed tags lists img tag meh.

CommentFileSizeAuthor
#3 select_default.png4.54 KBmropanen
#3 select_in_form.png2.29 KBmropanen
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

rnyberg’s picture

Since 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.

jenesis’s picture

Imho quite critical.
Temp workaround is to use taxonomy link field instead of select field.

mropanen’s picture

FileSize
2.29 KB
4.54 KB

Quite 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!)

tim.plunkett’s picture

Priority: Major » Normal
Status: Active » Postponed (maintainer needs more info)

Is your individual field required?
Is the field collection field required?

jmuzz’s picture

Issue summary: View changes
Status: Postponed (maintainer needs more info) » Closed (cannot reproduce)

It 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.