Add field grouping to core

Created on 24 June 2009, about 15 years ago

Updated 19 October 2023, 8 months ago

Idea summary

What is the problem to solve?

(Missing functionality X, prevent Y from happening, make Z easier to do)

Who is this for?

(Evaluators, site visitors, content authors, site managers, (advanced) site builders, frontend developers, backend developers, core developers, site owners, other?)

Result: what will be the outcome?

(Describe the result: how will this improve things for the stated audience(s)?)

How can we know the desired result is achieved?

(Usability test, a metric to track, feedback)

--- Original report ---
The ability to group fields becomes an important usability factor as soon as you have more than a few fields. If we keep fieldgroup.module packaged with the CCK UI in contrib, any module wanting to group fields programmatically will have to depend on CCK contrib.

The fieldgroup.module as it is right now probably needs some additional work before it is ready for core.

Having a grouping mechanism is important to move the profile.module to use field storage (see #394720: Migrate profile module data to field API → ).

Proposed solution

Add https://www.drupal.org/project/field_group → in Drupal core
📌 Move Field Layout data model and API directly into \Drupal\Core\Entity\EntityDisplayBase Needs work

✨ Feature request

Status

Needs work

Component

Idea

Created by

🇨🇭Switzerland floretan

Live updates comments and jobs are added and updated live.

Fields in Core

Needs issue summary update
Issue summaries save everyone time if they are kept up-to-date. See Update issue summary task instructions.

Incomplete comments

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

Comment 12 months ago →
🇩🇰Denmark ressa Copenhagen
+1 for adding Field Group to core. It's such a basic site builder tool, which the position as #10 most installed module → . It is enabled on ~44% of Drupal 8/9/10/11 sites (182,000/412,000).
Comment 12 months ago →
🇩🇰Denmark ressa Copenhagen
Alternatively, 📌 Move Field Layout data model and API directly into \Drupal\Core\Entity\EntityDisplayBase Needs work could also solve this?
Comment 8 months ago →
🇩🇪Germany donquixote
@ressa Field layout solves a different problem.
I agree field group should be in core, where it can be done much cleaner than in contrib.

contrib.social Blog FAQ Discussions

Production build 0.69.0 2024