Last updated 14 December 2015. Created on 20 March 2009.
Edited by cedewey, iantresman, realityloop, Amir Simantov. Log in to edit this page.

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.

What the radio buttons mean:
Modify current revision, no moderation = Publish immediately to the existing revision
Create new revision, no moderation = Publish immediately in a new revision
Create new revision and moderate = Unpublished until approved by moderator

Begin by logging in to your Drupal site as an administrator.

Jump to D7 Instructions

Instructions for D6

  1. Install Module Grants and Revisioning as per their README instructions. If you want to compare revisions and highlight the differences, also install the Diff module.
  2. Although you do not have to enable the main Module Grants module, it is encouraged that you do, for the reasons given on the Revisioning module home page in the section on "Dependencies". However the submodule Node tools, part of the same Module Grants package, is required for Revisioning.
  3. To view revisioned content you have a couple of handy options at your disposal. When you enable Module Grants Monitor a menu option Accessible content will appear in your navigation menu. Role-based access to its various content filtering tabs can be set at User management >> Permissions. When Revisioning is loaded there's an additional useful tab: In draft/Pending moderation. The tab lists all nodes that have revisions more recent than the one currently visible to the public.

    Alternatively, or in addition to the above, installation of Views will give you a Content summary view of all content on your site. You can use this view as is, or you can customize it to suit your needs.

  4. You can also configure as a block a cut-down version of the In draft/Pending moderation tab on the Accessible content. This is particularly handy for moderators as the block gets automatically updated with every browser click, so will always display an up to date summary of submitted content requiring review and publication.

    You configure the pending revisions block just like any other block at Administer >>Site building>>Blocks. Configure it so that only the Moderator role may see it. The block doesn't appear until at least one revision has been created on your site. We'll do this further down this page.

  5. Under Administer >> Content management >> Content types, click edit next to the content types (Page, Story... etc.) for which you wish to enable/disable revisioning. Under Workflow settings, "Default Options", tick both the "Create new revision" and "New revisions in draft, pending moderation" boxes. Also in this section untick "Published", as we don't want content to be public immediately after creation. Press “Save content type”.
  6. Navigate to User management>>Roles to create an Author role and a Moderator role.
  7. Under User management>>Permissions assign permission as follows.
    Make sure that “access content” (node module section) has defaulted to anonymous and authenticated users. Switch off “administer nodes” for Author and Moderator (or perhaps all roles) as this gives these roles unrestricted access to all nodes, which defeats our purpose.

    Essential: for the Author role tick "view revisions of own/any type content" for the content type(s) that are subject to moderation, i.e. the content types for which "New revisions in draft, pending moderation" was ticked in step 5. Note: you may use "view revisions" (node module section) instead, just be aware that "view revisions" applies across all content types, thus overriding the fine-grained versions of the revisioning section. Make sure none of the "view revisions..." permissions are ticked for the anonymous user.

    • Give the Author role “create content” and “edit own content” permissions for the desired content types. In the revisioning module section tick the "edit content revisions" permission for Author and Moderator.
    • Give the Moderator the "edit any type content“, "revert revisions”, "view revisions" (or "view revisions of any type content"), “publish revisions”, “unpublish current revision” and "view revision status messages" permissions.
    • You may not want to give any role the “delete revisions” permission, so that a full audit trail is always kept, in that content may be unpublished (removed from public view), but not removed from the database.
    • Finally, under the module_grants and revisioning sections assign permissions to access the content filtering tabs as you see fit. Note that these do not affect access themselves, just permission to use the filtering tabs. The Moderator role would normally have at least "access I Can View", "access I Can Edit", "access All" and "access Pending tab", while for other authenticated users "access I Can View" and "access All" may be sufficient.

    Press “Save permissions”.

  8. Create at least one user in the Author role and one in the Moderator role: User management>>Users>>Add user.

That's it. To see if it all works, log in as an Author and Create content, Maybe create a Story, provided you enabled it for moderation in step 5, as a Story goes straight to the front page so can be easily verified. Save. Log out and notice that the new unpublished content isn't visible to the public (anonymous users), yet.

Then log in as a moderator to inspect the revised content queue via the Accessible content>>In draft/Pending moderation tab and/or the "Pending revisions" block, which should now automatically appear. Click on the title of the content and then on the next page, pick the desired (i.e. only) revision by clicking on its saved date. The page that appears next displays the yet unpublished content prepared by the author. Above the content you'll find edit and publish links. Click the publish link and on the next page confirm. Log out to see the now public content.

