Last modified: 2008-01-03 17:50:14 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 T14492, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 12492 - Session data lost, software thinks edit summary is blank
Session data lost, software thinks edit summary is blank
Status: RESOLVED DUPLICATE of bug 8912
Product: MediaWiki
Classification: Unclassified
Page editing (Other open bugs)
1.12.x
PC Windows XP
: Normal minor (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2008-01-03 17:13 UTC by Simon Walker
Modified: 2008-01-03 17:50 UTC (History)
1 user (show)

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


Attachments

Description Simon Walker 2008-01-03 17:13:50 UTC
After the Session Data error message appears ("Sorry! We could not process your edit due to a loss of session data. Please try again.") when attempting to save an edit, and an edit summary is entered, the software then assumes that the edit summary is blank, or unmodified, as the "edit summary not entered" reminder appears WHEN retrying the save. This has happened at least twice to me today, so it is not a one-off problem. This problem does only appear to occur when the session data is lost. This bug occurs on the Edit page screen, and I am using Firefox 3 Beta 2, but I have also tested this with Firefox 2.0.0.11, which is a stable release of Firefox. Instead of appearing with the blank edit summary message, I would expect the software to see that I have in fact entered an edit summary, and continue saving the page after I click the save button.
Comment 1 Roan Kattouw 2008-01-03 17:50:14 UTC

*** This bug has been marked as a duplicate of bug 8912 ***

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


Navigation
Links