Reviewed & tested by the community
Project:
modr8
Version:
7.x-1.x-dev
Component:
Code
Priority:
Minor
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
19 Sep 2008 at 14:10 UTC
Updated:
13 Nov 2018 at 16:56 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
pwolanin commentedPossible yes, but this module doe not currently do that - it's really designed for initial moderation. Many sites would not want their content disappearing out of listing every time it's updated. This project has, unfortunately, not been updated for 6.x yet: http://drupal.org/project/revision_moderation
For more complex moderation scenarios, you might consider the actions with the trigger module (or a custom action/trigger). Actually - a more reasonable feature might be a node action to but it into moderation.
Comment #2
pwolanin commentedhere's a starting patch. Making it configurable would be better, of course.
Comment #3
mukesh.t commentedMy requirement is.. If a user is adding / editing contents in my site, it should not be displayed to any user till its not approved by the administrator.
I am using Modr8 module for the same, but whenever any user is editining the contents, the menu items are getting invisible and they are not visible till administrators is not approving.
But the way I want is it should display the old contents till its not being approved by the administrator.
Is it possible?
Comment #4
pwolanin commentedJust because you want it does not make it critical.
Comment #5
jefftrnr commentedModr8 has several Email settings for sending messages to content authors if their content has been approved/denied. I don't see this feature in the Revision-Moderation module. But Modr8 is missing the use of node-revisions to be able to moderate edited nodes. Any chance these two modules would be combined?
Comment #6
j0rd commentedI would like the functionality of allowing users to edit nodes, and having the revisions put into a moderation queue...while leaving the current node/revision published. Upon approval of the revision, the node gets updated.
This is essentially the functionality revision_moderation provides and is the last step I feel modr8 needs to be a robust solution for Drupal admins. A single UI for moderation is essentially for us admins, should we want to delegate these tasks to less technical users of our websites.
This has been requested in the modr8 and revision moderation issue queues.
Merge Revision Moderation with modr8
Comment #7
betz commentedI also would love this feature.
And a setting to enable/disable this would let people the choice if they need it or not.
Comment #8
mdih commentedsubscribing...
Comment #9
joachim commented> it's really designed for initial moderation
In which case, what's the point of the module at all? You can create that functionality merely by setting a content type to unpublished by default and giving moderators the permission to publish!
This is a bug not a feature request surely, and should be done in hook_nodeapi update rather than requiring further configuration to set up.
Comment #10
joachim commentedPatch on my own SVN, against the current release.
I've tried most combinations I can think of to check this works fine; ideally this module needs tests too ;)
Comment #11
kenorb commentedTrue, what's the point. I installed this module only for that reason.
Tested with latest version, works fine.
Comment #12
rupyjl commentedThe patch worked perfectly for me - thanks a lot.
Comment #13
mathankumarc commentedNew features are going into 7.x
Comment #14
kenorb commented