Last modified: 2010-05-15 15:59:36 UTC
When a page in a custom namespace becomes orphaned, it does not show up on the orphaned pages list. The query in includes/SpecialLonelypages.php is hardcoded to only show pages in the NS_MAIN namespace. Similar situations apply to Special:Ancientpages, Special:Fewestrevisions, Special:Mostcategories, Special:Mostrevisions, Special:Shortpages and probably more.
Requested fix: Include a namespace selection box either like the one found on Special:Allpages or the one in Special:Search, so that users can select what namespaces they want to search for orphaned pages.
I'd like to suggest an additional fix. Perhaps instead of having NS_MAIN hard-coded into the query, there should be a default of all $wgContentNamespaces ''and'' a namespace selector (that can override and display ''all namespaces'' regardless of $wgContentNamespaces.
So the menu would have the options:
* User talk
Thumbs-up? -down? It will probably require code a bit more complex in the special page query generation, but I think (as, apparently, does CodeCat) that it would be worthwhile to see pages from other namespaces that are orphaned or very old, etc.
Agreed. Pages in other namespaces can get lost just as easily as normal pages, so I'm wondering why this wasn't even suggested much sooner. Big sites like Wikipedia must have hundreds of pages that got lost but nobody knows about...
That said, I like the suggestion of adding (content) to the list. In fact, it would be nice if it were added to existing pages that use such a list as well.
Yes, probably ''thousands'' of pages at that.
Only problem with suggesting (content) be added to the other lists is that it should really be a new bug. Oh look, bug 12702 just got entered! :D
(In reply to comment #2)
> Agreed. Pages in other namespaces can get lost just as easily as normal pages,
> so I'm wondering why this wasn't even suggested much sooner.
It was suggested before.
*** This bug has been marked as a duplicate of bug 4204 ***