Put back moderation in core [#118134]

I gather from reading http://drupal.org/node/72343 that this was removed because the setting was handled inconsistently and because it had legacy stuff associated with it (queue.module). However, many, many sites need some form of moderation. Currently modr8 and revision_moderation attempt to provide this, but it's really a core function.

What I would propose is adding it back as follows:

- Content with its "moderated" bit set on is only visible to node admins, and the original author.
- Once a moderated node is published, any further edits go into a "moderated" queue as revisions (unless user has administer nodes privileges or some such, which would bypass this).
- Existing published copy stays current until/unless the new revision is approved.

While it might not serve every use case, it probably serves a bunch of them.

Comments

Comment #1

yched commented 12 February 2007 at 00:03

Oh yes, +1, esp on this item : Existing published copy stays current until/unless the new revision is approved.
This has been a long long discussed and awaited feature in many long threads over the last years, each one emerging form the previous one, and which sort of condensed into revision_moderation.

So, would this mean integrating parts of revision_moderation in core ?

Comment #2

webchick

she/they

English

Vancouver 🇨🇦

commented 12 February 2007 at 00:12

That's my current plan, yes. Though if you have a better implementation, by all means roll a patch. :)

Comment #3

yched commented 12 February 2007 at 09:45

No no, I haven't used it lately, but last time I checked, revision_moderation was pretty neat :-)

Comment #4

webchick

she/they

English

Vancouver 🇨🇦

commented 14 May 2007 at 17:35

Bump. Putting this back on my radar. The "rip revisions out of node module" patch doesn't seem to have much enthusiasm behind it, and the node_access stuff is in flux now w/ the nodeapi op access patch, so private forums are in the air... so I'll make this my project this week. :)

Comment #5

pwolanin commented 15 May 2007 at 02:30

@webchick -not to be contrary (well, ok it is contrary) but why does this need to be in core?

Comment #6

webchick

she/they

English

Vancouver 🇨🇦

commented 15 May 2007 at 03:04

Because it doesn't make any kind of sense that a content management system doesn't offer moderation out of the box. Especially when we have all these powerful features built-in. It's a matter of using them.

Also, more importantly, because I can't be trusted to keep upgrading revision_moderation each release. ;) And although you might be trusted to update modr8 each release, you might also get neck-deep in maintaining outline module and it might fall by the wayside, etc. Contrib shouldn't be the solution for such a vitally important feature. IMO, of course.

Comment #7

pancho

UTC+2 🇪🇺 EU

commented 1 December 2008 at 06:21

Version:	6.x-dev	» 7.x-dev
Component:	node.module	» node system

webchick:
I also think that moderation is a "must-have" feature, thus core-worthy.
If contrib had proven that this is an area in flux, with a lot of activity going on, then leaving it in contrib would be better. But obviously this code is particularly mature and (in combination with revision_moderation) does just what people expect from it.