Hi,

using collection field in views, users should have, IMHO, more flexible approach for settings of every single field added in a collection. Reproducing settings of field collection in views isn't sufficient.

If we have an image field with image widget linking to the content, for example, its path is leading to field collection instead of a node where the collection is embedded.

Or am I missing something?

Anyway, we need to set different image styles for different views, and it seems that this is presently not possible.

Thanks.

Comments

heretic381’s picture

Ok, I found a workaround for this. It is possible to use fields from field collection separately in custom views. Just add a relationship to content:your_field_collection. This enable all fields as separate items in views fields tab. You can then configure them as usual, rewrite the output etc...

heretic381’s picture

Everything worked fine. But then, working on a multilingual site, I discover that field collection doesn't work with entity translation. :{

What's the alternative?

jmuzz’s picture

Issue summary: View changes
Status: Active » Fixed

You can try the patch in #1344672: Field Collection: Field translation (entity_translation) support.. Another alternative may be entity reference and inline entity form but I am not sure what their entity translation support is like. You can see #1545896: Add Entity Translation integration. You may also want to look at multifield.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.