Scheduling a new draft of an already published node silently deletes the published page.

Created on 28 January 2025, 3 months ago

It's impossible to schedule a new draft release without silently losing the published version.

1. Create a new "Test" page with text: "Published", publish it.
2. Create a draft version for "Test" page with text: "Draft", set status to draft, save.
↳ When visiting /test page: can see the published version ("Published" text) and at /node/<id>/latest you see "Draft". ✔
3. Edit the page, change the text to "Scheduled", set status to scheduled, save.
↳ Now you can only see the unpublished "Scheduled" text page, non-admins get 404. ✖

Expectations: /node/<id>/latest shows "Scheduled" version and the /test page still shows "Published".

Marked as Major as we're technically losing the published content without any notice.

🐛 Bug report

Status

Active

Version

3.0

Component

Code

Created by

🇱🇻Latvia Phonoman

Live updates comments and jobs are added and updated live.

Comments & Activities

Issue created by @Phonoman
Comment 3 months ago →
🇱🇻Latvia Phonoman
Comment 3 months ago →
🇱🇻Latvia Phonoman
Ok, this was actually a misconfigured "Scheduled" content moderation state!
"Default revision" was checked, so this made the latest revision fall back to Scheduled (unpublished) state.
This seems to work correctly after all.
Comment about 1 month ago →
🇬🇧United Kingdom jonathan1055
Thanks for letting us know.

Production build 0.71.5 2024