Publishing issues with Required Related Field.
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 970
- Forks
- 486
- Avg merge
- 3d 33m
- Merged PRs (30d)
- 170
Description
Problem Statement
When a content type has a related field that is set as Required, it breaks the right click context menu Publish button, as well as publishing based on the Publish Date Field set within the Content Type. The error it produces claims that there is no item within the required relationship field, despite there being a related contentlet.
Steps to Reproduce
In a demo starter environment on the latest version.
- Go to the Content Types and edit the Activity content type
- Add a relationship field, relate any content type and set it as required.
- Go to the Content Search screen.
- Open any activity and attach an item to the related field created.
- Save the content.
- Exit out of the content.
- Try to publish the content with the right click menu (Might need to unpublish first)
https://github.com/user-attachments/assets/4ff1742d-5013-4351-9437-aaccc8ad4a22
Acceptance Criteria
The Right click context menu publishing as well as the automatic publishing based on the "Publish Date Field" if set should function with related fields that are set to required.
dotCMS Version
25.07.09-1
25.07.07-1
Latest
Proposed Objective
Customer Support
Proposed Priority
Priority 2 - Important
External Links... Slack Conversations, Support Tickets, Figma Designs, etc.
https://dotcms.freshdesk.com/a/tickets/32095
Assumptions & Initiation Needs
No response
Quality Assurance Notes & Workarounds
No response
Sub-Tasks & Estimates
No response
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
Reproduce the issue from the Content Types and Content Search screens using a required relationship field, then compare right-click publishing with automatic publishing from the Publish Date Field. Done means both publishing paths work when the required relationship contains a related contentlet, without the missing-relationship error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 35/100