Release status: experimental
|Description||Allows administrator to define additional NS tabs besides Subject and Talk|
|Author(s)||Pavel Selitskas (Wizardisttalk)|
|Latest version||0.1 (2013-02-15)|
(since 13cecf9 for query support)
|License||GNU General Public License 2.0 or later|
Translate the NamespaceRelations extension if it is available at translatewiki.net
|Check usage and version matrix; code metrics|
The NamespaceRelations extension allows an administrator to define additional namespace tabs besides Subject and Talk tabs in the interface. Whether the user is browsing Subject, Talk, or additional tabs, they will see the tabs all together.
The extension can be retrieved directly from Git [?]:
- Browse code
- Some extensions have tags for stable releases.
- Browse tags
- Select the tag
- Click "snapshot"
- Each branch is associated with a past MediaWiki release. There is also a "master" branch containing the latest alpha version (might require an alpha version of MediaWiki).
- Browse branches
- Select a branch name
- Click "Continue"
Extract the snapshot and place it in the extensions/NamespaceRelations/ directory of your MediaWiki installation.
If you are familiar with git and have shell access to your server, you can also obtain the extension as follows:
cd extensions/ git clone
- Download and place the file(s) in a directory called
- Add the following code at the bottom of your LocalSettings.php:
- Done - Navigate to Special:Version on your wiki to verify that the extension is successfully installed.
NamespaceRelations is configured solely by defining $wgNamespaceRelations. The supported format and parameters are as follows:
$wgNamespaceRelations = array( 'key1' => array( 'namespace' => NS_MAIN, 'target' => 12, 'inMainPage' => true, 'query' => 'param1=value1¶m2=value2', 'weight' => 5, 'hideTalk' => true, 'customTarget' => 'Test/$1' ), // etc. );
- A key (ID) that is used in many places. It's the ID that is used in HTML rendering for actual element ID. Besides, it's used to find an appropriate message for the tab (via nstab-extra-key1).
- Namespace ID where the tab should be visible.
- Namespace ID where the tab should link.
- By default, if the tab is attached to NS_MAIN, the tab won't be visible on Main Page (imitating Wikinews Opinions tab behvaiour). However, this may be overridden by setting inMainPage to true. This parameter isn't obligatory and is intended only for namespace = NS_MAIN.
- Query string which action=edit&redlink=1 is attached to if the target page doesn't exist. Works since MediaWiki 1.21alpha (13cecf9).
- Sorting weight. Subject and Talk tabs receive 10 and 20 appropriately; if weight is not set, every custom tab receives +10 points starting from 30 (30 for the first custom tab, 40 for the next, etc.). This parameter allows to place custom tabs in almost every position relative to Subject, Talk and other custom tabs.
- Hide Talk tab.
- Custom target title. $1 is the base title (for example, "Page" will link to "Test/Page" in the target namespace.
You can define multiple tabs per one namespace which link to different targets, but you cannot define multiple tabs for different namespaces which linking to the same target — it creates ambiguous situation where we have 2+ Subject/Talk tabs (creating both — actually 4 tabs —– seems excessive). On the other hand, the first case (1 namespace → 2+ targets) works just fine.
$wgNamespaceRelations = array( 'comments' => array( 'namespace' => 0, 'target' => 102, 'query' => 'preload=Wikinews:Commentary_pages_on_news_events/body&editintro=Template:Editintro_as-is' ) );
The messages are: nstab-extra-comments for caption, tooltip-ca-comments for tooltip.
$wgNamespaceRelations = array( 'citations' => array( 'namespace' => 0, 'target' => 114 ), 'documentation' => array( 'namespace' => 10, 'target' => 10, 'customTarget' => '$1/doc' ) );
The messages are: nstab-extra-citations and nstab-extra-documentation for captions, tooltip-ca-citations and tooltip-ca-documentation for tooltips, respectively.
- attached namespaces should be treated the same way as talk pages when page moving takes place (that being said, when a page is moved and a special checkbox marked, the attached page is also renamed)