Last modified: 2014-08-29 08:26:42 UTC

Wikimedia Bugzilla is closed!

Wikimedia has migrated from Bugzilla to Phabricator. Bug reports should be created and updated in Wikimedia Phabricator instead. Please create an account in Phabricator and add your Bugzilla email address to it.
Wikimedia Bugzilla is read-only. If you try to edit or create any bug report in Bugzilla you will be shown an intentional error message.
In order to access the Phabricator task corresponding to a Bugzilla report, just remove "static-" from its URL.
You could still run searches in Bugzilla or access your list of votes but bug reports will obviously not be up-to-date in Bugzilla.
Bug 11922 - Edit conflict not detected, middle edit reverted
Edit conflict not detected, middle edit reverted
Status: NEW
Product: MediaWiki
Classification: Unclassified
Page editing (Other open bugs)
All All
: Normal normal with 4 votes (vote)
: ---
Assigned To: Nobody - You can work on this!
: 22992 (view as bug list)
Depends on:
Blocks: 70163
  Show dependency treegraph
Reported: 2007-11-10 15:05 UTC by Orlady
Modified: 2014-08-29 08:26 UTC (History)
10 users (show)

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


Description Orlady 2007-11-10 15:05:28 UTC
An edit conflict should have been registered in the following sequence, but the second edit was saved anyway:
1. - User Zach4636 "undid" an edit made about 1 hour earlier. 

2. Before the above edit was saved, User Orlady had opened an edit window for the same article in order to remove a user's signature from the first line of the article. (This signature was part of the same edit that Zach4636 undid.) The edit was submitted two minutes later -- -- but it had the effect of restoring most of the content that Zach4646's edit had deleted.

An edit conflict should have been registered, preventing the second edit from being saved in this way.
Comment 1 Kef Schecter 2010-10-21 11:33:43 UTC
I notice a similar problem when editing the same page using multiple tabs. If you edit individual sections, the behavior is correct -- edits are merged properly if the sections don't overlap, and they yield a conflict if they do -- but if instead the two tabs are editing the entire page rather than individual sections, the second edit will silently undo the first.
Comment 2 Zwiebelleder 2011-06-01 18:33:26 UTC
Had the same problem today. Curiously on the edit conflict page. I was saving my edit on the conflict page and had overwritten a comment from another user, which he had written meanwhile.

See also:
Comment 3 Orlady 2012-03-04 04:08:09 UTC
This has cropped up again since the new version of MediaWiki was installed. At I have described two occurrences in two days of unflagged edit conflicts. In both instances in which edit conflicts were not registered, one user was editing a page section and the other user was editing the entire page.
Comment 4 Andre Klapper 2013-09-04 12:21:33 UTC
*** Bug 22992 has been marked as a duplicate of this bug. ***
Comment 5 Spinningspark 2014-07-10 13:05:40 UTC
I am restoring the priority of this to normal.  A bug that destroys the edits of others, potentially driving away new editors, cannot possibly be low priority.  According to the definitions, that means just sitting around until someone is kind enough to offer a patch.  IMHO, it should be an even higher priority.
Comment 6 Andre Klapper 2014-07-10 13:47:41 UTC
As long as nobody investigates and manages to track down criteria or situation to reproduce, it will de facto be low priority, no matter what it should be. :-/
Comment 7 Spinningspark 2014-07-10 14:08:11 UTC
Do you need more examples of the error?  What else can people do from the user side to help?
Comment 8 Andre Klapper 2014-08-05 22:35:00 UTC
(In reply to Spinningspark from comment #7)
> Do you need more examples of the error?  What else can people do from the
> user side to help?

Adam (CC'ed): You worked on bug 56849 (edit conflict detection) a while ago; maybe you could provide some input if there's anything / way users can help here?

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