[DEFECT] When push publishing children before parent, the relationship can break
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 970
- Forks
- 486
- Avg merge
- 3d 33m
- Merged PRs (30d)
- 170
Description
Problem Statement
When push publishing a content type with 2 or more relationships, and pushing the children first before the parent, can cause the relationship to break.
Steps to Reproduce
https://github.com/user-attachments/assets/f7fd28b9-507b-41e4-8f2d-0689c29ca2bb
Acceptance Criteria
Ensure that no matter what order pushing parent and child content types, the relationship remains in tact.
dotCMS Version
Latest Evergreen 26.01.12-01
Severity
Medium - Some functionality impacted
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 with the issue's reproduction steps and video, focusing on dotCMS push publishing for content types with multiple relationships. Verify publishing children before parents and the reverse order, then confirm that all relationships remain intact in both cases.
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
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100