Hi,
My issue is the following: I have a content type with a field that is a field collection. In that field collection i have a field which is again a field collection. When i initially create my node, everything's fine: I have a node with a field collection in a field collection.
Then i edit my node, and there are a couple of new empty child field collections (child= the field collection in the field collection). The strange thing is, when i don't delete those blank child collections, there are new parent collections in the database, and no child collections.... ?! Are you still with me ? ;)
I have the feeling that it's remotely linked to issue: http://drupal.org/node/1239946, but because it's not entirely the same, i'm posting a new one.
Another thing which i find kinda strange, is that my child collection is linked to my node and has the node id as entity_id, shouldn't that be the entity_id of the parent collection ?
It could be that field collections don't support nesting ? Or that i'm doing it wrong ? If so, just tell me ;)
ANd fyi, i removed all default values and required fields in my collections..
Thanx.
btw, i have a dev version from http://drupal.org/node/1239946, maybe upgrading helps, but i looked through the commits, and there are no newer commits which are related to an issue like this...?
Comments
Comment #1
30equals commentedUpdate: i updated the module + applied the patch from http://drupal.org/node/1239946#comment-5838700.
With apply the correct settings, i got rid of blank items, which then don't cause multiple parent field-collection items in my database.
So for now all is good, nevertheless i don't think this solves the issue in itself..?
Comment #2
jmuzz commentedSo the blank items and the extra database entries are no longer present. What else remains?
Nested field collections are supported.
Comment #3
jmuzz commented