Field Collection in Drupal core

+

+

+

+

+

This is a basic feature of content types in other portal / cms...

subscribe

subscribe

+1

+1

+

+1

But only if it plays nice with Field Group and carefully considers use cases supported by the other 3 or 4 related projects.

Isn't it a little premature to be asking for this? Of course we'd all like native multigroup in Drupal at some point, but Field collection itself is a young project who's feature set is still being added to and revised (see recent views discussion). I love field collection, and am very grateful for the work the maintainers have put into it, but I think they'd agree that this project isn't ready for core. Drupal 7 itself is in the early stages of its life cycle; just think of all the things that could happen over the next couple of years, including the development of other modules for similar use cases.

besides that is early, it's not the d7 version of multigroup, this is a totally different concept altogether. Multigroup is a collection of fields in an node/entity that are grouped together and stored within the entity it self. This module adds a relation between two entities and uses display logic to combine them at view/edit level.

It seems that multigroup would be more in place at the current fieldgroup module, as it is as far as I can think more of a formatter/widget issue then adding a complete different entity just to tie a bunch of fields together in a host form.

And no... I don't think this module should go into core, I personally think that drupal core should be lean and gems like this module should remain in contributed space.

I'm going out on a limb and postponing this until there is a stable version.

+1

+

For those still using "subscribe" comments, there's now a "Follow" button on top of the page. :]

I'd actually -1 seeing this in core, stable version or no. As was already mentioned, there are a number of modules that provide similar and/or related functionality. Which you use depends on your use case, and modules that are so interdependent definitely belong in the contrib space.

This doesn't mean the module is any less awesome, only that the decision whether or not to include it should be left to site builders, rather than further contributing to core bloat.

I wouldn't say its premature for asking for it to be in D8? It definitely needs some work but the advantages that this module provides is HUGE for different sets of data.

I've basically been waiting for this since D5.

Why would it need to be in core? Just because something is useful doesn't mean it should be in core. To the contrary, modules thrive in contrib, and tend to slow down development in core.

I don't believe there are any new features being added to D7 core at this point, and D8 core is well past feature freeze. Getting a D8 version of this module is still a great idea, though, so I'm going to mark this a duplicate of #1443960: Field Collection for Drupal 8 .

At most, it's a duplicate of
#607396: Killer feature: Fieldable Fields in core
and
#1792072: Merge field_collection module in Fieldable Fields killer feature in Drupal core

I want to refine my opinion by saying I am for a Field Collection style capability IF the performance issues with the current state of Field Collection is annihilated. Lots of FC records really hamper performance.

The FC team is addressing some of those issues, but yes, it can't be implemented without having proper performance.