Active
Project:
Revision Moderation
Version:
6.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
8 May 2009 at 03:10 UTC
Updated:
23 Apr 2011 at 05:00 UTC
Per http://drupal.org/node/364458, it appears that this module complements modr8. Does it make sense for these modules to be separate?
If anything, revision moderation functionality appears to be an enhancement of modr8 and doesn't make much sense as an independent module.
Comments
Comment #1
gpk commentedAs I understand it Revision Moderation lets you work on a node without the changes being visible to ordinary site users, per the discussion you reference. I don't think modr8 does that.
Comment #2
dinis commentedBy using views I was able to build two blocks and admin pages which combined the functionality of both this and Modr8 into almost identical looking interfaces for the content admins. Unfortunately, Revision Moderation for Drupal 6 is not yet working with Views, but fingers crossed we'll have that soon.
Drop me a line if you would like the views scripts for Drupal 5.
Comment #3
aren cambre commentedgpk: This is part of why I see the benefit of combining the two modules. Why should modr8 users not have that feature?
Comment #4
j0rd commentedModr8 is only for moderating new nodes. It does not deal with edits/revisions.
Revision Moderation is only for moderating revisions. To my knowledge, it does not deal with moderation approval of "new nodes".
The the functionality of the two modules were integrated, and the UI's unified, it would provide a robust moderation flow for Drupal admins.
Modr8 also provides the the content publishers with some useful email notification when their content is approved or denied. It also allows the moderator to send an email to the user to tell him, to update his content to meet standards before it will be approved. This are useful features, which I don't believe revision moderation has.
If the features of these two modules were unified, it would provide a robust moderation flow which would suffice for most drupal admins I believe.
I support this unification.
Comment #5
kesmeby commentedThis would be awesome. If Revision Moderation could be merged with either Modr8 or Workflow Module it would make either one a lot more useful for large sites where you have many editors but only a few publishers to ensure content integrity. This would be the best way to run any high-quality wiki.
Comment #6
aren cambre commentedI added #463636: Merge modr8 with Revision Moderation to the modr8 queue.
Comment #7
jbrauer commentedCertainly open to additional discussion. In many cases I've worked with sites that used one or the other of these modules and some that use both but it seems far from universal that using one module means the other is needed. When it comes to the email functions resolving the issues with Revision Moderation and workflow/actions/triggers is higher on my list for immediate attention.
Comment #8
eddified commented+1 subscribing
Comment #9
DrupalSza commentedAlso subscribing - I would love to have the UI merged...
Comment #10
alexbovey commented+2 subscribing
Comment #11
jamestombs commentedSubscribing
I see no problem merging the two and allowing the admin to chose whether initial moderation, revision moderation or both are required. The split UI at the moment will cause major confusion to the less IT literate users.
Comment #12
aren cambre commentedDoes maintainer still need more info? Just checking since it's been over a year with this status.
Comment #13
giorgio79 commentedjbrauer the maintainer mentioned that for D7 the way forward will be Workbench Moderation module, so this seems to be a no fix:
#995876: Revision Moderation Drupal 7 port