When Content Moderation module is enabled, different revisions of a node each have their own moderation state, e.g.:
- r5: draft
- r4: draft
- r3: published - current revision
- r2: published
- r1: draft
These revisions are listed on the Revisions tab on a node, at /node/ID/revisions, but that table does not show the state.
Currently, reverting a past revisions preserves its state, which means that:
- if you revert a draft, the new copy revision that is made is also a draft: e.g. new r6 is a copy of r1, and r3 is still the current revision
- if you revert a published revision, the new copy revision is also published: e.g. new r6 is a copy of r2, and is the *new current revision*.
Therefore, it's important to know the state of what you are reverting, as it changes what is live public content! ✨ Provide users with the option to select an appropriate moderation state when reverting to a previous revision Needs work seeks to allow selecting the moderation state of the new copy in a revert operation, but even with this change, it would still be useful to see the state of the different revisions.
The work for creating a unified entity revisions UI ( ✨ Implement a generic revision UI Fixed ) will break any patch here, but I think work on the node UI could be adapted to the new generic revisions controller class in that issue, when it eventually lands.
Alter the node route to change the controller.
New controller inherits from the existing one, and hands over to the parent class for a bundle that's not under moderation.
Once the generic UI lands, alter routes for all moderated entity types based on their 'version-history' link template.
Needs work
11.0 🔥
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
I couldn't apply the patch from #22. Recreated it to work with the latest 10.2
#22 doesn't apply on 10.2.x after
📌
Allow controller service wiring via constructor parameter attributes
Fixed
#23 is missing the BuildAlter class, adding it back.