Publish node when its first "revision" is approved
Todd Nienkerk - December 11, 2008 - 22:22
| Project: | Revision Moderation |
| Version: | 6.x-1.x-dev |
| Component: | Code |
| Category: | feature request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | needs review |
Description
I'm trying to figure out a solution whereby:
- New nodes are unpublished and held for moderation
- Once published, every revision of that node is held for moderation
While this is technically doable by combining Revision Moderation with Modr8, the two moderation systems are located in different places and employ very different user interfaces. It's a confusing situation for a webmaster!
I've been looking into actions and triggers. The actions supplied by Revision Moderation are almost perfect, except that this module doesn't set the node to publish when its first "revision" -- really the initial creation of the node -- is approved. This means a node stays unpublished after its revision is approved.
There are two possible solutions to this conundrum:
- The Revision Moderation module publishes nodes as revisions are approved. (Perhaps this could be a toggled behavior?)
- Create a new trigger -- "revision is approved" -- that would allow users to create a trigger that would publish the node.
#1
Sorry -- solution #2 has its terminology confused. What I meant to say was:
#2
Here's a patch for solution #2 above. Hopefully it's not embarrassing, as the documentation on actions/triggers/hooks is tough to follow.
This patch supplies a new trigger ("Moderated revision is published") to which one can apply the "Publish post" action supplied by node.module.
UPDATE: I should note that through the use of this new trigger, one no longer needs to use Modr8 to initially approve a new node.
#3
It appears this patch was applied prior to the alpha release. I'll leave this open for verification.
#4
subscribing.
I am also looking for a nice solution to moderation of original and subsequent revisions, I think this could be it.
btw, are there any other e solutions suggested?
thanks
R
P.S. would this patch become part of the revision moderation module or stay as a patch? I would of course prefer for it to be included. Currently we are completing moderation through publication checkbox, which isn't ideal as once it is published the original poster needs to be able to edit their post, but there are not any safeguards on this. It would be nice if revision moderation also didn't rely on the published check-box as I can see use-cases for unpublishing content. (We have a simple view created for all un-published content so moderators know what to work on).
#5
@richard.e.morton: The patch is included in the latest alpha release (see my comment #3). However, it's causing at least one problem I've come across: #392234: New nodes not held for moderation with trigger enabled