Last modified: 2009-05-15 11:06:57 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 18804 - Special pages use NS_MAIN instead of ContentNamespaces
Special pages use NS_MAIN instead of ContentNamespaces
Status: RESOLVED DUPLICATE of bug 8130
Product: MediaWiki
Classification: Unclassified
Special pages (Other open bugs)
All All
: Normal minor (vote)
: ---
Assigned To: Nobody - You can work on this!
Depends on:
  Show dependency treegraph
Reported: 2009-05-15 11:01 UTC by Lucas Garczewski
Modified: 2009-05-15 11:06 UTC (History)
1 user (show)

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

Patch (based on 1.14) (4.35 KB, patch)
2009-05-15 11:01 UTC, Lucas Garczewski

Description Lucas Garczewski 2009-05-15 11:01:30 UTC
Created attachment 6120 [details]
Patch (based on 1.14)

Various special pages use a hardcoded NS_MAIN value, where they should be using $wgContentNamespaces.

While this is not an issue at Wikimedia sites, it does affect other installations, including various Wikia sites, that use custom namespaces extensively.

I've attached a patch that corrects this in:
* SpecialFewestrevisions.php
* SpecialLonelypages.php
* SpecialUncategorizedpages.php
* SpecialWithoutinterwiki.php
* SpecialAncientpages.php
* SpecialDeadendpages.php

There might be other cases still. The patch is based on MW 1.14.
Comment 1 Roan Kattouw 2009-05-15 11:06:57 UTC

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

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