dotCMS / dotCMS/core

UVE: Show full content names in content search/list panel (multi-line wrapping)

Open
#35,876 1 comment 1 reaction 2 assignees View on GitHub

@fmontes is already working on this.

Since Jun 1, 2026.

  • #35878 by @copilot-swe-agent — merged
Enhancement Team : Scout
Dominant language
Java
Stars
970
Forks
486
Avg merge
3d 33m
Merged PRs (30d)
170

Description

Problem

When browsing or searching for content in the Page Editor, long content names are cut off, making it difficult to select the correct item — especially when multiple content pieces share similar naming prefixes.

Goal

Restore multi-line wrapping for content names in the content search/list panel, as was available in previous dotCMS versions.

Target Personas
  • Developer teams
  • Content teams
  • DevOps teams
  • System administrators (dotCMS)
Demo Expectations

Setup: A dotEvergreen environment with several content items that have long names (50+ characters)
Steps to Demo:

Open the Page Editor and launch the content search/list panel
Browse or search for content with long names
Show that full names are visible, wrapping to multiple lines as needed
Compare side-by-side with a screenshot of the truncated behavior (before fix)
Demonstrate behavior across at least two different browsers

Pass Criteria: Reviewer can read the full content name without any truncation or tooltip dependency
Fail Criteria: Any ellipsis (...) still appears on content names in the panel

Acceptance Criteria

Content names in the Page Editor content search/list panel are no longer truncated with ellipses
Long content names wrap across multiple lines within their container
The layout of the content list panel remains clean and usable with multi-line names (no overflow or broken layout)

User Stories

No response

Links

https://helpdesk.dotcms.com/a/tickets/37576

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.