[development] Use revisions to replace previews

Victor Kane victorkane at gmail.com
Sun Jun 10 12:53:38 UTC 2007

This is really necessary for many practical applications of Drupal.
Please put yourselves in the place of end users.

On 6/10/07, Michelle Cox <mcox at charter.net> wrote:
> How hard would it be to add a third button? So you have "preview" "save
> draft" "save"? Save draft would go through what save normally does with the
> exception that it doesn't wipe out any existing "official" version of the
> node where "preview" would just show you without any sort of saving as it
> does now.
> I don't know about the code end but from the user end that makes sense to
> me.
> Michelle
> On 6/9/2007 4:48:32 PM, Dries Buytaert (dries.buytaert at gmail.com) wrote:
> I agree with this.  As an excessive previewer myself, the mental
> model that lives in my head assumes that previews are volatile.  I
> preview because I don't want to save my data before it's ready to be
> saved.  I don't finish everything that I start writing so every once
> in a while, I abandon the post in which case the previews and the
> node ID would still be in the database?  That said, I'm not opposed
> to an auto-save feature or a 'Save as draft' feature.  Except that it
> should somehow align better with my mental model.
> Something else to consider -- spammers will often try to submit spam
> to your site. Even if they don't make it through, they might insert
> permanent junk in your database.

More information about the development mailing list