Node changes

If you want to keep track of the changes made to a node as comments, you can use this module: http://drupal.org/project/nodechanges

1. Install and enable the module
2. Go to the content type you are interested.
3. On the top, there is a tab "comment fields".
4. Add a new field to the comment (not to the content type)
5. Select field type: Comment diff and widget: Hidden
6. Set the number of values to "unlimited"

Bulk Enable Revisions for all Node Types

This is a utility function which cleans up the variable table, removing entries for node types which no longer exist, and then goes on to set all node types to have revisioning enabled. This code also has a line which disables the default of new nodes to be not Promoted to Front Page , although it is currently commented out. It displays information about what it has done. The first line, a comment, can be used in phpMyAdmin to show what the current settings are for each content type. It is my hope that someday this code might be used as a start for building a full blown module that shows and allows easy editing, and bulk modifications of all settings for all CCK/node types on a site.


function bulk_enable_cck_revisions() {

// select * from variable WHERE name LIKE 'node_options%' # sql to show status of all cck types, use this in phpMyAdmin or similar tool

// first, clean up any old data in the variable table that's not needed any longer.
$result = db_query("select name from variable WHERE name LIKE 'node_options%'"); # quick sql to show status of all cck types
while($name = db_result($result)){
$type = substr($name,13);
$count = db_result(db_query("SELECT COUNT(*) FROM node_type WHERE type = '%s'", $type));
if($count == 0){
drupal_set_message("$type no longer exists. Deleting node_option_$type from variable table");

Revisioning

Follow the seven simple steps below to create a basic content publication workflow that will satisfy most of your requirements for revision moderation, using the Revisioning module. Then, if needed, further enhance content security with fine-grained access control through two more tutorials on publication workflow for categorized content with workflow states.

In this first tutorial we'll keep things simple. We'll present a solution to the following common scenario:

Authors write content that prior to being made publicly visible must be reviewed (and possibly edited) by moderators. Once the moderators have published content, authors should be prevented from modifying it while “live”, but they should be able to submit new revisions to their moderators.

Subscribe with RSS Subscribe to RSS - revision