Active
Project:
Workbench Moderation
Version:
7.x-1.1
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
21 Feb 2012 at 10:07 UTC
Updated:
23 Jun 2013 at 14:56 UTC
Jump to comment: Most recent file
Comments
Comment #1
hyperglide commentedOpened an issue in the view_unpublished queue #1733844: Using the view_unpublished module with WorkbenchModeration
help pls.
Comment #2
jyraya commentedI would like to add a point here. why an editor could only view an unpublished content?
If this one has the permission "Edit any [content_type] content" added to "View all unpublished content", could he not access the content in "edit" mode too?
Or maybe, in order to cover all cases, I would be interesting to have the following permission:
What do you think about that?
Comment #3
hyperglide commentedjyraya -- Both of your points would work for our use case. However I would still lean towards the permission in the initial post.
Thanks!
harley
Comment #4
wickwood commentedFor our use case, being able to set a permission of "View [Content Type] Unpublished Content" would be best. We have several content types and editors dedicated to each of them, but those editors should not be able to view the unpublished content for content types they are not able to moderate.
I'm currently looking for an answer to this because it causes a great deal of confusion in our use case.
Thanks in advance for any assistance!
Steve
Comment #5
hyperglide commented@wickwood - At this time I am not aware of any way to accomplish this. A new patch is required, if you can help write. I can assist in testing.
Comment #6
wickwood commentedOK, I created a patch yesterday and it works for me. I don't have a lot of experience actually generating patch files, so hopefully this will also work for you.
The new permissions are for admins/moderators to view all unpublished content of a certain type. I did not restrict this to having $conf['workbench_moderation_per_node_type'] = TRUE because I thought having this set of permissions may be more common than having to workflow permissions per content type. But they may always go together.
The better way to handle both of these issues may be to have the options to turn them on and off with admin UI.
Anyway, let me know what you think.
Steve
Comment #7
wickwood commentedAlso, I don't know anything yet about running tests on patches.