When content_moderation is installed and several nodes already existed visitors (even anonymous) get the message "The content of this document has not been approved and is therefor not valid yet!" which is confusing since the node content is visible.
Should this also be handled by a permission or just restricted to certain user roles?
Comments
Comment #1
eugenmayer commentedWell actually this is the central functionality of content moderation and the most important one.
That message tells the visitor, that according that content there is no live so no approved version at all. This means, that the current viewed content is possibly faulty and can not be trusted. If you dont like those messages for visitors and you want rather hide those content till those get approved, you might use drafts
Comment #2
broonThis is strongly connected to the wiki behaviour (which this module was originally developed for I understand) so I agree to connect the message to the draft functionality.
But actually I am not against showing the message at all. My point is the (in my opinion) confusing behaviour regarding existing nodes. Let's say we have a drupal system with 10 published nodes. At one point content_moderation is installed. There is no moderation history for the 10 existing nodes (hence there is no "live" version) so the 10 nodes are marked as not verified even though they have been perfect for publishing before.
So maybe a solution here would be to set all existing published nodes into moderation state "live" upon installation of content_moderation?
Regards,
Paul
Comment #3
eugenmayer commentedActually it is not connected to a wiki behavior, but rather to quality managemennt where rules are more strict compare if you use that in a classic CMS case.
The solution you just have chosen is the correct one. Its not right removing the note its right to do what you actually suggest: "Actually those revision are expected to be approved".
Actually iam not sure where to put that functionality. On installation wont work out, as actually you will do so only for the moderated node types.
On activating the moderation on a node type, it should actually only happen once, but maybe even every time?
My idea would be showing a note for the admin when moderation was just activated which shows "when you like to approve and set live all the current revisions of node type XYZ, please click here." The we have a proxy form form confirmation (safety agains CSRF) and we are done.
What do you think?
Comment #4
broonYes, I've been thinking about the correct time to implement this feature. It should require the administrators work (as in deciding whether to update existing nodes or not). I agree with your proposal, it's about what I had in mind.
Comment #5
eugenmayer commentedComment #6
broonComment #7
mkalbere commentedSubscribing !
This module does exactely what I need ! Thanks to the dev !
a mass update in the http://XXX/admin/content/node would also be a very nice feature.
For now, ... sorry I have bad deadline, so I need to moove on . I wrote a quick and dirty workaround for people
It published all nodes that are not " live " using the latest revision.
!!! It has of course ... to be removed once the site goes live
Comment #8
ikeigenwijs commentedSubscribing !
Comment #9
grincon commentedIn case some one needs another quick "activate all option"
I used EXECUTE PHP block and ran this code to activate all nodes of type 'page' that are not live:
Comment #10
eugenmayer commentedThats an interesting feature!. What we need now is to put this functionality behind a form and we are done.