[DEFECT] Contentlets remain in Draft state after page publication in UVE
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 970
- Forks
- 486
- Avg merge
- 3d 33m
- Merged PRs (30d)
- 170
Description
Problem Statement
In our UVE page editor, contentlets can exist in either 'Draft' or 'Live' states, and pages also maintain their own publication state. The expected behavior is that when a page is published (by executing the 'publish' workflow action), ALL contentlets contained within that page should transition to 'Live' status. Specifically, if any contentlets are in a 'Draft' state at the time of page publication, they should automatically be updated to 'Live'.
However, this is not happening. The page successfully transitions to a published state, but any contentlets that were in 'Draft' state prior to publication remain in 'Draft'. This leads to significant issues because 'Draft' content is not displayed to end-users when viewing the published page in a browser, resulting in incomplete or broken page content. This severely impacts customer publishing workflows and the integrity of the content they are trying to make public. This issue appears to be consistent upon every page publication attempt. Browser and OS details are not directly relevant as the issue stems from the publishing process backend, affecting all public-facing content display.
Steps to Reproduce
- Access the UVE page editor.
- Create or select an existing page.
- Add one or more contentlets to this page, ensuring at least one of them is saved in 'Draft' state.
- Save the page (if necessary).
- Execute the 'publish' workflow action for the selected page.
- After the publishing process completes, verify the state of the contentlets that were previously in 'Draft' (e.g., by checking their status in the editor or through an API call if available).
- Observe that the contentlets that were in 'Draft' state prior to publication have not transitioned to 'Live' and remain in 'Draft' state.
- Access the published page in a web browser.
- Observe that the content corresponding to the 'Draft' contentlets is not displayed to the end-user.
Acceptance Criteria
- Upon successful publication of a page via the 'publish' workflow action, all associated contentlets that were previously in 'Draft' state must automatically transition to 'Live' state.
- The content from all contentlets (now 'Live') on the published page must be correctly and fully displayed to end-users when viewed in a web browser.
- The fix must ensure that customer publishing workflows are no longer negatively impacted by 'Draft' content failing to appear on published pages.
dotCMS Version
b88ae57
Severity
High - Major functionality broken
Links
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the issue in the UVE page editor with a page containing a Draft contentlet, then execute the page's publish workflow action. Inspect the backend path triggered by that action and verify contentlet states through the editor or API. Done means every associated Draft contentlet becomes Live and its content appears on the published page.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend, content
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100