Surely this module is supposed to stop users from making a post public before an editor has seen it?
Why then, can untick the moderation box during node creation, and totally bypass moderation!!??
What kind of moderation is that, where the can user choose not to be moderated??
Can someone tell me what I'm doing wrong.
Thanks.
Comments
Comment #1
-Anti- commentedAh ok... moderated users aren't supposed to have 'administer node' permission.
But my users NEED the 'administer node' permission so they can set
the parameters: sticky, promoted, published, etc. (and access revisioning?)
But the node still needs to then be moderated!
They should not be able to uncheck the moderation box.
Is there a solution?
Why is the 'moderate' tickbox tied into the 'administer node' permission anyway?
That creates a pretty serious limitation IMO.
Cheers.
Comment #2
-Anti- commentedNo comments?
What about the workflow module?
Is that a suitable alternative to modr8?
Comment #3
pwolanin commentedusers with 'administer nodes' can essentially bypass all other node-related permissions. It's for administrators. Perhaps you shoudl re-think your workflow.
Comment #4
-Anti- commentedThanks for your reply.
However, this is for a school website. The teachers *are* the administrators with regard to deciding what is published, promoted and stickied, adjusting the access permissions with one of the access modules, and accessing revisions. There are several options provided by 'administrate nodes' that they need to use.
But the headmaster himself needs to then moderate all created nodes, at least for a trial period.
Any suggestions on how to achieve this workflow?
Comment #5
-Anti- commentedJust as follow-up, I think this module may help:
http://drupal.org/project/override_node_options
Not tried it yet though.
I depends if it only works with the default publishing options (sticky, promoted, author, etc)
or whether is picks up any additional options put there by third party modules like modr8.
In addition, it looks as though it still has a lot of bugs in the issue queue.
Comment #6
pwolanin commentedComment #7
jahubego commentedComment #8
geekgirlweb commented