Please, how to make it work?

Its in development, so I'm not sure if its supposed to work yet. Here's how I configured a field collection:

1. went to a node type (e.g. admin/structure/types/manage/page/fields) and added a field of type "field-collection"
2. went to field collections configuration (admin/structure/field-collections) and added some fields to the collection. The user interface worked nice for me.
3. Create a node of that type (node/add/page). The field collection doesn't show up on the node edit page (yet) as its under development and the UI is elsewhere currently (see comments below).
4. Go to view the node (content/test or node/NNNN) and you will see "add" links to add the field groups.

Add a field-collection field somewhere (e.g. to a node), then go to admin->structure->field-collection to add fields to the collection.

As of now there is only UI to add field-collections to an already existing entity. E.g. add a node having the field-collection field, then when viewing it you'll get links to add/edit the field collection.

thanks. I updated my previous post.

In my opinion, the new items should be added at the create node form instead of at the view node page.

Why did you implement it that way?

A good idea could be make it configurable.

subscribing – interested in the answer to #5

I've been waiting for this functionality since... I dunno. A long time.

And as an answer to myself and dani.latorre: #947288: Use case?

It's not very clear for me how to add a multigroup field to a node type from code?

This looks very promising. How's work with the widget going ?

+1!

#5 makes a lot of sense, it would be nice to add values in the node creation.

Hello

I'm using field collection and looks great! Thank you for the module.

I've done also all I need with it. I can't show my field collection in a node tpl. How can I print the field to the output in a tpl.

I would like to add the output to the $variables in a preprocess function.

I'm trying to use field_collection_field_formatter_view but i can't get it. Could you give me a hand?

Thank you.

Subscribing

Subscribing

If you're trying to show and theme the field collection you have a couple of options.

You can render it with the $content variable, like this:

print render($content['your_field_collection']);

and theme through the output through the field_collection_item.tpl.php. For more fine grained theming, check this thread: http://drupal.org/node/1100736

I have also used entity load directly in the node.tpl.php. With a little alteration you can probably use this in a preprocess function.
http://drupal.org/node/1107214

subscribe

All the steps in #1 worked well for me, this looks very promissing. I like it!
I look forward to further development in this module.

subscribing

Amazing module! subscribing too. Hope the next release ...the "show" widget will be on ;-)

subscribing ...

>In my opinion, the new items should be added at the create node form instead of at the view node page.

Having the form on the node-form is for sure nice in many use-cases, see #977890: Display collection fields within entity form (subform/embedded) for WIP.

>Why did you implement it that way?
Having separate forms and just add/edit/delete links is another one, what in my case lead to a better to UX than otherwise and was easier to implement. My main use-case when I wrote this was having a profile (built with profile2) that is separated in multiple profile categories which can be edited out of the profile overview in the overlay - somehow similar to the profile on facebook or other social networking sites.

I really think this needs to be integrated into the standard node edit form.

Requiring a user to edit a node in two separate places is bad UX imo.

EDIT: Just saw the latest dev version .. it can be embedded now, works really well.

subscribing