Hopefully, I can explain this correctly.

We need to implement a content approval process and I thought there was a module to manage this (or maybe it's already available in Drupal core), but haven't been able to locate it.

Client wants content to go through an approval process before being published (i.e., made live).

We would like to create at least 3 administrative roles, like Content Editors, Content Publishers and Super Admins.

Content Editors can edit content, but not publish it. Content Publishers can edit and publish content (which includes approving/rejecting any changes made Content Editors). Super Admins would have access to everything in Drupal.

Any help is appreciated.

Thanks,

Teddy

Comments

This seems so simple, yet I am not able to find it either.

I tried the combination of trigger + actions + workflow + workflow_ng + token ... but it is simply not working

All there needs to be is:

1) user submits node -- email [with link to node] sent to editor
2) editor reviews -- email sent to manager to approve [with direct link]
3) manager approves [node gets published]

I know it sounds simple... but it probably isn't.
Please tell me or guide me which module combination is the correct one.

Thanks so much.

-
I do not see things the way they are - I see them the way I am

-
I do not see things the way they are - I see them the way I am

We're looking for something similar, especially if the approval for content (not just comments moderation) is dictated by a role permission. The workflows module might suffice to do what you want, but for us is overly complex.

Someone at Oregon State Univ has this figured, going by their help documentation...
http://oregonstate.edu/webprojects/drupal/using-approval-queue
I can't see "approval queue" as a module anywhere, but maybe OSU developed it in-house (CCK? with reference to the publish/don't publish check box process available by default)

Cheers
S

"I make solutions that nobody wants to problems that don't exist" -Alvin Lustig

Si

"I make solutions that nobody wants to problems that don't exist" -Alvin Lustig

I'm using Drupal 5.x and use revision moderation to accomplish this. As an editor makes a change and submits it, it goes to a pending status for review by an publisher. The old page is still displayed on the website until the new revision is approved. You do not want to have the page go to an unpublished state, because that would break any links to that page until it was published again. I found revision moderation (project/revision_moderation) to be the best solution for this. It is very nice too, that it keeps a list of revisions and you can revert back to a previous version based on your permissions (very good, because people sometimes to make mistakes that a publisher would not know about).

- Shane

same problem:(
http://drupal.org/node/229887#comment-1042611
tried a lot of posting but none what so ever helped
i think its time to write a module for drupal for the first time :(

I would say revision_moderation accomplishes this. Instead of writing a module, you may want to see about joining the project and then just adding additional functionality into it. Don't reinvent the wheel, just make it better.

- Shane

> We need to implement a content approval process and I thought there was a module to
> manage this (or maybe it's already available in Drupal core), but haven't been able to locate it.

I thought that's what workflow does?
http://drupal.org/project/workflow

Everything I say is opinion, even if interpreted as fact.
Sometimes I may be inaccurate or *GASP* wrong!
Sometimes I attack Drupal due to frustration. Get over it.

There's a tutorial for setting up a content reviewing system with Workflow-ng 2.0 here: http://drupal.org/node/156317#comment-769331

- Vivian