Last modified: 2014-11-14 07:57:49 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T11749, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 9749 - Changes lost when submitting an edit after the session has expired
Changes lost when submitting an edit after the session has expired
Product: MediaWiki
Classification: Unclassified
Page editing (Other open bugs)
PC Linux
: Low normal with 1 vote (vote)
: ---
Assigned To: Nobody - You can work on this!
: testme
: 58642 (view as bug list)
Depends on:
  Show dependency treegraph
Reported: 2007-05-01 00:53 UTC by Ron Platt
Modified: 2014-11-14 07:57 UTC (History)
4 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Description Ron Platt 2007-05-01 00:53:25 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.
Comment 1 Dan Collins 2011-07-12 04:29:24 UTC
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. ???)
Comment 2 Andre Klapper 2013-12-18 13:52:54 UTC
*** Bug 58642 has been marked as a duplicate of this bug. ***
Comment 3 omid 2013-12-19 08:34:50 UTC
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.
Comment 4 Matthew Flaschen 2014-11-14 02:14:39 UTC
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).
Comment 5 Nemo 2014-11-14 07:57:49 UTC
(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.

Note You need to log in before you can comment on or make changes to this bug.