Last modified: 2009-02-06 02:13:30 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 12183 - change in output for MediaWiki:1movedto2
change in output for MediaWiki:1movedto2
Product: MediaWiki
Classification: Unclassified
General/Unknown (Other open bugs)
All All
: Normal enhancement (vote)
: ---
Assigned To: Nobody - You can work on this!
Depends on:
  Show dependency treegraph
Reported: 2007-12-02 19:39 UTC by Chris
Modified: 2009-02-06 02:13 UTC (History)
0 users

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


Description Chris 2007-12-02 19:39:56 UTC
right now, in MediaWiki:1movedto2  $1 is the old name, and $2 is the new name. the default system text in this page is "[[$1]] moved to [[$2]]"

the problem is, since $1 just got moved to $2, $1 is now a redirect to $2, making both those links essentially the same.

repeated attempts to use {{fullurl}} to make a redirect=no link out of $1 have failed due to the order of the parser dealing with {{fullurl}} vs the dereference of $1 to the value of the original name (it ends up with a link to the page "$1" not the value of $1)

consider on Special:Whatlinkshere

< thispage
The following pages link to thispage: 

the first "thispage" is a link to the page including a "redirect=no", where as the 2nd one, does not have a redirect=no.
Comment 1 Chris 2009-02-06 02:13:30 UTC
was fixed in a later major version after i filed the bug forever ago

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