<br><br><div class="gmail_quote">On Mon, Feb 7, 2011 at 11:41 AM, will trillich <span dir="ltr"><<a href="mailto:will.trillich@serensoft.com">will.trillich@serensoft.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Catalystry:
<div><br></div><div>So there's a second page where they fill out some finalization options (with the original data in hidden fields) and there they have a final "submit" button for the purpose. And they should be able to use their browser's "back" button to get back to the edit form.</div>
<div><br></div><div><br></div><div>The problem we're wrestling with is that the "edit" action should have a URL distinct from the close action so that the user can hit the "back" button if need be.</div>
<div><br></div><div>/item/# <= view item</div><div>/item/#/edit <= edit form</div><div>/item/#/close <= confirm-close form</div></blockquote><div><br></div><div><br></div><div>Nah. I wouldn't have two URLs. I'd have one URL, and determine whether to save or save+close based on the value of the submit button.</div>
<div>Furthernore, after a successful submit (assuming http POST) I'd redirect the user to a new display page via GET so that they can hit the refresh button all the like without attempting to repost the submission.</div>
<div><br></div><div>Len.</div></div><br>-- <br><a href="mailto:lenjaffe@jaffesystems.com" target="_blank">lenjaffe@jaffesystems.com</a> 614-404-4214<br>Asst. Scoutmaster Troop 156 - <a href="http://www.bsatroop156.org" target="_blank">www.bsatroop156.org</a> - <a href="mailto:webmaster@bsatroop156.org" target="_blank">webmaster@bsatroop156.org</a><br>
Proprietor: <a href="http://www.theycomewithcheese.com/" target="_blank">http://www.theycomewithcheese.com/</a> - An Homage to Fromage<br>