Log in as an author again, press Accessible content, select the recently created Story and click the Edit tab. You will find that after you (the author) has saved the new revision, the version visible to the public (the current revision) remains unchanged.

Log in as a Moderator once more, select the revised content (pending revision), edit it if you wish and Publish this for all to see. Note that the current revision has now become 'archived' and when you select it you'll find a link to revert to it.

Unpublish?

In most revision moderation scenarios content does not often get unpublished. Rather a different revision (old or recently modified) is made current, while the previous revision is auto-archived.

To remove content (current and all revisions) from public view without deleting it) you have to unpublish the node. You can do this by unticking the appropriate box on the content editing form. It requires the role to have the "administer nodes" permission, which unfortunately also lets the user view, edit and delete any content, a privilege that would obliterate all our good work. For this reason the Revisioning module comes with the "unpublish current revision" permission and link, so that you don't have to give any role the "administer nodes" permission.

Auto-notification of authors upon publication

Taking advantage of the pre-defined triggers of the Revisioning module and the various tokens of the Token Actions module, it is easy to have the system automatically send an email to the author of a revision when a moderator publishes, reverts or unpublishes it.

Make sure that the core Trigger module is enabled on the Administer>>Site building>>Modules page. Then select an advanced action from the drop-down at Site configuration>>Actions, e.g. "Send tokenized e-mail", and configure it. A full list of all tokens available to you (given the modules you've enabled) appears when you click Placeholder tokens at the bottom of the page. Put the [revision-author-mail] token in the recipient field and something like "Your content [revision-title]" in the subject. The body of the email message might look like this:

    Hello [revision-author-name], 

    Moderator [user-name] has just approved and published revision #[vid] 
    of your [type-name] titled "[revision-title]", found at [menu]: [menupath].

    Please email [user-name] ([user-mail]), for further information about this
    publication.

    Regards,

    [site-name] [site-url] [site-slogan]
    [site-date]

Finally, attach your action to the relevant trigger (Site building>>Triggers>>Revisioning).
Now publish a node. The author of the node should get an email. If this doesn't happen, check the logs at Administer>>Reports>>Recent log entries.

Note: should the message "No available actions for this trigger" appear on the Triggers page, install the Trigger Unlock module.

What's still missing?

  • In this simple set-up all authors can view each other's content; when you have many authors producing lots of content this may not be good enough and you may want to assign categories to both content and author roles, so that only “sports authors” have access to “sports” content.
    See Revisioning for categorized content (for D6).
  • Although Authors can't publish content, they can still edit it after they've saved it, placing it in the care of the moderator for review; conversely a Moderator may (accidently) publish a revision before the Author was done with it. This is because we don't have a separation by content states (“with author”, “with moderator”). This is where the Workflow module comes in. See Revisioning with state-based content access control (for D6).

Instructions for D7

  1. Install
    Revisioning as any other module. If you want to compare revisions and highlight the differences, also install the Diff module.
  2. For a handy summary of your revisioned content install and enable Views. This should instantly give you a ready-to-use canned view at /content-summary, in your navigation menu. When you visit Structure>>Views page, you'll find details of this revisioning_content_summary view, which you may leave as is or customize to suit your needs. For instance you can move it to another menu, drop or add columns, etc.
  3. In addition, you may configure the "pending revisions" block as a supplementary content summary. This block is particularly handy for moderators, as it updates automatically with every browser click, so it will always display an up-to-date summary of recently submitted content requiring review and publication.
    Configure the pending revisions block just like any other block at Structure >>Blocks. Using the Roles link/tab under "Visibility settings" you would normally configure this block so that only the Moderator role may see it. Details of role assignment follow below. The block doesn't appear until at least one revision has been created on your site. We'll do this further down this page.
  4. Under Structure>>Content types, click edit next to the content types (Basic page, Article, etc.) for which you wish to enable/disable revisioning. Under Publishing options, "Default Options", tick both the "Create new revision" and "New revisions in draft, pending moderation" boxes. Also in this section untick "Published", as we don't want content to be public immediately after creation. Press “Save content type”.
  5. Navigate to People>>Permissions>>Roles to create an Author role and a Moderator role.
  6. Under People>>Permissions>>Permissions assign permissions as follows:
    • In the Node module section, switch off "Bypass content access control" for Author and Moderator (or even all roles) as this permission provides almost unrestricted access to all nodes, which defeats our purpose. The "Administer content" permission is less far-reaching in D7 than it was in D6. If you want your moderators to be able to opt in/out of moderation on an ad hoc basis, then you may grant "Administer content" to the moderator role. See the section Opt in/Opt out details.
    • The anonymous user should only have the “View published content” permission.
    • Give the Author role “Content type: Create new content” and “Content type: Edit own content” permissions for the desired content types. Also "View own unpublished content".
    • Give the Moderator the "View content revisions" (or "Content type: View revisions of any content"), "Revert content revisions”, and "Content type: Edit any content“ permissions.
    • In the Revisioning section tick the "Edit content revisions" permission for Author and Moderator.
    • For the Author role tick "Content type: View revisions of own/anyone's content" (Revisioning section) for the content types that are subject to moderation, i.e. the content types for which "New revisions in draft, pending moderation" was ticked. Note: you may use "View content revisions" (Node module section) instead, just be aware that "View content revisions" applies across all content types, thus overriding the fine-grained versions of the revisioning section.
    • Give the Moderator the "View revision status messages", “Publish content revisions (of anyone's content)”, and “Unpublish current revision (of anyone's content)” permissions.
    • Make sure none of the "Content type: View revisions of..." permissions are ticked for the anonymous user.
  7. Consider not giving any role the “Delete content revisions” permission, so that a full audit trail is always kept, in that content may be unpublished (removed from public view) but not removed from the database.
  8. Press “Save permissions”.
  9. Create at least one user in the Author role and one in the Moderator role: People>>List>>Add user.
  10. At Configuration >> Text formats make sure that the roles just created can use the text input formats you want them to use. For instance "Full HTML" or "Filtered HTML" only.

That's it. To see if it all works, log in as an Author and Add content, Maybe create an Article, provided you enabled it for moderation, as an Article goes straight to the front page so can be easily verified. Save. Log out and notice that the new unpublished content isn't visible to the public (anonymous users) yet.

Then log in as a Moderator to inspect the revised content queue via the "Pending revisions" block, which should now automatically appear. Click on the title of the content and then on the next page, pick the desired (i.e. only) revision by clicking on its saved date. The page that appears next displays the yet unpublished content prepared by the author. Above the content you'll find edit and publish links. Click the publish link and on the next page confirm. Log out to see the now public content.

Log in as an author again, select the recently created Article from /content-summary and click the Edit tab. You will find that after you (the author) has saved the new revision, the version visible to the public (the current revision) remains unchanged.

Log in as a Moderator once more. After clicking the title of the content in the "Pending revisions" block, you'll find that the content now has two revision. Select the pending (i.e. recently revised) revision, edit it if you wish and Publish this for all to see. Note that the current revision has now become 'archived'. When you select it you'll find a link to revert to it, if necessary.

Revisioning has a number of additional configuration options. You'll find them in two places. Firstly on the Configuration page, under the Content authoring section, secondly for each of the content types at Structure>>Content types>>edit, Publishing options, "Create new revision" fieldset. They're all self-explanatory. Have a look and see if any apply to your use-case.

Tip: a quick way to make the /content-summary view appear in the admin, rather than the public theme is to change in the Views UI the URL to /admin/content-summary. Or use the handy Page theme module.

Opt in/Opt out

With the "Administer content" permission being less far-reaching in D7 than "administer nodes" was in D6, you can now confidently give selected roles the permission to opt-in or opt-out of content moderation on a per-edit basis. So, for instance, if at Structure >> Content types >> edit the content type Article has not been configured to be subject to moderation by default, then the roles with the "Administer content" permission may, at any point, decide to switch moderation on, simply by pushing a radio button on the Article content edit form.

Unpublish?

In most revision moderation scenarios content does not often get unpublished. Rather a different revision is made current while the previous revisions is auto-archived.

To remove a piece of content (current and all revisions) from public view without deleting it, you have to unpublish the node. You can do this by unticking the appropriate box on the content editing form. This requires the role to have the "Administer content" permission, which also grants access to a few more options. If you don't want to do this, give the role the more fine-grained "Unpublish current revision" permission instead. Content may then be unpublished from the Revisions tab that sits next to the View tab.

Auto-notification of authors upon publication

Taking advantage of the pre-defined triggers of the Revisioning module and the various tokens of core, it is easy to have the system automatically send an email to the author of a revision when a moderator publishes, reverts or unpublishes it.

Make sure that the core Trigger module is enabled on the Structure>>Modules page. Then select an advanced action from the drop-down at Configuration>>Actions, e.g. "Send e-mail...", and configure it. A full list of all tokens available to you (given the modules you've enabled) will be available at the bottom of your action configuration page, provided you have also installed and enabled the Token module. This module also provides additional tokens, such as [content-type:name], not available in core.

Put the [revision:author:mail] token in the recipient field and something like "Your content [revision:title]" in the subject. The body of the email message might look like this:

    Hello [revision:author:name], 

    Moderator [user:name] has just approved and published revision #[revision:vid] 
    of your [node:type] titled "[revision:title]", found at [node:url].

    Please email [user:name] ([user:mail]), for further information about this
    publication.

    Regards,

    [site:name] [site:url] [site:slogan]
    [date:medium]

Finally, attach your action to the relevant trigger (Structure>>Triggers>>Revisioning).
Now publish a node. The author of the node should get an email. If this doesn't happen, check the logs at Reports>>Recent log entries.

Looking for support? Visit the Drupal.org forums, or join #drupal-support in IRC.

Comments

lancsDavid’s picture

Finally, under the module_grants and revisioning sections assign permissions to access the content filtering tabs as you see fit. The Moderator role would normally have most of these tab permissions, in particular the "access 'Pending' tab"

i'd appreciate some additional guidance here. specifically, what content filtering tabs would - typically - be granted to different roles & why

where i'm at: i've gone through the tutorial & enabled most of the tabs for both moderator & author (because i didn't know what else to do), but having done that there seems to be an awful lot of tabs & its more than a little confusing what they all mean.

for the Moderator - who I've enabled all the tabs for - i've got 8 of them (with Revisioning, Module Grants & Diff modules installed, as per the tutorial)...

TOP ROW >> "I created" | "I last modified" | "I can edit" | "I can view"
BOTTOM ROW >> "in draft / pending publication" | "Published" | "Unpublished" | "All"

not knowing much about publication workflows (as a subject) i don't know if its being unreasonable to expect there to be less tabs in the interface. but if anyone can recommend which ones to turn off & which to leave on to retain basic functionally (for a typical situation) i'd appreciate it, as 8 tabs is just too many for both me & my users

(especially as the top & bottom rows of tabs seem to interact with each other in ways not immediately obvious)

lordrahvin’s picture

I love both this module and this tutorial, thank you!
It was very helpful. I don't think I would have figured this out without your helpful tutorial and examples.

I ended up dissallowing all "I created" and such tabs and removing the Accessible Content link from the navigation menu in favor of posting up a "Pending" block. It's very simple for my editors. That's even better than I was hoping for!

nrackleff’s picture

I have set up this workflow using grants and revisioning and it is great. Thanks for this outline. We've discovered one little problem though. The moderators do see the "Unpublish current revision" link on the revisions tab, but if there have been no revisions since the original item was published, then the revisions tab is not displayed and there is no way for moderators to unpublish the current item from the site. How do moderators unpublish a piece of content that has not been revised? Should they have the revisions tab? have I done something wrong in the setup? Thanks for your help. -Nancy

RdeBoer’s picture

E.g. 6.x-3.1. Make sure to also download latest release of Module Grants, e.g. 6.x-3.2

felicyco’s picture

love this module.
the only thing is that i cant seem to find the edit link so I can published a node that has been revised.
i'm working in conjunction with the book module, diff.

just to check if I'm doing it correctly my path after an editor has revised and save content already in place.
i log in as administrator>accessible content>I can edit > In draft/pending publication> select title of node > select revision date of the in draft/pending publication.

this takes me to the node that was revised but no published. Once here if I'm correct I'm suppose to find the edit link so i can published the new revision. cant find that link anywhere.

please help!!!

Thanks,
Felipe

RdeBoer’s picture

You publish via the Publish this link which should appear once you've clicked on the revision modification date, as you described.
Reasons why the Publish this link does NOT appear might be:
o the logged-in user does not have the 'publish revisions' permission, see User management >> Permissions, section "revisioning".
o the content type doesn't have the New revision in draft, pending moderation tickbox ticked, see Content management >> Content types >> edit >> Workflow settings
PS: please use the forum for issues like these

StevenSokulski’s picture

Some of this information is pretty out of date, especially the tokens mentioned in the last couple paragraphs. The email address you need to use is the [revision-author-mail] and I can't seem to get any of the other node-specific tokens.

RdeBoer’s picture

The revision-related tokens work, as per the recently updated project page. For the other tokens see the Token module issue queue: #635570: Most tokens do not work in tokenized E-mails: [account:user], [account:mail]

Tim-Erwin’s picture

Hey,

thanks for the module. The whole access stuff in drupal is a pure headache. I'd like it if you would STRONGLY point out that it is essential to enable "view revisions of ANY content" in order to make this module work. I had to read the code to find that - after hours. (I know, it appears in step 7, but not as an essential step for this module to work.)

Regards

acarrasco’s picture

Hello everyone,

The message above is true, please take this into account to modify the instructions.

Congratulations and thank you for the module, is excellent.

LuckyBamboo’s picture

If a user edits one of nodes when this module is activated he is then sent to this page: /node/xxx/revisions/yyy/view , instead of being sent back to the node.
If the user can't view the revisions screen he gets a "You are not authorized to access this page". BIG problem. anyway to control where the user is redirected to after editing?

RdeBoer’s picture

Please post any further comments to this thread: #729378: Allow authenticated users to "view own revisions" but not "view all revisions". It also contains a workaround.
Where would you like the system to redirect to? To the current revision, the one the user started to edit?
Because, in a warped way the current behaviour does make sense... If the user is not the initial author and they have not been granted the permission to view revisions (of any type or the saved content type in particular), then they are not authorised to access a page displaying a revision, even though it's the one they just edited and saved (from current) ....
I do agree we need a "view own revision" kind of permission whereby "own" means the "revision(s) I created", as opposed to the "node I created". Feature request.

losman’s picture

First of all I can't thank you enough for the 'Revisioning 'application. I've been working and testing it with positive results.
However, it seems that whenever I publish or unpublish, this warning below comes up.

warning: Parameter 2 to revisioning_revisionapi() expected to be a reference, value given in E:\wamp\www\includes\module.inc on line 483.
warning: Parameter 2 to revisioning_revisionapi() expected to be a reference, value given in E:\wamp\www\includes\module.inc on line 483.

Is there anything I can change in the code to remove this warning?

Thanks

Losman

RdeBoer’s picture

frankiedesign’s picture

Hi there!

I'd like to give users the possibility to edit some nodes on their own resposibility (without moderation and/or new revision) and some other nodes (OF THE SAME TYPE) only by sending them to moderation.

Is that already possible with the given modules?

Best solution would be some integration with the TAC module, I think...
If you can't imagine any usefull scenario for such functionality, picture this:
Let's have a site with a lot of content of the type page, which can be created by users having either the role department1 or department2. With TAC the pages are sorted to the categories "department1pages" and "department2pages". These pages should be editable without moderation. But now, add a category "pagesofbothdepartments". Every page edited (or even created?) belonging to this category should need a moderation of a "department_coordinator". (Since none of the two departments wants someone from the other department edit stuff, that is afterwards refering to BOTH of the apartments).
So, that was the generic example... but the situation is explained quite well in my first line already...

Thanks for hints, answers and comments!

BTW: Nice module(s), anyway.. Good work. :)

Monzer Emam’s picture

I suggest following changes for step number 8

  1. Under User management>>Permissions assign permission as
    follows.
    • 8.1 In the node module section:
      • Make “access content” has defaulted (checked) to anonymous and
        authenticated users.
      • Switch off “administer nodes” for Author and Moderator (or
        perhaps all roles) as this gives these roles unrestricted access to
        all nodes, which defeats our purpose.
      • Give the Author role “create type name content” and “edit own
        content” permissions for the desired content types.
      •  You may not want to give any role the “delete revisions”
        permission, so that a full audit trail is always kept, in that
        content may be unpublished (removed from public view), but not
        removed from the database.
    • 8.2 In the revisioning module section:
      • Tick the "edit revisions" permission for Author and Moderator.
      • Essential: for the Author role tick "view
        revisions of own/any type content" for the content type(s)
        that are subject to moderation, i.e. the content types for which
        "New revisions in draft, pending moderation" was ticked in step 5.
        Note: you may use "view revisions" (node module section) instead,
        just be aware that "view revisions" applies across all content
        types, thus overriding the fine-grained versions of the revisioning
        section. Make sure none of the "view revisions..." permissions are
        ticked for the anonymous user.
    • 8.3 Give the Moderator in the node module section :
      "edit any [type|content type] content“, "revert revisions”,
      "view revisions"  (or In the revisioning module
      section :"view revisions of any [type|content type]  content"),
      “publish revisions”, “unpublish current revision” and "view revision
      status messages" permissions).
    • 8.4 Finally, under the module_grants and revisioning sections assign
      permissions to access the content filtering tabs as you see fit. Note
      that these do not affect access themselves, just permission to use the
      filtering tabs. The Moderator role would normally have at least "access
      I Can View", "access I Can Edit", "access All" and "access Pending tab",
      while for other authenticated users "access I Can View" and "access All"
      may be sufficient.
    • 8.5 Press “Save permissions”.
canishk’s picture

This is very serious issue.

I just enabled 3 content types for reviosioning. But while editing all the content-types came with revisoining which results pending the publication of new nodes. Even I have double checked all the content type to make sure that they are coincidently enabled reviosioning. I want to put these content-types without any pendiong/draft nodes.

Please reply. This is a stopper issue now!

haggins’s picture

Hi,
this looks like a very cool module. However I don't get the moderator access to the revisions page. Moderator only gets access to the edit page unless I grand him "administer nodes" permission. But this is too much.

Moderator has the following permissions:
node-module
- access content
- edit any myType content
- revert revisions
- view revisions

revisioning-module
- edit revisions
- publish revisions
- view revision status messages
- view revisions of any myType content

Moderator cannot access:
- node/8
- node/8/revisions/list
This pages are only accessible after the node/revision has been published.

What did I miss? I'm using 6.x-3.11.

Edit: There's also only the current revision listed at the revisions page even when I create x new ones.

sidone’s picture

Hi haggins,

I had the same issue. It was solved at the moment I activated the main "module grants" module.

Is there also a dependency to main "module grants" module?

matt.rad’s picture

I am having the same issue now on D7. Any ideas how to fix it there, since Module Grants has no D7 release?

sticky2010’s picture

Revisioning module conflicts with Panel Node Template. I am using

Revisioning module: 6.x-3.11
Panels: 6.x-3.9

We have 'Person' content type. We want to use Panels to show domain.com/Person content type using Panel Node Template.

When we try to enable the Panel Node Template, I get the following error:

"Page manager module is unable to enable node/%node because some other module already has overridden with _revisioning_view"

Can somebody advise what is wrong please? Thank you.

sticky2010’s picture

Here is the link to if your Panel Node Template conflicts with Revisioning Module:

http://drupal.org/node/519924

RdeBoer’s picture

... or one of the alternatives described in the link above

RdeBoer’s picture

... one of the alternatives described in the link below

misterT’s picture

"The anonymous user should only have the “View published content” permission (Node module section)."

I have a node that started out with 3 revisions, and is now published, and the anonymous user is unable to access the published (and current) revision of the node.

--------
edit: I duplicated this several times using only core and the Revisioning module. However currently I am no long experiencing this issue. I think the issue occurred only during use of the 7.5-dev release of core from July 25 2011, which I am no longer using. At the moment I don't have time to investigate further. If this happens again I will start an issue report and try to ensure it's not a permissions mistake on my end. This post pertains to revisioning-7.x-1.2.

michielkenis’s picture

First of all thanks a lot for this great module! It's exactly what I'm looking for. But I have a problem. Either I use the module the wrong way or there is somewhere a bug.

When I create content and publish it, the content is visible to all users (of course). But when I edit the content and I mark it for moderation (so it needs approval of someone), the edits are published and shown to public anyway. Even if I checked off the 'Publish' option. How can I make sure the edits aren't visible to anyone before the moderator has given his approval?

RdeBoer’s picture

That way you and I can track it and it can be more easily commented on:
http://drupal.org/node/add/project-issue/revisioning