At the moment I had a group of fields I want to use in every content-type and to define it for every single content-type directly there.

It would we very cool if I can e.g. define a group which I can share for selected content-types.

an example:

the group I want to share for content-types like "blog", "artists" (own defined), article and page:

1. selectbox "layout" from a taxonomy term
2. selectbox "homepage-teaser" (e.g. yes/no or something like position 1, position 2 ...)
3. selectbox "subpage-teaser-display" (e.g. highlight, standard, list-item ...)

These 3 fields should be available in every selected content type.
If I then decide to add a forth value or other changes I just had to add it to that group and don´t had to add it on every content-type.

Is this possible ?
Does this idea fit to your module and your ideas of it?

Comments

Stalski’s picture

Stalski CreditAttribution: Stalski commented
Status: Active » Closed (won't fix)

Hey, it is certainly possible but i don't see it happen in field group, as field_group is designed to group fields. What you want is in fact more field_sets or an even easier way then to share fields across entities. You can always "use existing field" everywhere and you have several export possibilities (in core, ctools, features) . So here i see no issue.
If we would do this, then the system would need a group reference system so we never delete some group that shouldn't somewhere else.
So we did not want to complicate things and stay with display of fields by using groups.