if you edit a page with activated "moderation queue" the node gets completely hidden.
This is good in general BUT
I think that the old version of this node should be shown until someone approves the new version.
Examples:
-----------
#1 Without this someone could go through all drupal.org/handbooks-pages "edit" them with just a single click at save
And what happens then?
We dont have anymore even one help page.
Do you want this?
I think not
#2 I want that my employees could edit the pages. But I want to approve their changes after I read though them.
They click at "edit" change for example a typo and click then at "save".
The whole site is hidden from now on.
(For example kitt's last change at 07. Create a module configuration (settings) page - he appended the '0' at the title so that all the related nodes get sorted the right way - please look at Creating modules - a tutorial is this tutorial usefull now? the visitor sees just a destroyed area)
Could someone with enough knowledge of the revisions-system look at this?
Thanks
Tobias
ps. does "Approve the selected posts" at admin/node work?
at my system it does not...
it would be nice to have a button at the node itself (under this message) which let me approve the post.
Comments
Comment #1
eaton commentedI agree wholeheartedly -- easy to say since I'm not posting any code, naturally.. heh.. But the ability for individual revisions to enter moderation would be a HUGE boon.
Comment #2
Tobias Maier commentedIt's not just a huge boon. It's needed because without this this feature is more harmfull than usefull...
Comment #3
janekb commentedFor me it's a feature request not a bug report. Drupal can still be released without it, although for me it's also very usefull.
Comment #4
beginner commentedComment #5
LAsan commentedFeature request moving to cvs.
Comment #6
mdupontModeration has been removed from Drupal core. Closing the issue. The contrib module Revisioning does just that, though.