dotCMS / dotCMS/core

Text/URL field auto-populated with unexpected value in Compact Edit (New Edit Content UI)

Open
#35,580 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

OKR : Customer Support Team : Maintenance
Dominant language
Java
Stars
970
Forks
486
Avg merge
3d 33m
Merged PRs (30d)
170

Description

Problem Statement

When a content type containing a Text field (used as a URL/CTA link) is added to a page and
opened via Compact Edit mode (inline editing from the page editor), the Text field is
automatically pre-populated with an unexpected/random URL value — before the user makes any
changes. If the content is saved in this state, the bad value is persisted, overwriting the
intended URL.

The same content opened in Full Editor mode shows the field correctly as empty or with
the correct saved value.

Steps to Reproduce

https://drive.google.com/file/d/1F1etBH100t00-N5pnx3wZCRgVUT-4u76/view?usp=drive_link

Steps to Reproduce

  1. Create a new Content Type with a Text field (variable name: url)
  2. Create a contentlet of that type — leave the url field empty
  3. Add a Container using that Content Type to a Page
  4. Open the Page in the Page Editor
  5. Hover over the contentlet and click the inline edit (pencil) icon to open Compact Edit mode
  6. Before making any changes, observe the url Text field
Acceptance Criteria

Expected Behavior

The url field should be empty (or show the previously saved value).

Actual Behavior

The url field is pre-populated with an unexpected URL value (appears to be the current
page URL, admin URL, or browser origin). If saved, this value is persisted on the contentlet.

dotCMS Version

26.04.28-02

Severity

Medium - Some functionality impacted

Links

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

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.

Research direction

Start with the Compact Edit or New Edit Content UI entry point and reproduce the issue using a content type with an empty url Text field. Compare the field initialization in Compact Edit with Full Editor, then verify that opening and saving without changes preserves an empty or previously saved value rather than a page or browser URL.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
frontend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
55/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.