Last modified: 2006-10-06 14:24:47 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 7506 - special:whatlinkshere should list the whatlinksheres by namespace
special:whatlinkshere should list the whatlinksheres by namespace
Status: RESOLVED DUPLICATE of bug 4624
Product: MediaWiki
Classification: Unclassified
Database (Other open bugs)
All All
: Low enhancement (vote)
: ---
Assigned To: Nobody - You can work on this!
Depends on:
  Show dependency treegraph
Reported: 2006-10-06 14:13 UTC by Duncan Harris
Modified: 2006-10-06 14:24 UTC (History)
0 users

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


Description Duncan Harris 2006-10-06 14:13:18 UTC
Currently, all of the special:whatlinkshere are listed by alphabetical order,
except for the newest entries at the bottom which are later sorted into the
alphabetical order (don't ask me how).

Unfortunately this results in the main namespace whatlinksheres (which are the
most important) getting all jumbled up with others from other namespaces,
especially the unimportant talk pages and user talk pages.

So can we please separate these additonally by namespace, so main namespace at
the top, then talk:, then the others in alphabetical order?

This would help sort out cross-namespace links, which are frowned upon (atleast
from main to another).
Comment 1 Aryeh Gregor (not reading bugmail, please e-mail directly) 2006-10-06 14:24:47 UTC
This might suggest a marginally different implementation, but still basically a

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

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