Hi,

is it possible for an existing node to go into the moderation queue when someone is editing it?

Currently only a newly created node shows up in the moderation queue.

Or am I missing something?

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

pwolanin’s picture

Possible 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.

pwolanin’s picture

Status: Active » Needs review
FileSize
1.81 KB

here's a starting patch. Making it configurable would be better, of course.

mukesh.t’s picture

Priority: Normal » Critical

My 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?

pwolanin’s picture

Priority: Critical » Normal

Just because you want it does not make it critical.

jefftrnr’s picture

Modr8 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?

j0rd’s picture

I 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

betz’s picture

I also would love this feature.
And a setting to enable/disable this would let people the choice if they need it or not.

mdih’s picture

subscribing...

joachim’s picture

Status: Needs review » Needs work

> 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.

joachim’s picture

Category: feature » bug
Status: Needs work » Needs review
FileSize
934 bytes

Patch 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 ;)

kenorb’s picture

Status: Needs review » Reviewed & tested by the community

True, what's the point. I installed this module only for that reason.
Tested with latest version, works fine.

rupyjl’s picture

The patch worked perfectly for me - thanks a lot.

mathankumarc’s picture

Version: 6.x-1.x-dev » 7.x-1.x-dev

New features are going into 7.x

kenorb’s picture

Priority: Normal » Minor
Issue summary: View changes