Last modified: 2013-02-13 12:46:58 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 4204 - Consolidate special pages with namespace selector
Consolidate special pages with namespace selector
Status: NEW
Product: MediaWiki
Classification: Unclassified
Special pages (Other open bugs)
All All
: Low enhancement with 5 votes (vote)
: ---
Assigned To: Nobody - You can work on this!
: 5864 6268 12689 18273 29083 (view as bug list)
Depends on: 8516 39660 2468 8130
  Show dependency treegraph
Reported: 2005-12-07 09:41 UTC by Joel Nothman
Modified: 2013-02-13 12:46 UTC (History)
9 users (show)

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


Description Joel Nothman 2005-12-07 09:41:15 UTC
There is a namespace selector on [[Special:Recentchanges]]; why nowhere else?

It could be used to consolidate:
- {All pages, Categories, File list} into "Pages"
- {Most linked to categories, Most linked to images, Most linked to pages} into 
 "Most linked to pages"
- {Uncategorized categories, Uncategorized pages} into "Uncategorised pages"
- {Unused categories, Unused files, Orphaned pages} into "Orphaned pages"
- {Wanted categories, Wanted pages} into "Wanted pages"

It will also make Pages with most categories, Pages with most revisions, New 
pages, Short pages, Oldest articles be more generic.

And even these could ALL be combined into ONE page with subpages, or a 

The listings could provide more info for the given namespace, ie links to the 
image when referring to the Image: namespace.

Not only will this allow for less repetitive code, it will stop the ambiguity 
between the terms "pages"/"articles" and "files"/"images".

If nothing else, it will save a lot of time adding the same enhancements to 
multiple different special pages.
Comment 1 Ævar Arnfjörð Bjarmason 2005-12-07 09:51:50 UTC
One reason why we don't offer the option of select namespaces on certain pages
is that doing so could make them superexpensive as the indexes in place to
generate them would no longer be effective, one example of this could be
Special:Shortpages (let's presume for the sake of argument that the page table
didn't have a namespace index), generating a list of the 100 shortest pages with
an index on page_len would be inexpensive but allowing users to select a
namespace with no index on page_namespace could in a worst case scenario result
in a scan of hundreds of thousands of rows for a namespace that not a lot of
pages exist in (like Portal_talk).

Another reason for it might be that simply noone has bothered coding it yet, or
it's something that's inherantly much harder to do due to a certain structuring
in the code. One example of this is Wantedpages/Wantedcategories, the querycache
object currently works in a way that makes it impossible to have two different
SQL queries for a single special page based on arguments given to it if you want
to cache it.
Comment 2 Joel Nothman 2005-12-07 10:57:18 UTC
If caching is a problem, the same can be done by subpages instead of 
arguments, ie Special:Pages/Wanted/Category. I presume here querycache would 
allow different SQL queries?
Comment 3 Filip Maljkovic [Dungodung] 2006-06-10 23:09:39 UTC
*** Bug 6268 has been marked as a duplicate of this bug. ***
Comment 4 Lejonel 2008-01-23 11:14:29 UTC
*** Bug 12689 has been marked as a duplicate of this bug. ***
Comment 5 Dan Jacobson 2009-05-18 13:05:11 UTC
*** Bug 5864 has been marked as a duplicate of this bug. ***
Comment 6 Dan Jacobson 2009-05-18 13:06:19 UTC
*** Bug 18273 has been marked as a duplicate of this bug. ***
Comment 7 Alexandre Emsenhuber [IAlex] 2011-05-31 11:16:54 UTC
*** Bug 29083 has been marked as a duplicate of this bug. ***
Comment 8 MZMcBride 2012-08-26 16:21:00 UTC
If people are serious about seeing this bug resolved, it should have an accompanying RFC: <>. This is going to require some thinking and planning.
Comment 9 Nemo 2012-08-26 20:48:28 UTC
Let's call bug 39660 a blocker (an instance of this): I think the dropdown is the best solution for it.

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