(I thought it was a better idea to open a new issue for D6 rather than posting to #171210: Play nicely with revision moderation (do not publish latest revision when submitting workflow tab), which is for D5.)

Is it a feature request, a support request or a bug report I don't know, but the fact is it is still impossible to have worflows working at a revision level, where we can set a state to a revision and where the existing revisions will be left published until the new one have gone through the workflow (even if it needs an external module like Revision Moderation to achieve that). A lot of people would need content to follow a workflow before publication, not only for new content, but also for updated content, and that without unpublishing the existing version of the node on the public website. A similar feature is requested in D7 core at #218755: Support revisions in different states.

The issue is running for quite some time now (2007) and I'm posting here to know where the problems are lying for D6, what is lacking, and what can be done. I am willing to help as much as possible on this issue.

Comments

chinko’s picture

chinko CreditAttribution: chinko commented

I am a newbie in Drupal. Our company is considering using Drupal to build enterprise level websites.

One of our primary business requirements is to enable a content editor to update text on existing pages. The changes need to be reviewed and approved by another person before they are visible to the public. Before a changed node is approved, we need the web site to continue displaying the last approved revision. The fact that the workflow module does not support this means we cannot allow changes made directly in the live site. We need to setup a separate authoring environment for the editing and approval. We then need a migration process to dump all tables and files from the authoring environment to the live environment. With live content being added by visitors in the live site, the migration is just impossible.

We have looked at a number of modules related to backup, migration, import and export and AutoPilot. None of them is a complete solution for this migration process.

It will really be great if the workflow can handle revision level publishing, i.e. rendering the latest approved revision. Does anyone know if this is very hard to achieve?

Chin

Kristen Pol’s picture

Kristen Pol
she/her
Primary language English
Location Santa Cruz, CA, USA
CreditAttribution: Kristen Pol commented

I got revisions working with the workflow module by using the revision moderation module (with my patches). Check out: http://drupal.org/node/387728

Kristen Pol’s picture

Kristen Pol
she/her
Primary language English
Location Santa Cruz, CA, USA
CreditAttribution: Kristen Pol commented

I have since switched to using the revisioning module along with a custom action and it's working nicely.

rconstantine’s picture

rconstantine CreditAttribution: rconstantine commented

In general, workflow can work with the revisioning module. However, if at any time in your process you need to make programmatic changes to the node content via rules (for example), those changes will get applied to the 'current' live revision, rather than the pending revision and I think it has to do with node_save being called by the workflow module. Just a guess though.

So integration isn't all there yet.

johnv’s picture

johnv
Primary language Dutch
CreditAttribution: johnv commented

This would be possible if Workflow were a 'true' Field API field, as proposed in #2019345: Create a 'Workflow Field' with Widget, Formatter, Fieldtype

johnv’s picture

johnv
Primary language Dutch
CreditAttribution: johnv commented
Status: Active » Closed (duplicate)

Let's focus on #2019345.