[development] Use revisions to replace previews

[Kevin Reynen]

And how would the average user find a previewed but not saved revision?

Is that something only users in a role with access revisions could recover?

- Kevin Reynen

On 6/7/07, David Strauss <david at fourkitchens.com> wrote:
>
> With clever use of revisions, we could eliminate the preview system
> entirely from the codebase.
>
> Here's how it would work. If a user clicks Preview, it creates a new
> revision but does not mark it as the current revision. The preview seen
> is the new revision rendered. If a user clicks Save, it creates a new
> revision *and* marks it as the live one. Optionally, we could then
> delete the interim preview revisions.
>
> Another advantage to this is that a user can work on a node, preview it,
> and have their work saved. If a user comes back and edits the node with
> unsaved previews, they can choose to work from the latest preview or the
> latest public revision.
>
> I know Drupal 6 goes a long way to fixing previews, but this would
> eliminate all inconsistency.
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.drupal.org/pipermail/development/attachments/20070607/df8dbd52/attachment.htm