Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.Problem/Motivation
The "Manage Display" portion of the Field UI loops through all known regions, and displays the fields for each of them.
Previous to 8.3.0, this list of regions was hardcoded to "Content" and "Disabled".
Now with the Field Layout module customizing this list of regions, a very confusing bug can arise.
When a region's machine name is changed during development, any field assigned to that region will no longer be shown in the UI.
This is mitigated by an easy workaround: change to another layout, and change back.
Proposed resolution
Because we can't (and shouldn't) do tracking of changes to the layout definitions, there is no reasonable way to update each instance of the layout.
Instead, the Field UI should show all fields with invalid regions in the "disabled" region.
Remaining tasks
User interface changes
Fields in invalid regions will be displayed as "Disabled"
API changes
N/A
Data model changes
N/A
| Comment | File | Size | Author |
|---|---|---|---|
| #4 | 2870410-region-4.patch | 3.72 KB | tim.plunkett |
| #4 | 2870410-region-4-interdiff.txt | 1.5 KB | tim.plunkett |
| #2 | 2870410-region-2.patch | 2.22 KB | tim.plunkett |
Comments
Comment #2
tim.plunkettComment #4
tim.plunkettComment #5
DyanneNovaI've tested and the patch successfully moves the orphaned fields into the disabled region.
Comment #6
alexpottCommitted and pushed 992ed45 to 8.4.x and 57bd004 to 8.3.x. Thanks!
@DyanneNova thanks for reviewing the issue. When you do post a review, be sure to describe what you reviewed and how. This helps other reviewers understand why you considered the issue RTBC (and is considered for issue credit).