BlueSpiceNamespaceManager
-
- Last edited 5 years ago by Florian Bäckmann
-
-
- This page is a draft but has an approved version
Contents
What is BlueSpiceNamespaceManager?
BlueSpiceNamespaceManager displays information about the namespaces that are defined on the wiki. It also allows for creating, deleting and renaming namespaces, as well as chaning its settings.
Where to find the BlueSpiceNamespaceManager?
BlueSpiceNamespaceManager is availble from the right navigation, from "Global actions" tab, under "Management", or by directly accessing Special:NamespaceManger
.
The functionality of BlueSpiceNamespaceManager
Every namespace that exist on the wiki, has a corresponding talk namespace, eg. namespace Template has talk namespace Template_talk. Talk namespaces are ment to hold the discussions on the topics of the main namespace.
Basic functionality allows for:
- Creating new namespaces. New namespace can be added by clicking on the "Plus" icon above the table containing the namespaces. In the dialog that opens, enter the name for the new namespace and select desired options.
Creating a new namespace will automatically create a corresponding diskusssion namespace for it. ID of the new namespace cannot be choosen, it will be assigned automatically based on wiki settings and existing namespace IDs.
- Editing a namespace - namespace can be edited by clicking on the "wrench" icon, in the table row or above the table, when a namespace is selected. Names of talk namespaces
Deleting a namespace
The button can be used to delete a selected namespace. System namespaces and namespaces not created in the manager can not be deleted. You will be warned that you are about to delete the Namespace for good. If there are articles already in your namespace, you can choose what happens to them:
- they are deleted,
- they are moved to the mainspace,
- they are moved to the mainspace with a suffix "(from )"
Note: it is not possible to separately delete a discussion namespace, as this is associated with the corresponding custon namespace.
See also
Our reference page.