Last modified: 2012-11-04 18:27:37 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 2306 - Special:Whatlinkshere lists ordered by creation timestamp - ordering and filtering should be possible
Special:Whatlinkshere lists ordered by creation timestamp - ordering and filt...
Status: REOPENED
Product: MediaWiki
Classification: Unclassified
Special pages (Other open bugs)
unspecified
All All
: Low enhancement with 9 votes (vote)
: ---
Assigned To: Nobody - You can work on this!
http://nike.users.idler.fi/betawiki/s...
:
: 3780 9423 23763 (view as bug list)
Depends on:
Blocks: 4588
  Show dependency treegraph
 
Reported: 2005-06-03 13:27 UTC by lɛʁi לערי ריינהארט
Modified: 2012-11-04 18:27 UTC (History)
8 users (show)

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


Attachments

Description lɛʁi לערי ריינהארט 2005-06-03 13:27:21 UTC
URL
http://jadesukka.homelinux.org:8180/mediawiki15c/index.php?title=Special:Whatlinkshere&target=Template:TASKBODY/&limit=500&offset=0
see also
http://jadesukka.homelinux.org:8180/betawiki/Image:Image_namespace_sort_order_in_image_links_01.jpg
or
Image links at [[commons:Image:Jigokudani hotspring in Nagano Japan 001.jpg]]

The order in which the links are listed is probably "rcid".

enhancement request(s):
- minimal: as "magic watchlist"
- enhanced: filters for namespaces, etc.

Best regards Reinhardt
Comment 1 lɛʁi לערי ריינהארט 2005-10-23 10:24:13 UTC
*** Bug 3780 has been marked as a duplicate of this bug. ***
Comment 2 lɛʁi לערי ריינהארט 2006-01-17 23:45:29 UTC
Hallo!

Exchanged url because Betawiki has moved.

Bug 4588: Group pages by templates in list of file links on Image page

suggests that the code from "special:Whatlinkshere" should be reused in the file
links section in Image pages. It would be great to fix this before. Added Bug
4588 to the "blocks" list.

[[special:Watchlist/edit]] is not using the same code but there pages are
grouped by namespaces.

Filtering by namespace is possible at Special:Contributions, Special:Allpages
and Special:Recentchanges.
A common code is planed at
Bug 2468: The code that generates the namespace form for Special:Contributions,
Special:Allpages and Special:Recentchanges should be merged

See also: http://bugzilla.wikimedia.org/showdependencytree.cgi?id=2468 

best regards reinhardt [[user:gangleri]]
Comment 3 lɛʁi לערי ריינהארט 2006-05-05 08:49:19 UTC
updated url
Comment 4 Rob Church 2007-01-03 00:07:07 UTC
With our current schema, it would be impossible to do this in any kind of
efficient manner. I'm also inclined to question the utility of such a function,
even if it were implemented.
Comment 5 Yonatan Horan 2007-03-27 08:39:55 UTC
*** Bug 9423 has been marked as a duplicate of this bug. ***
Comment 6 Aaron Schulz 2008-05-27 05:02:35 UTC
They are listed by page_id, which generally correlates with creation time, except for restorations. A namespace filter seems to have been added for some time.
Comment 7 spacebirdy 2008-08-07 14:36:51 UTC
Reopened: it is possible to sort by namespace, but _not_ alphabetically, thus reopening bug again, since bug 3780 also links here and also other filters had been requested, thanks.
Comment 8 Dan Jacobson 2010-02-07 02:15:18 UTC
One visits [[Substance abuse]] and checking
[[Special:WhatLinksHere/Substance abuse]] one is convinced that [[Drug
abuse]] does not link to [[Substance abuse]]... it seems alphabetically
ordered, but that is just a coincidence for this page.

If MediaWiki insists on not making these lists alphabetically ordered,
then it should make it more obvious, so the user will remember to try
the 500 button. And while you are at it, make Category lists etc. etc.
also not alphabetically ordered, so the user doesn't get used to
thinking that all lists on MediaWiki are alphabetically ordered.
Comment 9 Dan Jacobson 2010-02-07 02:17:38 UTC
(In reply to comment #8)
> then it should make it more obvious
E.g., have at the top of the list some mention of what the ordering is by,
as there is no way the user could guess. That way the user would not get so despondent that there is apparently no logic.
Comment 10 Alexandre Emsenhuber [IAlex] 2010-06-03 18:32:41 UTC
*** Bug 23763 has been marked as a duplicate of this bug. ***
Comment 11 Scott Martin (http://enwp.org/user:scott) 2012-11-03 16:11:33 UTC
If the database can't produce results in alphabetical order, pump the results into a sortable table and let JavaScript do the work.

Table sorting code is ten a penny. Here's some, MIT-licensed:
http://yoast.com/articles/sortable-table/

(In reply to comment #4)
> I'm also inclined to question the utility of such a function,
> even if it were implemented.

People work through lists in order while fixing things. It's very hard to know how far you are through a task when the list is in apparently* completely random order.


* A normal user will have no idea what's going on inside the database or how it's ordering the results of this query.
Comment 12 MZMcBride 2012-11-03 16:17:20 UTC
(In reply to comment #11)
> If the database can't produce results in alphabetical order, pump the results
> into a sortable table and let JavaScript do the work.
> 
> Table sorting code is ten a penny. Here's some, MIT-licensed:
> http://yoast.com/articles/sortable-table/

MediaWiki already has JavaScript table sorting. The issue is that paginated results will make the sorting useless, isn't it?
Comment 13 Scott Martin (http://enwp.org/user:scott) 2012-11-04 18:27:37 UTC
(In reply to comment #12)
> MediaWiki already has JavaScript table sorting.

Ah. I had been under the misapprehension it was something template-based. Okay.

> The issue is that paginated results will make the sorting useless, isn't it?

Well, in many cases it's possible to see all the results of the query by bumping up the limit parameter, at which point sorting becomes valuable. 

It should be made clear that sorting applies only to the visible results.

"The following 50 pages link to Example. 
Sorted in alphabetical order. [change sort direction]
(previous 50 | next 50) (20 | 50 | 100 | 250 | 500)"

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


Navigation
Links