Problem/Motivation

The tabs on the node edit form cannot be reordered via the UI. Some of the tabs map to a field in the 'Manage form display' settings, but as this is based on fields, these settings do not affect the tab display.

You can reorder fields within tabs, e.g. Authored on and Authored by within the Authoring info tab, or Sticky and Promoted within the Promotion options tab. But the tab order is hardcoded, although this isn't as obvious with fields that are mapped 1-1 with a tab like URL alias or Comments.

Proposed resolution

Develop a method (TBC) for reordering the tabs within the UI.

Remaining tasks

  1. Agree on an approach
  2. Write a patch with tests
  3. Review

User interface changes

TBC but it would add a UI for reordering the tabs.

API changes

TBC

Data model changes

TBC

Release notes snippet

N/A

Original report by chrisck

Problem/Motivation

The URL alias field and URL redirect field are not respecting their weight order on the content edit/create page. I know URL redirect is a module while URL alias is part of core, but it just so happens both of these fields' weights are not working. I've tried using both the drag handles and editing the row weights.

Steps to reproduce

  1. Go to admin/structure/types/manage/page/form-display
  2. Move URL alias field above "authored by" or "authored on" field using the drag handles or row weights

URL alias field weight order
content edit showing order weight not respected

CommentFileSizeAuthor
manage-form-display-weight.png10.79 KBchrisck
content-edit.png8.99 KBchrisck

Comments

chrisck created an issue. See original summary.

chrisck’s picture

chrisck
he/him
Location BC, Canada
commented
chrisck’s picture

chrisck
he/him
Location BC, Canada
commented
Issue summary: View changes
pameeela’s picture

pameeela commented
Title: URL alias and URL redirect field not respecting weight order in content form » Allow node form tabs to be reordered
Category: Bug report » Feature request
Issue summary: View changes
Issue tags: -fields, -field, -weight, -weights, -url alias, -url redirect +Bug Smash Initiative

@chrisck, I believe this is a feature request. The manage form settings is for fields, not tabs, and it does respect the field weight for those fields but only within a given tab. E.g., you can reorder authored on and authored by within the Authoring info tab, or sticky and promoted within the promoted tab. So the tab order is hardcoded, although this isn't as obvious with fields that are mapped 1-1 with a tab like URL alias. (Also menu settings is a tab and it's not represented in the form display config at all.)

I suspect that there might already be an issue for this, but I couldn't find it.

Also removed keyword tags per the issue tag guidelines.

pameeela credited mlncn.

pameeela’s picture

pameeela commented
Related issues: +#3103426: Remove hard-coding of authoring information for administrators, node options for administrators, and meta data from content edit forms

Added #3103426: Remove hard-coding of authoring information for administrators, node options for administrators, and meta data from content edit forms as related because I closed it as a duplicate, and added mlncn here as a contribtuor.

Version: 9.0.x-dev » 9.1.x-dev

Drupal 9.0.10 was released on December 3, 2020 and is the final full bugfix release for the Drupal 9.0.x series. Drupal 9.0.x will not receive any further development aside from security fixes. Sites should update to Drupal 9.1.0 to continue receiving regular bugfixes.

Drupal-9-only bug reports should be targeted for the 9.1.x-dev branch from now on, and new development or disruptive changes should be targeted for the 9.2.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.1.x-dev » 9.3.x-dev

Drupal 9.1.10 (June 4, 2021) and Drupal 9.2.10 (November 24, 2021) were the last bugfix releases of those minor version series. Drupal 9 bug reports should be targeted for the 9.3.x-dev branch from now on, and new development or disruptive changes should be targeted for the 9.4.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.3.x-dev » 9.4.x-dev

Drupal 9.3.15 was released on June 1st, 2022 and is the final full bugfix release for the Drupal 9.3.x series. Drupal 9.3.x will not receive any further development aside from security fixes. Drupal 9 bug reports should be targeted for the 9.4.x-dev branch from now on, and new development or disruptive changes should be targeted for the 9.5.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.4.x-dev » 9.5.x-dev

Drupal 9.4.9 was released on December 7, 2022 and is the final full bugfix release for the Drupal 9.4.x series. Drupal 9.4.x will not receive any further development aside from security fixes. Drupal 9 bug reports should be targeted for the 9.5.x-dev branch from now on, and new development or disruptive changes should be targeted for the 10.1.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

damienmckenna’s picture

damienmckenna
Location TN, USA
commented

If all of the meta data fields were exposed as extra fields, would that work? I just ran into this problem with a contrib module where the weight value from core.entity_form_display.node.CONTENTTYPE.default.yml is overriding the value I'm setting via hook_form_alter().

Version: 9.5.x-dev » 11.x-dev

Drupal core is moving towards using a “main” branch. As an interim step, a new 11.x branch has been opened, as Drupal.org infrastructure cannot currently fully support a branch named main. New developments and disruptive changes should now be targeted for the 11.x branch. For more information, see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 11.x-dev » main

Drupal core is now using the main branch as the primary development branch. New developments and disruptive changes should now be targeted to the main branch.

Read more in the announcement.