Setting Roles For Writers, Editors & Publishers

You'll probably need to use the workflow module to do what you want. Lullabot recently did a screencast on how to use actions and workflow together (I haven't had a chance to watch it yet). Maybe you can skim something useful from that.

This is something you might be able to accomplish using the simple access, actions, and workflow modules.

Cheers,

Bill

-------
http://www.funnymonkey.com
Tools for Teachers

I am also looking at doing exacly the same thing, so far no success though.

I'm guessring the workflow module will need some kind of "inbox" where user tasks are put to be completed. Once one of the users with the role X has performed this task, then the task is deleted from their "inbox". This task item could contain a link to the node to be reviewed/approved/published.

If anyone finds out how to do this, it would be great!

I'll keep you up to date on my findings...

I produced a solution for a writer/editor workflow and want to share it. It's complicated, so the explanation below may be missing some parts. This assumes you're familiar with the actions and workflow modules, as well as coding a Drupal module. Anyway, here it goes:

I set up a new content type with CCK. Let's call it an article.

I then set up 2 roles under administer/access control/roles: writer and editor. Writers will write articles and submit them for editorial review. Editors will edit articles and publish to the website. Under administer/access control, allow the writer role to create new articles but not edit their own.

I installed the simple_access, actions and workflow modules. These modules. along with some code in a custom module, helped get the job done.

First, I set up simple access. Create an editor group and assign the editor access role to this group. Also, set up simple access to display view, edit and delete selections if a user has the "assign access to nodes" access rights. Finally, go to access control and give the editor role this right.

Now, set up a workflow that is similar to the example workflow given in the workflow.module readme file. This workflow basically allows 3 states: creation, Draft and Approved. Set up the workflow so that authors move the workflow from creation to Draft and editors move the workflow from Draft to Approved. Don't give anyone rights to move from Approved to Draft. Allow the editor user role to see the workflow tab, under Workflow Tab Permissions. Finally, assign the workflow to your article node type.

Now, create a custom module in the usual way. Add the function to send email to a role group, as outlined here: http://drupal.org/node/48738. This will allow editors to receive notification of a new article. Then, add 2 more functions, one which will assist in allowing editors to edit an article, and one which will allow everyone to see the article after it is approved:

function action_change_simple_access_so_editors_can_edit($op, $edit = array(), $node) {
switch($op) {
  case 'metadata':
    return array(
      'description' => t('Change Simple Access so editors can edit'),
      'type' => t('Simple Access'),
      'batchable' => false,
      'configurable' => true,
    );

  case 'do':
    db_query('DELETE FROM {node_access} WHERE nid = %d AND realm = \'simple_access\'', $node->nid);
    db_query("INSERT INTO {node_access} (nid, gid, realm, grant_view, grant_update, grant_delete) VALUES (%d, %d, 'simple_access', %d, %d, %d)", $node->nid, 2, 1, 1, 1);

    break;

  case 'form':
    return array();

  case 'validate':
    return true;

  case 'submit':
    return array();

  }
}

function action_change_simple_access_so_everyone_can_see($op, $edit = array(), $node) {
switch($op) {
  case 'metadata':
    return array(
      'description' => t('Change Simple Access so everyone can see'),
      'type' => t('Simple Access'),
      'batchable' => false,
      'configurable' => true,
    );

  case 'do':
    db_query('DELETE FROM {node_access} WHERE nid = %d AND realm = \'simple_access\'', $node->nid);
    db_query("INSERT INTO {node_access} (nid, gid, realm, grant_view, grant_update, grant_delete) VALUES (%d, %d, 'simple_access', %d, %d, %d)", $node->nid, 0, 1, 0, 0);
    db_query("INSERT INTO {node_access} (nid, gid, realm, grant_view, grant_update, grant_delete) VALUES (%d, %d, 'simple_access', %d, %d, %d)", $node->nid, 2, 0, 1, 1);

    break;

  case 'form':
    return array();

  case 'validate':
    return true;

  case 'submit':
    return array();

  }
}

NOTE: In the code above, the gid value for the INSERT statements must be the same as your simple access editor group ID.

Save it, enable the module.

Now go to administer/actions. Add a new action to email the editors user role group. Also, add new actions for the newly added code from above. Once you've added all 3 actions, go to workflow, then actions. For the transition of creation to Draft, add the actions for emailing the editors and for changing the Simple Access so editors can edit. For the tranisiton of Draft to Approved, add the action to change Simple Access so everyone can see.

Now, try it out. A user in the writer role can create a new article and simply submit it. This sends an email to the editorial group, notifying them of the new node. The article is not accessible by anyone other than the editors at this point. An editor can then login, go to that node, edit it if necessary, then transition it from Draft to Approved. Once Approved, the node is available to all users.

I've been looking at this stuff for hours, so there's a good chance I forgot something here. If I did, let me know.