Assign additional people to Revision Moderation
shane_jordan - February 14, 2008 - 17:12
| Project: | Revision Moderation |
| Version: | 6.x-1.0-alpha1 |
| Component: | User interface |
| Category: | support request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed |
Description
How do you allow more than just the administrator to view the items that are in a revision status? More than viewing, I would like them to be able to publish items that are in the revision status. Based on the user's role, allow them to publish items.
Thank you,
Shane
#1
I believe it bases it off "revert revisions" permissions from node module.
#2
#3
#4
Now, using the drupal 6.10, I would like to know which are the minimal permissions which should be given to a user to be able to moderate revisions.
I made some tests with Masquerade 6.x-1.1 and the role I use for modr8 6.x-1.1, I added the following permissions :
* revert revisions
* view revisions
This way the minimal permissions user can view revisions but not the revisions bloc, he can also not moderate revision.
Which are the minimal permissions what I have to give to him to be able to view the bloc and moderate the revisions ?
Should I give :
* edit own X content, where X is all concerned content types,
* revert revisions,
* manage nodes (node admin, appeare translated to me),
* create X content ?
#5
i believe that "administer nodes" is the key permission for making this work.
#6
I am a bit surprised because "administer nodes" seems to me a bit too much for just accepting revisions.
#7
The block requires "administer nodes" permission to view the block.
#8
People with "administer nodes" permission can do everything on nodes, so it is natural they can also moderate revision.
But then I began to use the modr8 module to moderate node, it appeared to as a delegation tool. I can delegate the moderation to people who have no special permission but modr8 permission. This is a tool which allows me to let more people participate and take responsibililties in the web site, with a small number of administrators with "administer nodes" permission.
After begining to use modr8, I came to the conclusion that revision have also to be moderated. But now I realize, they work very differently and are almost uncompatible in usage.
On the contrary of modr8, I perceive the Revision Moderation module as giving more work to a small number of administrators as I would not like to give "administer nodes" permission to a large number of people.
#9
Automatically closed -- issue fixed for 2 weeks with no activity.
#10
The problem is probably that there isn't a permission to 'publish revisions' etc - if so, this issue should be marked as a duplicate of #387728: Add permissions, modify how permissions are used, and allow editing of revisions without them becoming live
If not (i think this issue is slightly less invasive - whether it goes far enough I'm not sure), we don't want to show nodes the user can't access in the list of pending revisions. But - until there are a different set of permissions (and not sure the maintainer wants this?) - there's not much reason to hide the block from users who already have permission to edit and publish at least one pending revision. Do you think?
So I just checked to make sure the user has 'view revisions' (rather than 'administer nodes') permission to display the block, then check revision_moderation_admin_perm() for each node in revision (to see if they should be listed). If there are no items in the list already editable/publishable by the user, display 'No pending revisions found'. Then we only need to make sure user has 'administer nodes' perm before displaying the 'View all pending revisions link.
What do you think? (patch attached)
Edit: forgot to add last check to this patch - see next one
#11
This one check that user has 'administer nodes' perm before displaying the 'View all pending revisions link.