Last modified: 2014-11-14 07:57:49 UTC
In a system where users must be logged in to edit, if an edit form is submitted beyond the expiry period, only a message to log in again is presented and all text changes lost. This occurs if someone has spent too long editing and is unaware of the pending expiry. Pushing the back button with Explorer 7 yields only an "expired page" message with all previously entered text unavailable. If the post page would a least maintain a copy of the newly entered text, the user could regain their logged in status without losing all their hard work.
Are there still browsers that don't correctly preserve entered form text? I tried this a few times (navigating to different pages manually while there was data in the edit form) and it was still there when I got back on firefox 7, chrome 13, opera 10. (also, the user mentions internet explorer, but has platform = Linux. ???)
*** Bug 58642 has been marked as a duplicate of this bug. ***
I don't understand why something this important has been ignored for long time. Although it doesn't make problem in minor edits, It can discourage user in major editing. It has most impact on new users who are not aware of session expiration.
I think this is fixed (a long time ago). I did the following (locally): 1. Log in. 2. Go to an edit page. 3. Make some changes 4. Delete all cookies for the site. 5. Click "Save page" I get "Sorry! We could not process your edit due to a loss of session data. Please try again. If it still does not work, try logging out and logging back in." and a preview. Like a normal preview, the text is shown below and not lost. I can then: 6. Log in again in a new tab or window. 7. Preview 8. Save If this is still present for you, please give your browser (with version) and exact steps to reproduce (like the ones above).
(In reply to Matthew Flaschen from comment #4) > I think this is fixed (a long time ago). As far as I remember the "Sorry! We could not process your edit" message has always existed (yep, found it; 2005, fdbdd7707ba98066456ea20892572b34d2ead649 ). I interpreted this bug as being about renewal of tokens and perhaps user sessions. Comment 0 says "In a system where users must be logged in to edit", did you test that? I added it as step 0 in before yours (with a publicly viewable page) and I got the "view source" screen.
