Problem/Motivation

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.

Steps to reproduce

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

Proposed resolution

Add a transition to the Editorial workflow for draft -> archived

Remaining tasks

User interface changes

API changes

Data model changes

Release notes snippet

CommentFileSizeAuthor
#5 3214914-draft-to-archived-5.patch1.8 KBdaniel korte

Comments

joachim created an issue. See original summary.

Version: 9.3.x-dev » 9.4.x-dev

Drupal 9.3.0-rc1 was released on November 26, 2021, which means new developments and disruptive changes should now be targeted for the 9.4.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.4.x-dev » 9.5.x-dev

Drupal 9.4.0-alpha1 was released on May 6, 2022, which means new developments and disruptive changes should now be targeted for the 9.5.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.5.x-dev » 10.1.x-dev

Drupal 9.5.0-beta2 and Drupal 10.0.0-beta2 were released on September 29, 2022, which means new developments and disruptive changes should now be targeted for the 10.1.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

daniel korte’s picture

daniel korte
he/him/his
Primary language English
Location Brooklyn, NY
commented
Status: Active » Needs review
StatusFileSize
new 3214914-draft-to-archived-5.patch1.8 KB

I’m not sure a new transition is needed. Could we change the existing “Archive” transition to include “Draft” in the “From” state?

Status: Needs review » Needs work

The last submitted patch, 5: 3214914-draft-to-archived-5.patch, failed testing. View results

othermachines’s picture

othermachines commented

+1 Agree that this is a more sensible default, and also that modifying the existing transition is sufficient. Will come back to review.

Version: 10.1.x-dev » 11.x-dev

Drupal core is moving towards using a “main” branch. As an interim step, a new 11.x branch has been opened, as Drupal.org infrastructure cannot currently fully support a branch named main. New developments and disruptive changes should now be targeted for the 11.x branch, which currently accepts only minor-version allowed changes. For more information, see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 11.x-dev » main

Drupal core is now using the main branch as the primary development branch. New developments and disruptive changes should now be targeted to the main branch.

Read more in the announcement.