- 🇨🇦Canada othermachines Edmonton, Alberta
+1 Agree that this is a more sensible default, and also that modifying the existing transition is sufficient. Will come back to review.
If a node has a published version, with working draft revisions which are newer than the published revision, then taking this node offline (archived) so the public can't see it is a complicated process that's not easy to discover.
1. Create a node under moderation
2. Publish a revision
3. Create some further working draft revisions
4. Try to unpublish the node. There is no option at this point to archive it, which is how node are unpublished when under moderation
The only way I think this is possible is like this:
5. Create a new published revision
6. Create a new archive revision, now that this transition is allowed
Add a transition to the Editorial workflow for draft -> archived
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
+1 Agree that this is a more sensible default, and also that modifying the existing transition is sufficient. Will come back to review.