Active
Project:
Revisioning
Version:
7.x-1.0-alpha1
Component:
User interface
Priority:
Normal
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
23 Jan 2017 at 17:02 UTC
Updated:
24 Jan 2017 at 22:15 UTC
Jump to comment: Most recent
Comments
Comment #2
rdeboerHi Sylvain
Give them the permission to publish, after you've done that first review.That should do it.
Rik
Comment #3
svanou commentedHi Rik !
Thanks a lot for your answer! I'm not sure to fully understand you point.
Should it be under admin/people/permissions > Publish revisions of own content ? That would not allow my users to publish on the first time yes ?
Thanks ! Sylvain
Comment #4
rdeboerOops.. still have sleep in my eyes. Brain not functioning.
You need a per-user solution. What I suggested is a per-role solution.
So won't work.
No the module doesn't support your scenario out of the box. You'll have to write a patch for it to do that.
Sorry.
Comment #5
svanou commentedHi Rik! Thanks a lot :)
Actually i'm fine with doing a per-role solution. Let me explain again to be sure: I want to be able to moderate content when a registered user submit a new node and then if the node is "live" they should be able to modify the same content without moderation.
Comment #6
svanou commentedHi Rik !
Let me know if you need further clarifications. Thanks again! Sylvain
Comment #7
rdeboer@svanou
You'd create (or re-used) a content type for which the Published tick box is UNTICKED.
Your user would be able to create content of that type but it would not be published.
You as a moderator would assess that content, change it if necessary and then publish it (ticking the Published box on that content, prior to saving it).
Then the user can modify it from there on.
You would have to set up permissions for this user role and for the moderator role.