Last modified: 2004-09-08 13:02:16 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 69 - per-section editing clobbers random section
per-section editing clobbers random section
Status: RESOLVED DUPLICATE of bug 56
Product: MediaWiki
Classification: Unclassified
Page editing (Other open bugs)
All All
: Normal normal (vote)
: ---
Assigned To: Nobody - You can work on this!
Depends on:
  Show dependency treegraph
Reported: 2004-08-16 05:34 UTC by Timwi
Modified: 2004-09-08 13:02 UTC (History)
1 user (show)

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


Description Timwi 2004-08-16 05:34:23 UTC
Originally submitted by Robert Dodier (robert_dodier)  2004-06-23 08:36


I've seen this twice on Wikipedia:Votes for deletion:

If a section (denoted by equals signs) is edited by
clicking the link that says "[edit]" at the right-hand
margin (i.e., not editing whole page), when the section
is saved, the saved text clobbers some other section at

Here are two examples:

It seems like a pretty serious bug to me; its presence
pretty much obviates the usefulness of the per-section
editing scheme. 

Thank you very much for your attention to this issue. I
appreciate your help very much!

Robert Dodier
Comment 1 Wil Mahan 2004-09-08 13:02:16 UTC
Hi, after looking at your example, I can confirm that this bug is the same as bug 
56, for which I have submitted a patch. Thanks.

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

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