editing unpublished nodes by non-author?
| Project: | Workflow |
| Version: | 6.x-1.0-rc3 |
| Component: | Code |
| Category: | support request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | duplicate |
Jump to:
I am using Drupal 6.5 with Workflow 6.x-1.0-rc3.
I have four states for my Page content type: Draft, Ready to Review, Ready to Publish, Published.
I have three roles: Author, Editor, Publisher.
I wish the Author to be able to create a node (unpublished) and move it to Ready to Review.
I wish the Editor to be able to edit it (still unpublished) and move it to Ready to Publish.
I wish the Publisher to be able to move it (unpublished) to Published (the state change will trigger and action and publish it.
I have set these setting in Workflow/Workflow Access, but if I don't allow the Author permission to "Edit Own Page" in Drupal's main Permissions page, the Author can't edit the page. If I allow the Author permission to "Edit Own Page" he can edit it in any state.
So my question is, how do I permit an author of a node to edit that node in Draft, Ready to Review but no Ready to Publish - all 'unpublished by core' states? The settings in Workflow Access seem to be there, but they seem to be overridden by core permissions. Thanks.
#1
One way to deal with the inability to edit unpublished nodes would be to, using Content Access module, set the node to only be visible by the Author, Editor, and Publisher. When the node is moved by the Author to Ready to Review, a trigger Publishes (using core) the node. It is editable by the Author and Editor, yet it is not viewable by the public. Once set to Ready to Publish, a trigger changes the node's author to the name of the Editor, thus taking editing privileges away from the Author. The Publisher, when ready to publish the node, changes viewing permissions to make it visible to the public.
Quite a nasty hack, but it would work. Any thoughts? Thanks.
#2
Drupal's node access system does not apply to unpublished nodes. workflow_access can do nothing about that. A similar question was discussed in #156028: Workflow nodes must always be published for access controls to apply.
#3
I've done this where nodes are published by default and moved into a "submitted" workflow state (where only editors and publishers can see it) and then a "reviewed" state (where only publishers can see it) and a "published" state (where everyone can see it). It works pretty well, but yes it is not an ideal solution. If only there was a way to give users access to unpublished content without "administer nodes" permission...
#4
Hi all in this thread!
I've been struggling with this too and have used various combinations of existing contributed modules to get it a simple publication workflow to work that includes both unpublished and published content.
To no avail.....
So, I wrote my own: Revisioning.
I'm not promising it will solve all your problems (if it doesn't let me know - haha!), but it may at least alleviate them or entice us to put our collective thinking-caps on.
The above link takes you to a page with further links to 3 progressively more elaborate step-by-step tutorials, that may or may not be of any use to you.
It's only the first version of this module, so let me know where it falls down for you!
Good luck!