The below is actually how I had to code up
the last user-submitted content site we made. Separate buttons which execute
that state change versus the radio pick and the ‘submit’ button
would be a good improvement.
How could we help implement this change
directly into workflow?
-Greg
From:
development-bounces@drupal.org [mailto:development-bounces@drupal.org] On Behalf Of Florian Loretan
Sent: Monday, June 11, 2007 6:01
AM
To:
Subject: Re: [development] AB-Use
revisions to replace previews
On 6/11/07, Earnie
Boyd <earnie@users.sourceforge.net>
wrote:
But in the later scenario I might not be ready for the editor to
publish it. I would always want a [preview] without saving to the DB.
I would want [draft] to save a working copy for later revision by me
and only me. And I would then want a [ready] for an editor to publish.
If I was editor then I would get the [publish] button instead of the
[ready] button.
That's actually an improvement that I thought about adding to the workflow
module.
Instead of having a radio-button allowing to set the workflow status, having
buttons for every available workflow status would be clearer (from a user
prospective, you'd expect a change of the status setting to be reversible,
whereas buttons clearly indicate an action being performed).
I haven't heard anything about integrating the workflow module in core (maybe
something to consider at some point?) but we could already have this enabled
for the basic core workflow.
Florian