Make consistent regions in code for fields UI overview screens

Created on 16 September 2012, about 13 years ago

Updated 11 August 2025, about 1 month ago

Spin-off from 📌 [META] Gradual changes to Field UI Closed: duplicate . This is just the first step in a refactoring process field ui needs.

Regions in Field UI

Now we have "main", "visible", "hidden" as default regions and separate row handlers to work with, etc ... . To alter the fields UI screens, it's very difficult and inefficient altering to obtain things that should be transparent or done behind the scene.
The solution is to use content/hidden so the concept of layouts can more easily be introduced later.

This patch includes:

make regions consistent across the fields and display overview screens. Important, since there is only 1 region, it won't be shown at display screen.
make row handling in PHP consistent for all screens. I started with "content" and "hidden" to not change too much at the same time.
getRegion in javascript always knows the region and not hardcoded on the hidden/main region anymore.
Refactor the code so the overview screens are based on the same base class. (One change is for instance that a method getRegions will define the regions and how the behavior is by default).
added the region column so it works with regions by default. Nesting behavior is now consistent on both screens as well.

The only visually thing is that you need to change regions to change regions.
Before you needed to set the format type to something or "hidden", which triggered the region update.

📌 Task

Status

Postponed: needs info

Version

11.0 🔥

Component

field_ui.module

Created by

🇧🇪Belgium Stalski

Live updates comments and jobs are added and updated live.

JavaScript

stale-issue-cleanup
To track issues in the developing policy for closing stale issues, [Policy, no patch] closing older issues

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 about 1 month ago →
🇺🇸United States smustgrave
Thank you for creating this issue to improve Drupal.

We are working to decide if this task is still relevant to a currently supported version of Drupal. There hasn't been any discussion here for over 8 years which suggests that this has either been implemented or is no longer relevant. Your thoughts on this will allow a decision to be made.

Since we need more information to move forward with this issue, the status is now Postponed (maintainer needs more info). If we don't receive additional information to help with the issue, it may be closed after three months.

Thanks!

contrib.social Blog FAQ Discussions

Production build 0.71.5 2024