Last modified: 2014-08-29 08:26:42 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 T66237, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 64237 - Warns about nonexistent edit conflicts
Warns about nonexistent edit conflicts
Status: NEW
Product: MediaWiki
Classification: Unclassified
Page editing (Other open bugs)
All All
: High normal (vote)
: ---
Assigned To: Nobody - You can work on this!
Depends on:
Blocks: 70163
  Show dependency treegraph
Reported: 2014-04-22 12:59 UTC by Elitre
Modified: 2014-08-29 08:26 UTC (History)
7 users (show)

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

Screenshot (155.28 KB, image/png)
2014-05-30 19:24 UTC, Rummana Yasmeen

Description Elitre 2014-04-22 12:59:56 UTC
Not sure if related to bug 55392.
IP user on it.wp reports what follows:
he edited multiple times.

First edit, an edit conflict notice came up.
He tried to solve that, but there were no actual differences. At that point, although he didn't save, he noticed his edit had already been saved in the history.
Second edit, nothing to report.
Third edit, same thing as the first one.

Firefox 28.0, Win7, Vector.

I didn't try to reproduce.
Comment 1 James Forrester 2014-05-30 02:42:30 UTC
I think (hope) that this was fixed in the fixes to edit conflict code a few weeks ago.
Comment 2 Rummana Yasmeen 2014-05-30 05:28:44 UTC
I got this issue today again, while I was trying to add a new section in edit source mode.But could not reproduce it later.But this is the second time I experienced this issue following the same steps.
Comment 3 Rummana Yasmeen 2014-05-30 19:24:29 UTC
Created attachment 15537 [details]

Again, reproduced on test2, screenshot attached.Reopening the bug.
Comment 4 Alex Monk 2014-05-31 15:33:32 UTC
In edit source mode? Is this a VE bug?
Comment 5 Rummana Yasmeen 2014-05-31 19:36:38 UTC
Yes, the edit conflict warning appears in the edit source mode , not in VE .
Comment 6 Alex Monk 2014-05-31 19:46:48 UTC
Okay, I will move this to the MediaWiki product of BZ then.
Comment 7 Alex Monk 2014-05-31 22:27:31 UTC
Ran into what I believe to be this bug at
Comment 8 James Forrester 2014-06-10 18:12:50 UTC
Copying in Adam who was active in this code area recently – ideas about a regression?
Comment 9 Adam Wight 2014-06-11 20:54:28 UTC
This would be the first I've heard of a new regression.  I've tried to leave the edit conflict code functionally unchanged with my recent patches, and the first report predates any work I've done.

I do know there are lots of unpleasant ways that edit conflicts can fail at the moment, silently losing changes being the worst.  The reported conflict behavior doesn't sound familiar however, so I'll leave this bug open.

Currently, I'm focusing on adding log instrumentation so that we are able to better diagnose this sort of thing.
Comment 10 Rummana Yasmeen 2014-06-13 18:18:48 UTC
This happens to me everyday atleast once in a new login session, when I first time try to save something from Edit Source mode.
Comment 11 Nemo 2014-07-10 13:35:36 UTC
We probably need a tracking bug for edit conflicts issues here.
Comment 12 Andre Klapper 2014-07-10 16:31:54 UTC
Who does a tracking bug exactly help and which problem does it solve?
Why is searching for "edit conflict" not sufficient?

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