[development] AB-Use revisions to replace previews

Greg Holsclaw Greg.Holsclaw at trouvemedia.com
Mon Jun 11 17:03:30 UTC 2007

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


How could we help implement this change directly into workflow?





From: development-bounces at drupal.org
[mailto:development-bounces at drupal.org] On Behalf Of Florian Loretan
Sent: Monday, June 11, 2007 6:01 AM
To: development at drupal.org
Subject: Re: [development] AB-Use revisions to replace previews


On 6/11/07, Earnie Boyd <earnie at 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
	  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

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.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.drupal.org/pipermail/development/attachments/20070611/2ee4629b/attachment.htm 

More information about the development mailing list