Last modified: 2008-08-06 19:41:58 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T17051, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 15051 - {{SUBPAGENAME}} and {{SUBPAGENAMEE}} don't work on all namespaces
{{SUBPAGENAME}} and {{SUBPAGENAMEE}} don't work on all namespaces
Status: RESOLVED INVALID
Product: MediaWiki
Classification: Unclassified
Parser (Other open bugs)
1.14.x
All All
: Normal enhancement (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2008-08-05 21:14 UTC by Platonides
Modified: 2008-08-06 19:41 UTC (History)
1 user (show)

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


Attachments
Remove code restricting to namespaces with subpages (761 bytes, patch)
2008-08-05 21:14 UTC, Platonides
Details

Description Platonides 2008-08-05 21:14:34 UTC
Created attachment 5121 [details]
Remove code restricting to namespaces with subpages

Ok, this is a documented 'feature': they only work on namespaces whith subpages enabled. But there's no reason they shouldn't work on the rest as well. SUBPAGENAME has a well-documented behaviour, its use means you want exactly the subpage, else you would be using {{PAGENAME}}
It also causes inconsistencies when moving templates from one wiki to another (eg. bug 15050).

PAtch attached which modifying {{SUBPAGENAME[E]}} behaviour, as well as {{BASEPAGENAME[E]}} to keep consistency. The only use on core and svn extensions of those two title functions is to implement these magic words.
Comment 1 Aryeh Gregor (not reading bugmail, please e-mail directly) 2008-08-05 21:17:55 UTC
{{PAGENAME}} means "return full page name unconditionally", {{SUBPAGENAME}} means "return subpage name if this is a subpage, otherwise return full page name".  Some expected behavior is not necessarily going to work if the namespace doesn't support subpages.  Not sure this is a good idea -- if you're moving pages to a namespace without subpages, you should either rename the (ex-)subpages to something that doesn't use subpage syntax, or enable subpages in the namespace.
Comment 2 Platonides 2008-08-05 22:56:04 UTC
It means that only because that's the way it has been coded. The name is {{SUBPAGENAME}} not {{SUBPAGENAMEIFNSALLOWSTHEM}} ;)
Bug 5167 just asks for a magic word to differentiate between page levels.

Comment 3 Brion Vibber 2008-08-06 19:41:58 UTC
Either subpages exist in the namespace, or they don't. They need to *not* be broken so pages like [[OS/2]] don't think they're subpages of [[OS]].

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


Navigation
Links