Hi

After days of fiddling with Revisioning and Workflow configuration I just can't get them to play ball together. I'm sure the functionality i'm trying to achieve is quite standard (ie draft->review->published etc), and I've followed the 'state-based revisioning' tutorial as a guide: http://drupal.org/node/408052

The above post states

Once a revision has been promoted to “live” an author can again grab that piece of content at any time by transitioning it to “in-draft” (via the Workflow tab). They can repeatedly edit and save content, but it always takes a moderator (or administrator) to review it and make it visible to the public.

The issues i'm having seem to stem from the fact that Workflow states are stored against NODES and NOT REVISIONS. If a node can have many revisions but only have a single "global" state, i cannot see how the above could ever work. For example, how can a node be in a 'published' state (publically viewable), and also in a 'draft' state such that the author can submit a new revision, if only one state is allowed per node?

Another point is that when you transition a node via the 'workflow' tab, a new revision is not created (as opposed to the case of editing it on the node form). Surely you wan to create a new revision whenever the state is changed?

I appreciate these issues may be more closely related to Workflow, but since Revisioning appears to be geared towards integration with Workflow i thought you may be able to offer some insight.

Comments

rdeboer’s picture

rdeboer
Location Melbourne
commented

Hi rich,
You hit the nail on the head with saying that "Workflow states are stored against NODES and NOT REVISIONS".

There is a bit of an impedance mismatch.
But if you try the tutorial you mentioned you'll find that Workflow+Revisioning is actually quite workable a combo.

When a node is marked as "published" only one (known as the "current") of the many revisions of the node is publicly visible.
In a proper setup, permissions are set so that anonymous users may NOT view any revisions, except for the currently published one. So it's important you UNTICK the "view revisions" permission for anonymous users, while ticking it for authors and moderators.
This is how a node can be in a draft state (allowing the author to create a new revision) while simultaneously its current revision is visible to the public.

"Another point is that when you transition a node via the 'workflow' tab, a new revision is not created (as opposed to the case of editing it on the node form). Surely you wan to create a new revision whenever the state is changed?"

I'd say this is personal choice, whether you want a new revision created when the state is changed. The Workflow developer must have felt this wasn't the case. To avoid confusion between the two options, Revisioning comes with an admin setting (Administer >> Site configuration >> Revisioning that suppresses the option to change state via the Edit form.
See also #789760: workflow state changes create new revisions for a similar discussion.

Hope this clarifies things a bit.

ravi.shankar.mishra’s picture

ravi.shankar.mishra commented

hi...rich.3po and RdeBoer
1-i make new revision from node which have workflow state 'published'
2-when i change revision Workflow state from 'published' to 'draft' it also change the Workflow state of node which is in the public ('published') and now it is not show to user (anonymous user ) because i have condition that if Workflow state is 'published' then user (anonymous user ) can see the content
3-how i can change revision state (other than published ) but node which is in public should have same workflow state('published')...

rdeboer’s picture

rdeboer
Location Melbourne
commented

Sorry ravi
Not sure I understand what you mean...

nflowers1228’s picture

nflowers1228 commented

I just had the same issue, at least I think it's the same issue. If I moved content from one workflow state to another (Live to Send for Review) neither the published version or revision were visible to the public because both had the Send for Review workflow state, which only allowed administrators and editors the ability to view. I had to allow anonymous users to view the pages in the Send for Review workflow state. Then the "published" version could be seen even though it was in the Send for Review state. The revision could not be seen because the ability to view must be controlled by the Revisioning module.
I found the instructions http://drupal.org/node/408052 to be helpful. #8 was what I was missing, thinking that if I allowed anonymous uses to view my pages in Send for Review mode, they could see them prior to being published. I tested this thoroughly and that is not the case.

rdeboer’s picture

rdeboer
Location Melbourne
commented
Status: Active » Closed (cannot reproduce)

No activity for 3 months. Closing.