<HTML><BODY style="word-wrap: break-word; -khtml-nbsp-mode: space; -khtml-line-break: after-white-space; ">@Kevin: A revision is always stored in the DB (in the node_revisions table IIRC) and hence it *is* saved. So it would simply show up in the list of revisions, meaning that if the user can access the revisions, he can access the preview revision as well.<DIV>But I'm sure David is talking about some UI enhancement that would allow the user that would ask the user if he'd like to edit his last unpublished revision (i.e. a preview) when the user edits a node.<DIV><BR class="khtml-block-placeholder"></DIV><DIV>@David: IMO the interim preview revisions should be deleted.</DIV><DIV>And the ability to go back to your last unpublished revision (last preview) should also take a special case into account: what if /another user/ has updated the node after your last unpublished revision? The user should be warned in this case, or he might unknowingly erase new content by that other user.</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>Wim</DIV><DIV><BR><DIV><DIV>On Jun 7, 2007, at 21:29 , Kevin Reynen wrote:</DIV><BR class="Apple-interchange-newline"><BLOCKQUOTE type="cite"><BR>And how would the average user find a previewed but not saved revision? <BR><BR>Is that something only users in a role with access revisions could recover?<BR><BR>- Kevin Reynen <BR><BR><DIV><SPAN class="gmail_quote"> On 6/7/07, <B class="gmail_sendername">David Strauss</B> <<A href="mailto:david@fourkitchens.com">david@fourkitchens.com</A>> wrote:</SPAN><BLOCKQUOTE class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> With clever use of revisions, we could eliminate the preview system<BR>entirely from the codebase.<BR><BR>Here's how it would work. If a user clicks Preview, it creates a new<BR>revision but does not mark it as the current revision. The preview seen <BR>is the new revision rendered. If a user clicks Save, it creates a new<BR>revision *and* marks it as the live one. Optionally, we could then<BR>delete the interim preview revisions.<BR><BR>Another advantage to this is that a user can work on a node, preview it, <BR>and have their work saved. If a user comes back and edits the node with<BR>unsaved previews, they can choose to work from the latest preview or the<BR>latest public revision.<BR><BR>I know Drupal 6 goes a long way to fixing previews, but this would <BR>eliminate all inconsistency.<BR><BR><BR></BLOCKQUOTE></DIV><BR></BLOCKQUOTE></DIV><BR></DIV></DIV></BODY></HTML>