Last modified: 2010-05-15 15:48:27 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 10912 - Sortable backlinks
Sortable backlinks
Status: RESOLVED INVALID
Product: MediaWiki
Classification: Unclassified
Special pages (Other open bugs)
1.9.x
All All
: Normal enhancement (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2007-08-13 23:57 UTC by Eep²
Modified: 2010-05-15 15:48 UTC (History)
0 users

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


Attachments

Description Eep² 2007-08-13 23:57:54 UTC
I've added rudimentary sorting to "Whatlinkshere" (backlinks) results (see http://www.tnlc.com/wiki/index.php?title=Special:Whatlinkshere/Template:effect for an example) but this (and other) results page(s) need some tweaking:

* Don't show the "View (previous 50) (next 50) (20 | 50 | 100 | 250 | 500)." lines if there aren't more than 50 (or whatever is configured in prefs) results. Also, it's not a sentence so the period should be removed (which can be changed in MediaWiki:Viewprevnext at least--case-sensitive and won't take effect even if redirected to upper case version until it's re-edited, annoyingly).

* I assume the initial sorting is by database table ID/key so a table column for that should be added (I couldn't figure it out), and the "(inclusion)", "(redirect)", and other "description" text should be in a separate column from the page name (without the parentheses).

*Show the total result count (like category lists do); I can get the total results but not for each page (tried using $rows--returns "Array"--and $row--returns nothing--but they don't work).
Comment 1 Rob Church 2007-08-14 00:00:02 UTC
Please file one separate issue per bug and use clear descriptions of each.
Comment 2 Eep² 2007-08-14 00:02:35 UTC
It's too annoying having to do that--the bug submission form needs a way to add multiple issues with common form elements...
Comment 3 Rob Church 2007-08-14 00:13:13 UTC
Complain to the people who write the bug tracking software, then.

Your bug report contains multiple distinct issues, each of which can be addressed at separate times, and is therefore subject to separate tracking. It isn't possible to track individual parts of a single bug report.

At the moment, we show paging links on eligible pages regardless of the number of rows, which presents a consistent interface. If this is going to change, it needs to change for all pages. It's not clear whether it *should* change.

There's an existing bug for filtering on inclusions, redirects, etc. - see bug 6934.

Obtaining the total result count might well be more expensive than it seems, which is a reason such pages often don't have them; the best that can be obtained is sometimes the number of entries on the page.

I removed the '.' in r24763. I'm ignoring the gripe about the behaviour of the message cache and titles.
Comment 4 Eep² 2007-08-14 00:33:42 UTC
How/where do I submit Bugzilla enhancement requests then? I thought it was made especially for MediaWiki...

Why clutter up the UI with unnecessary controls? Seems like the case for change is obvious to me... It's like when devs leave in disabled menu options that can't be clicked yet mindlessly fill up menus (and enabled branching menus with all disabled menu options under them is especially annoying). Efficiency in design...design efficiently.

The filtering bug is different from what I am proposing.

Why would obtaining the total result count be more expensnive than it seems when it's already done within the script? All I'm proposing is outputting the result for the user...

Why ignore the "gripe" when it's valid? With lowercase pages enabled (in localsettings.php via "$wgCapitalLinks = false;"), MediaWiki, although showing the original message text, won't actually USE that lowercase page's text if it's changed. Lowercase "MediaWiki:" system message pages should automatically redirect to 1st-letter uppercase pages by default like MediaWiki does for namespaces: "template:test" will auto-redirect to "Template:test" (and to "Template:Test" with lowercase links off).

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


Navigation
Links