Revision/version language on revision listing page is misleading with content moderation enabled

Created on 3 August 2017, over 7 years ago
Updated 18 September 2023, about 1 year ago

Problem/Motivation

The current language around revisions/versions on the revision listing page is misleading and confusing. There are a few issues:

Tab/task label

When there is a forward revision in existence, a new primary task tab is presented on nodes that is called "Latest version". This is confusing since nearly everywhere else Drupal uses the term "revision" rather than "version".

Proposal: Update the language to read "Latest revision".

Confusing "Set as current revision" button

The node module provides a "Set as current revision" button for forward revisions. When content moderation is enabled, clicking this button, and submitting the confirmation form works, and even displays a success message. However, the current revision is left at the one that it was set at prior to submitting the form. A new revision is created, but with the default moderation state. The confirmation form has no help text, and the buttons presented there are "Revert" and "Cancel".

Proposal: Relabel the link to Copy as latest revision to be more clear about what is actually happening. Relabel the confirmation form button to match, and provide appropriate help text.

Risk: is it confusing to put this option on the revision that is already the latest revision? We could hide completely on the latest revision, but some of the work going on in this related ticket really needs it to exist: ✨ Provide users with the option to select an appropriate moderation state when reverting to a previous revision Needs work . I propose we keep it for now...it's still a step forward.

Unclear "revert" button

The node module also provides a "revert" button on old revisions. It's not clear what "revert" means in this context. The confirmation form has no help text.

Proposal: Relabel this to read Copy as latest revision to be more clear about what is actually happening. Provide appropriate help text on the confirmation form.

Risk: Depending on what ends up happening in this related ticket ( ✨ Provide users with the option to select an appropriate moderation state when reverting to a previous revision Needs work ), this terminology might need to be updated in the future.

πŸ› Bug report
Status

Needs work

Version

11.0 πŸ”₯

Component
Content moderationΒ  β†’

Last updated 1 day ago

  • Maintained by
  • πŸ‡¦πŸ‡ΊAustralia @Sam152
Created by

πŸ‡ΊπŸ‡ΈUnited States jhedstrom Portland, OR

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

  • πŸ‡³πŸ‡ΏNew Zealand john pitcairn

    The tab should be "Latest revision" by default.

    I have users really struggling to understand Drupal revisions, especially with content moderation in the mix. The problem is "current revision" does not necessarily mean "published". It could be:

    • The latest revision of an entity that has never been published. This is also the default revision.
    • The published revision, with no forward drafts. This is also the default revision.
    • The published revision, with some forward drafts on top of it. The latest draft is the default revision.
    • A previously-published revision, with no forward drafts. This is also the default revision.
    • The latest forward draft of a previously-published revision. This is also the default revision. Current no longer corresponds to a revision that is or was published - WTF?

    Given the above, I don't think "current revision" is a useful term in a list of revisions. It's only relevant internally. Editors want to be able to easily identify:

    1. The published revision.
    2. If there is no published revision, the last-published revision.
    3. The editable revision.
    4. Whether the entity as a whole is published (there may be a long list of forward drafts).

    Then the revision action labels and confirmation form text needs to be different, depending on what the actual outcome will be:

    • Will the revision become published?
    • Will the revision become the new editable revision?
    • Are there any forward drafts that will become orphaned?

    We have workflow state transitions and state transition labels. Can we make use of those?

Production build 0.71.5 2024