Allow editors to edit published nodes without it reverting to the draft state. [#2172361]

Hello,

I would like to allow my editors make edits to a published node without the state changing back to draft.
It seems like this should be an option somewhere.

In my case i have the following roles
Contributor: Can add nodes, work with it in a draft and mark it as "needs review"
Editors: Can add nodes, as well as make edit to and publish nodes in the "needs review" state.

If an editor makes changes to an already published node, it should not go back to the draft state. I understand that they can select published in the dropdown. But that is hidden in the bottom vertical tab and they forget about it often, and then don't realize why their changes aren't published. It would be nice to leave the post in its current state if the user has permission to move it to that state and only move it back to draft if they dont have permission to publish.

I hope that makes sense.
Thanks.

Comments

Comment #1

loze commented 13 January 2014 at 10:17

This would also involve changing the text of the edit tab to read "edit" rather than "new draft" in this case.

Comment #2

input commented 15 January 2014 at 19:12

Actually I have exactly the same problem. Published nodes should not got back to draft for higher editors.
I know, that you can give users permissions to set moderation state on edit page. But for some reason (maybe the are to lazy) they don't like this method. An direct edit method for users with correct permissions would be great.

Comment #3

input commented 15 January 2014 at 21:15

After 3 Beers and fighting through a mix of german and english within rules (i'm german)

Update:

You can achive this by using rules.

Example:

(Be aware of user roles value. I selected 2 with the option not all of them are needed)

{ "rules_bypass_workbench" : {
    "LABEL" : "Bypass Workbench Moderation",
    "PLUGIN" : "reaction rule",
    "OWNER" : "rules",
    "REQUIRES" : [ "workbench_moderation", "rules" ],
    "ON" : { "workbench_moderation_after_moderation_transition" : [] },
    "IF" : [
      { "content_is_using_workbench_moderation" : { "node" : [ "node" ] } },
      { "user_has_role" : {
          "account" : [ "site:current-user" ],
          "roles" : { "value" : { "3" : "3", "4" : "4" } },
          "operation" : "OR"
        }
      },
      { "contents_previous_state" : { "node" : [ "node" ], "moderation_state" : "published" } },
      { "contents_current_state" : { "node" : [ "node" ], "moderation_state" : "draft" } }
    ],
    "DO" : [
      { "workbench_moderation_set_state" : {
          "node" : [ "node" ],
          "moderation_state" : "published",
          "force_transition" : 1
        }
      }
    ]
  }
}

Checked this with several role permissions (creator, controller, master-editor/ admin) and it seems to work so far.
New revision is created and moderation-Tab at least published->draft, draft -> published

Comment #4

robcarr

English

Perthshire, Scotland

commented 28 June 2014 at 14:48

Status:

Active

» Postponed

Input's solution using Rules is an entirely valid approach. I'd agree that not being able to bypass Workbench Moderation is an irritation for the content admins, but this feature is probably not a priority in the WM module right now

Comment #5

input commented 30 June 2014 at 07:44

Btw. after several months of "testing" my solution is still working ;)

But you should tell your editors, that if they want to have an new unpublished draft from an existing node, they should set moderation state inside edit-form manually.

You can even extend this rules setup by using a global Flag.
For example this way you can tag Nodes as "Have to be edited" or "Edit this node and publish it without any further moderation steps". Or make my above example independent from users role, so you can flag a user as master-editor, who has the same rights as other editors, but can edit and publish immediately. ....

I think there are a lot of possibilites using rules and workbench together.