<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>