Last modified: 2014-09-08 10:54:54 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 T71920, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 69920 - new section not added on edit conflict
new section not added on edit conflict
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-08-22 19:30 UTC by Umherirrender
Modified: 2014-09-08 10:54 UTC (History)
4 users (show)

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


Description Umherirrender 2014-08-22 19:30:58 UTC
Have seen this[1] edit on the german village pump: The summary indicates a new section, but actually the last edit was removed and no new text was added. Possible regression from Gerrit change #144603, but also possible from other changes, because this was seen short after the update to 1.24wmf17.

Comment 1 Andre Klapper 2014-08-24 18:56:33 UTC
(In reply to Umherirrender from comment #0)
> Possible regression from Gerrit change #144603

I see that anomie and Aaron are already CC'ed...

Wondering how often this problem happens.
Comment 2 Brad Jorsch 2014-08-25 15:21:01 UTC
The situation of getting an edit conflict when adding a new section is very hard to test, since it generally cannot conflict. But if it does, the user will be given the usual full-page edit screen with the current page text in the top box, the diff between the top and bottom text boxes, and additional text box with the submitted content (in this case, the new section merged into the article).

My best guess as to what happened here was that it did hit the rare case where a conflict can occur on a new section edit, and then additionally hit bug 42163 giving a top box with the content of the older revision, and then the user just clicked "save" again on the conflict screen without altering the text in the top textbox.

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