dotCMS / dotCMS/core

[DEFECT] UVE Triggers layout save when changing the page template

Open
#34,280 0 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 updating the template field of a page while standing on Layout tab of the UVE, it is recognizing it as a change in the Layout, triggering a save and resulting in a Custom Page Layout when the expected result was to change the template

Steps to Reproduce

https://github.com/user-attachments/assets/7a7dad0f-a61a-41aa-8f59-db83da6d9363

  1. Create a Page
  2. Go to the UVE
  3. Go to Layout tab
  4. Click on properties
  5. Change the template for another existing one
  6. Click on publish
  7. Close the tab and wait a bit
  8. When the save is triggered you will see a message indicating that
  9. After the save, click on properties, you will see the Custom Page Layout template instead of the one you selected on step 5
Acceptance Criteria
  • If the goal is to update the template field (the layout was never modified), a save should not be triggered.
dotCMS Version

latest

Severity

Low - Minor issue or cosmetic

Links

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

Reproduce the issue in the UVE using the listed steps, focusing on the Layout tab, template properties, publish flow, and delayed save. Trace where changing the template is classified as a layout change and identify the existing save trigger or change-tracking tests. Done means changing only the template does not trigger a layout save or produce a Custom Page Layout.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.