dotCMS / dotCMS/core

Align Host Content Type behavior in New Edit Mode with Old Edit Mode

Open
#34,724 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

dotCMS: New Edit Contentlet Needs UI Priority : 3 Average Team : Falcon
Dominant language
Java
Stars
970
Forks
486
Avg merge
3d 33m
Merged PRs (30d)
170

Description

Description

When New Edit Mode is enabled and the Host Content Type is opened through the Sites Portlet, its behavior should match the existing behavior from Old Edit Mode.

This applies to the following entry points in the Sites Portlet:
• Sites Portlet → Add Site → Start with a blank site
• Sites Portlet → Click over any site to edit it
• Sites Portlet → Right-click over any site → Edit

Currently, behavior differs from Old Edit Mode. The goal is to ensure functional parity and UX consistency.

Additionally:
• If a siteKey is already saved:
• An Edit button must be displayed
• When clicked, a confirmation dialog must appear (same behavior as Old Edit Mode)

The New Edit Mode implementation must replicate the Old Edit Mode.

Acceptance Criteria
  • When New Edit Mode is enabled, opening the Host Content Type from any Sites Portlet entry point behaves the same as in Old Edit Mode
  • Behavior is consistent across:
    • Add Site → Start with a blank site
    • Click on a site → Edit
    • Right-click → Edit
  • If a siteKey is already saved, an Edit button is displayed
  • Clicking the Edit button triggers a confirmation dialog identical in behavior to Old Edit Mode
  • No regressions introduced in site creation or editing flows
  • Smoke test validates Host creation and update workflows
Priority

Medium

Additional Context

https://github.com/user-attachments/assets/872d244d-facf-459c-baaf-97a489bfa585

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 Sites Portlet entry points listed in the issue and compare how Host Content Type opens in New Edit Mode versus Old Edit Mode. Trace the saved siteKey and Edit button flow, including the confirmation dialog. Use the requested smoke test to validate Host creation and update workflows across all three entry points.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.