Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.I just activated the content moderation module to take a look how it behaves compared to workbench suite.
I'm shocked. The "Review" state is missing by default. As I see no case about this in the queue. So this must be intentionally.
But you guys may missed something.
- Who needs this module? Very large installations.
- Why do they need this module? Because they fear idiots will publish non-reviewed content.
- When is there no need for this module? If I do not need to review content.
Using Drupal content moderation without a review state does not require this module. It simply makes NO sense. I see I can reconfigure all this, but such defaults make zero sense and really this config is complex for other beginners.
Issue fork drupal-2843451
Show commands
Start within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
compare
Comments
Comment #2
hass CreditAttribution: hass commentedComment #3
Sam152 CreditAttribution: Sam152 as a volunteer and at PreviousNext commentedThere isn't a bug here, so marking as a feature request.
Comment #4
hass CreditAttribution: hass commentedNot a bug? The module is totally useless without a review process. The review process is WHY you enable content moderation. The name already says by itself what is is made for - MODERATION. Currently there is no moderation process. Just a unpublish/publish.
Without the module I have the same process:
A draft is by definition NOT ready for getting published. Maybe someone rewrites a draft 10 times before it get's to review and than will be published. No review means I need to publish drafts that may or may not ready. Nobody knows.
Comment #5
Sam152 CreditAttribution: Sam152 as a volunteer and at PreviousNext commentedQuite funny, but this is almost the actual issue described as an example of a major feature request.
Comment #6
hass CreditAttribution: hass commentedI'm not reading such cases. Feature regressions are always bugs.
Comment #7
timmillwoodThe "Review" state was removed in https://www.drupal.org/node/2725533#comment-11402055 based on #2757275: Decide on default moderation states.
Comment #8
hass CreditAttribution: hass commentedI see no discussion why Review process was "removed" or just not implemented. Webchick suggested a list of states and all follow "blind".
As noted - this module is totally useless and makes no sense without this step. "Moderation" of content is not possible with this workflow.
Cannot belive I'm the first one saying this. Don't get it, sorry.
Comment #9
timmillwoodPersonally is makes perfect sense.
Content is added as the "draft" state, someone reviews it and moves it to "published", which it's finished with it gets moved to "archived". Simple.
If you need more steps, add them.
Comment #10
hass CreditAttribution: hass commentedHow should he know that you are done with your draft? If there are 100 or 1000 drafts I'm interrested how you find out what is ready and what is still in in draft state where authors started to work on, but have not finished their work. FAIL.
This module is a content moderation module. Moderation requires a review. This does not exists for unknown reasons. This module must have review state by default.
Comment #12
timmillwoodIn #2755073-107: WI: Content Moderation module roadmap @xjm mentioned "this is a feature request that can porbably be wontfix". I agree.
Comment #13
bkosborneI stumbled across this and am a big confused over the issue. Couldn't you just add a new state called "Reviewed", create the proper transitions to that state, assign the appropriate user roles access to those transitions, and be done with it? That's all possible with this module out of the box.