Skip to content

remove statusChange delete commands when content is republished from draft/expired state#1373

Open
johan-bell wants to merge 15 commits intomainfrom
1278-api-remove-deletecmds-from-database-when-draftedexpired-is-set-back-to-published
Open

remove statusChange delete commands when content is republished from draft/expired state#1373
johan-bell wants to merge 15 commits intomainfrom
1278-api-remove-deletecmds-from-database-when-draftedexpired-is-set-back-to-published

Conversation

@johan-bell
Copy link
Collaborator

No description provided.

@MrDirkelz
Copy link
Collaborator

MrDirkelz commented Mar 11, 2026

Something to look at:

  • Currenly deleteCmds are not generated when a document is set to an "expired" state (maybe should consider generating deleteCmds for expired documents)

Copy link
Contributor

@ivanslabbert ivanslabbert left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The fix needs to remove existing deleteCmd docs with docId = contentDoc ID and deleteReason = DeleteReason.StatusChange if the previous state was draft and the current state is published.

@johan-bell johan-bell force-pushed the 1278-api-remove-deletecmds-from-database-when-draftedexpired-is-set-back-to-published branch from 63c10a3 to 28b9fb6 Compare March 19, 2026 17:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

API: Remove possible deleteCmds from database when a draft document is set to published

3 participants