Preserve Article Status on Fork and Republish
under review
Akash Sivaraman
When updating an article and setting its status to “None” under Configure Category Settings during publish, the system behaves correctly. However, when the same article is forked and republished, the status is unexpectedly changed to “Updated” after the publish event—even though the UI indicates “None” prior to publishing.
Expectation -
-> When an article is forked, the new version should inherit the previous status by default.
-> The publish modal should display the current (inherited) status rather than defaulting to “None.”
-> The system should respect the user’s selection during publish and not override it post-publish.
-> Status should only change if the user explicitly selects a different option.
Log In
Mohamed Shakheen
marked this post as
under review
Mohamed Shakheen
Hi Raspberry Basilisk
Thank you for highlighting this behavior in detail.
We understand the concern—there is a clear inconsistency between the status shown in the UI during publish and the final status applied after publishing a forked article. This can lead to confusion and unintended status changes.
Based on your inputs, the expected behavior around status inheritance and respecting user selection during publish is valid:
- Forked articles should retain the previous version’s status by default.
- The publish modal should accurately reflect the inherited status.
- The system should not override the selected status post-publish unless explicitly changed by the user.
We’ve captured this as a product limitation for further investigation. The team will analyze the current workflow or a gap in how status handling is implemented for forked articles.
We’ll keep you posted here once we have more clarity on the fix or next steps.
Akash Sivaraman
+Raspberry Basilisk