You are viewing an old version of this page. Return to the latest version.
BlueSpiceNamespaceManager
-
- Last edited 5 years ago by Florian Bäckmann
-
-
- No status information
Revision as of 13:08, 10 July 2020 by Mlink-rodrigue (talk | contribs) (Removed redirect to Reference:NamespaceManager)
Extension: BlueSpiceNamespaceManager
Overview | |||
---|---|---|---|
Description: | Administration interface for adding, editing and deleting namespaces. | ||
State: | stable | Dependency: | BlueSpice |
Developer: | HalloWelt | License: | GPL v3 only |
Type: | BlueSpice | Category: | Administration |
Edition: | BlueSpice free | ||
Features
NamespaceManager allows to manage all namespaces in the wiki.
Usage / features
The NamespaceManager is visible for users with admin permissions. The following actions are possible
- Creating a namespace
- Editing a namespace
- Deleting a namespace
- Turning features for a namespace on or off :
- Subpages: Activates the use of subpages, which introduce some hierarchical organization into wiki pages.
- Content namespace: Contents from this namespace will be prioritized in the search results.
- Category check: Warns users on page save that a page has no associated category.
- Secured page assignments:
- Page templates: allows page templates to be used.
- Visual editor: activates VisualEditor.
- Rating: displays a star-based rating option with the page title.
- Recommendations: displays a recommendations icon next to the page title.
- Read Confirmation: users that are assigned to this page need to confirm when they have read the page.
- Semantic MediaWiki: activates Semantic MediaWiki.
- Approval: creates draft and approved versions of pages.
- Sorting, filtering, and exporting of the table grid
Technical Information
Configuration
This extension offers no configurations.
Rights (permissions)
Users must have the namespacemanager-viewspecialpage permission in order to change the namespace configuration.
Requirements
NamespaceManager requires BlueSpiceFoundation.
More info
For detailed description and usage, visit our help page.