Needs work
Project:
Workbench Moderation
Version:
7.x-1.x-dev
Component:
Miscellaneous
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
11 Nov 2011 at 14:05 UTC
Updated:
18 Sep 2020 at 06:23 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
stevectorI suggest you give the first role permission to go from "draft" to "needs review." This role should not have permission to make things published.
The second role could transition from "draft" straight to "published."
Please re-open if I have misunderstood.
Comment #2
Anonymous (not verified) commentedI have a similar situation (Rules is involved, though).
My solution is to add a rule, to set content to "published", if it's from a certain role and in the moment when it transits to "needs review".
@stevector, adding transitions for my understanding still means to transit manually and - in case of rules changing the content implicitely - is not possible, because the content status will flip back to "draft" or "needs review" automatically.
As an example, the rule would look like:
The rule invokes a conditional Rules component component_rules_util_user_is_moderator_or_admin to restrict it to mods and admins.
Comment #3
anybody*reopening*:
I just found this issue because I was asking myself the same question as @k_zoltan. The permission "Bypass workbench moderation" can be understood that way that content created by a user with this permission is AUTOMATICALLY being published without further moderation.
Such a behaviour is for example implemented in modr8.module and makes a lot of sense to me. In most cases users with that permission don't need or want an extra step to publish their own content (bad workflow).
So I'll change this into a feature request to provide an option to auto-publish moderated content created by a user with the bypass permission.
Please think about it a bit.
Of course a workaround is possible using rules (in my case I used Rules Bonus to get the "user has permission" condition and check for the bypass permission, which is even a bit cleaner to me than to check for a role as described in #2.
Anyway I think an out-of-the-box solution is very very useful here. That way this permission really starts making sense to me.
Thanks a lot.
Comment #4
joachim commented> The permission "Bypass workbench moderation" can be understood that way that content created by a user with this permission is AUTOMATICALLY being published without further moderation.
That is how I understood it too.
It would be really useful to have this functionality, possibly as a new permission. As a developer, I frequently make test edits to nodes that I want to see live immediately, and I keep forgetting to change the publication status when I save the form!
Comment #5
joachim commentedHere's a patch.
This saves an awful lot of clicking when editing test nodes during development!
Comment #7
pbcelery commented+ for feature request.
Our site "managers" and "editors" do not want to create drafts, then go through a second publish step. We use moderation so they can approve others' posts. Making them approve their own posts adds to the confusion adopting Drupal.
Did this patch really fail? It looks like a good solution.
Comment #8
joachim commentedI expect it's because some of the tests need to be tweaked to account for the new behaviour this patch adds.
Comment #9
anybodyYes you're right. We need separate tests for this permission and the old tests have to be run for a user without this permission.
Comment #10
aseabrook commentedFrom a UX point of view, it makes sense to make this feature a part of Workbench Moderation. I want to apply this patch but I'd rather wait until this feature gets rolled out in the next release. Any chance of that happening?
Let me know if there is anything I can do to help.
Thanks
Comment #11
bbcPatch #5 works well for me. Thanks!
Comment #12
plato1123 commentedJust curious if this patch ever made it into a release?