Last modified: 2010-05-15 16:03:31 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 13467 - Add link type selectors to Special:WhatLinksHere
Add link type selectors to Special:WhatLinksHere
Status: RESOLVED DUPLICATE of bug 6934
Product: MediaWiki
Classification: Unclassified
Special pages (Other open bugs)
All All
: Normal enhancement (vote)
: ---
Assigned To: Nobody - You can work on this!
Depends on:
  Show dependency treegraph
Reported: 2008-03-21 09:37 UTC by Kalan
Modified: 2010-05-15 16:03 UTC (History)
1 user (show)

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


Description Kalan 2008-03-21 09:37:31 UTC
Currently Special:WhatLinksHere shows three link types at once: page links, redirects and template transclusions. Sometimes it's useful to browse them at once, but sometimes it's not. For Wikimedia, there is a workaround "WhatRedirectsHere" Toolserver tool [1], but if you want other options than just redirects, you will have to extract them by hand.

My proposal is to add "selectors" to that special page, same appearance as in Special:RecentChanges:

[Hide/Show] page links | [Hide/Show] redirects | [Hide/Show] transclusions

For compatibility, all of them should be turned on by default.

Comment 1 Huji 2008-03-21 21:54:34 UTC
This is partially duplicating bug 13248 (or vice versa?!)
Comment 2 Huji 2008-03-21 22:06:59 UTC

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

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