I hope this is the correct place for this, I've been working through the Documentation at http://drupal.org/node/408052.

I have everything working according to the documentation but it seems a final step is missing.

I've set up a trigger to publish the node when it moves to the final state 'live'.

When you view this in Accessible content it says Published: Yes, Workflow state: Live. Which is correct.

If the workflow state is then changed to 'draft' or 'review' it still shows as Published: Yes in the accessible content which is correct because a version of it is published, but a later version is not published so it should also show as unpublished, this creates the problem where an editor can not easily find nodes in review after a previous revision has been published.

Is there a final step in the documentation missing or have I missed it? Or is this a feature request?

Thanks for the great modules.

Comments

rdeboer’s picture

rdeboer
Location Melbourne
commented

Thanks for the great feedback Nick!

You've answered most of your questions, but I' might just do that some more....

Revisioning aims to offer a low-cost/low-effort solution even if you don't install Workflow.

Without Workflow, Revisioning is lacking clearly defined states, so the definition of a "revision in review" is a bit wishy-washy. This is a result of Drupal core not cleary defining what "published" means in the presence of multiple revisions. "Published" is just a flag (i.e. "yes" or "no", not both) on the node object, regardless of what revisions may be at play.... and that's what the Accessible content page directly reflects. You should read it as "there is one revision that is published (not saying which one)".

Having said that.... if an author changes the state from "live" to "draft" (as that's the only state in which authors can edit the content) and they change and save the edits, then that content **should** show up under the "Pending" tab.... Is that not happening?

nick.c’s picture

nick.c commented

Thank you for the quick response, you are absolutely correct.

When setting up the permissions I hadn't enabled "access Pending tab" for editor.

Thank you also for the extra clarification, it makes much more sense knowing about the nodes and multiple revisions and the way the publish flag works.

rdeboer’s picture

rdeboer
Location Melbourne
commented
Status: Active » Closed (fixed)

Great!
Then I might close this one.

guykit’s picture

guykit commented

before you close this! I have set it up so as you describe so that when the workflow is changed to published the revision is published, but is there a way of doing this in reverse? i.e. If I change the workflow state to draft the item seems to have to be unpublished thru the revisions tab still - seems to me I need a trigger action like "unpublish the most recent revision" Or is there another way of doing this?

Thanks for your help

rdeboer’s picture

rdeboer
Location Melbourne
commented

After you have published the first revision of a node, "in draft" means that you're working on a new revision, while the current revision is still visible to the public. So the node needs to remain published.
Remember that "published" simply means that there is one revision visible to the public (all others are currently not visible). If you unpublish a node, all its related content is taken off the site.

gupta.sandeepcs’s picture

gupta.sandeepcs commented

hey nick,
i think you will face the problem in deleting the node as when u take the content back to draft stage the author gets the authority of deleting both the published revision as well as edited revision that is one on which u are working in draft stage..
So don't u think this is a bug as author is not supposed to delete the published content..i have faced the similar problem that's why i am writing it..