Problem/Motivation

Part of #3624760: Plan: consistent Display Builder entry points in the Navigation top bar.

On an entity page, the display built with Display Builder is reachable only as a local task in "More actions" ("Display: Full content"), with the same label whether an override exists or not. Following it on an entity without an override creates one. "Display: Teaser" is listed on the full page, where no teaser is rendered. The bundle display has no entry at all.

Proposed resolution

Add one entry to the "Display" dropdown for the display rendering full:

  • the bundle display, scope "every bundle item";
  • or the override, scope "this item only";
  • or "Customize this item", when overridable and not yet overridden. Creating an override becomes an explicit action; the builder URL no longer creates one on GET.

Remove our override local tasks from the top bar when Navigation is enabled, keep them as tabs otherwise.

Remaining tasks

  • Evaluate: list the overridden bundle display as inactive, to explain why editing it changes nothing on this item.
  • Tests: bundle display, override, and overridable without override; visiting an override builder URL no longer creates an instance.
Command icon Show commands

Start within a Git clone of the project using the version control instructions.

Or, if you do not have SSH keys set up on git.drupalcode.org:

Comments

mogtofu33 created an issue. See original summary.

mogtofu33’s picture

Assigned: Unassigned » pdureau
Status: Active » Needs review
Issue tags: +display_builder-1.0.0-beta8, +UX, +AI-accelerated

Note:

  • Visiting the override builder URL still creates an instance. The "Customize this content" entry makes it an explicit action, but the underlying route behavior is unchanged. It belongs in the override buildable, not the top bar.
  • The override label reads "Entity view override: Article [2] (Full content)". It comes from the buildable's own label, which keeps it consistent with the Instances panel, but it's wordy in a menu.
pdureau’s picture

Status: Needs review » Needs work

Works only for full display, not for default (which is the Full when there is no Full).

The cache is not invalidated when we activate or disable full display

pdureau’s picture

Assigned: pdureau » mogtofu33
mogtofu33’s picture

Assigned: mogtofu33 » pdureau
Status: Needs work » Needs review
pdureau’s picture

Assigned: pdureau » mogtofu33
Status: Needs review » Reviewed & tested by the community

Great

  • mogtofu33 committed 7d71e62c on 1.0.x
    task: #3624762 Top bar entry for the main content display: bundle...
mogtofu33’s picture

Assigned: mogtofu33 » Unassigned
Status: Reviewed & tested by the community » Fixed

Now that this issue is closed, review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, credit people who helped resolve this issue.