Last modified: 2006-08-12 04:08:14 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 6932 - Moving pages with named entity in title
Moving pages with named entity in title
Status: RESOLVED DUPLICATE of bug 337
Product: MediaWiki
Classification: Unclassified
General/Unknown (Other open bugs)
All All
: Normal normal (vote)
: ---
Assigned To: Nobody - You can work on this!
Depends on:
  Show dependency treegraph
Reported: 2006-08-06 14:40 UTC by Holger Thölking
Modified: 2006-08-12 04:08 UTC (History)
0 users

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


Description Holger Thölking 2006-08-06 14:40:18 UTC
On the German Wikipedia, someone created the articles “Trondheims-Ørn“
and “Fortuna Hjørring” (yes, exactly as I typed it). My attempt to move
these pages to the correct pages (“Trondheims-Ørn” and “Fortuna Hjørring”)
failed, as the software—announcing that a page cannot be moved over
itself—apparently treats characters and their corresponding named entities the same.

I then tried to rename the articles “crabwise”, i.e., moving the pages to a
wrong destination first (e.g. “Trondheims-Orn”), deleting
“Trondheims-Ørn”, and afterwards moving the page back to the correct
page. However, it turned out that the page couldn’t be renamed at all and had
finally to be moved via copy-and-paste.
Comment 1 Brion Vibber 2006-08-12 04:08:14 UTC

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

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