Last modified: 2011-04-14 15:10:33 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 T19934, the corresponding Phabricator task for complete and up-to-date bug report information.
First Last Prev Next    This bug is not in your last search results.
Bug 17934 - Special:DoubleRedirects in a multi-redirect configuration
Special:DoubleRedirects in a multi-redirect configuration
Status: NEW
Product: MediaWiki
Classification: Unclassified
Special pages (Other open bugs)
1.15.x
All All
: Low enhancement with 2 votes (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency tree / graph
 
Reported: 2009-03-11 12:50 UTC by Russell Blau
Modified: 2011-04-14 15:10 UTC (History)
3 users (show)

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

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Russell Blau 2009-03-11 12:50:57 UTC 
Since r45973, it has been possible to configure a wiki to allow double- or higher-level redirects, up to a maximum value given by $wgMaxRedirects.  If this variable is set to a value greater than 1, however, [[Special:DoubleRedirects]] will show redirects that are valid under the wiki's configuration.  The special page should be fixed to show only those redirect chains that exceed the maximum configured length, and probably should also be renamed to [[Special:MultipleRedirects]] or something similar.  The default introductory text in [[Mediawiki:Doubleredirectstext]] should also be updated, preferably incorporating the value of $wgMaxRedirects in the text, and [[Mediawiki:Doubleredirects]] should be changed to "Multiple redirects" or something similar.
Comment 1 Matthew Cutler 2009-03-11 18:17:00 UTC 
I suggest a rename to [[Special:LongRedirectChains]] when this bug is fixed.
Comment 2 Le Chat 2009-05-06 07:43:40 UTC 
Is anything being done about this? It seems a waste of work to have introduced this new functionality if we're not going to be able to use it because of this one little remaining bug.
Comment 3 Le Chat 2009-05-06 07:52:17 UTC 
PS Similar situation at bug 17571, where I've suggested that there might be some connection between the two issues.
Note You need to log in before you can comment on or make changes to this bug.
First Last Prev Next    This bug is not in your last search results.

Navigation
Links