m (Text replacement - "BlueSpice Farm" to "BlueSpice farm") |
m (Text replacement - "BlueSpice Cloud" to "BlueSpice cloud") |
||
Line 4: | Line 4: | ||
|developer=HalloWelt | |developer=HalloWelt | ||
|type=BlueSpice | |type=BlueSpice | ||
|edition=BlueSpice free, BlueSpice pro, BlueSpice farm, BlueSpice | |edition=BlueSpice free, BlueSpice pro, BlueSpice farm, BlueSpice cloud | ||
|compatible=BlueSpice | |compatible=BlueSpice | ||
|category=Content Structuring | |category=Content Structuring |
Latest revision as of 10:51, 7 June 2024
Extension: BlueSpicePageTemplates
Overview | |||
---|---|---|---|
Description: |
Displays a list of templates marked as page templates | ||
State: | stable | Dependency: | BlueSpice |
Developer: | HalloWelt | License: | GPL-3.0-only |
Type: | BlueSpice | Category: | Content Structuring |
Edition: | BlueSpice free, BlueSpice pro, BlueSpice farm, BlueSpice cloud | Version: | 4.1+ |
Features
BlueSpicePageTemplates allows users to create new pages from predefined templates to start with a basic page structure.
- Create a template (with headers, categories, boxes and other content) in the template namespace.
- Create a page template using the special page Special_PageTemplatesAdmin give the page template a name and a description.
- Each template should be assigned a template from the "Template" namespace that represents the structure of a document.
- Page templates can be assigned to a particular namespace, so that a certain template will only appear when creating pages in that namespace.
- The page template is shown as a choice when a new page is created.
Some aspects of this extension can be configured on the page Special:BlueSpiceConfigManager, under "Page templates". Here, wiki administrators can:
- Force a target namespace for the page that was created from the template
- Hide default templates
Default page templates
Since BlueSpice 4.2, several default page templates are provided through the Page templates manager. The templates themselves are located in the "Template" namespace and prefixed with the letters "PT" (example:Template:PT How-to article).
For more information on how to add or remove available page templates, see the help page.
Updates to the default templates:
If you have edited the default page templates in your wiki, they will not be overwritten during any BlueSpice upgrades. It is possible, however, that the default templates are added to the Page templates manager again after an update. You can simply remove the unwanted templates again.
An update to the current default version of all page templates can be forced with the following command from the wiki root:
php maintenance/update.php --quick --force
Technical Information
This information applies to BlueSpice 4. Technical details for BlueSpice cloud can differ in some cases.
Requirements
- MediaWiki: 1.39.0
- BlueSpiceFoundation: 4.3
Integrates into
- MWStakeContentProvisioner
Special pages
- PageTemplatesAdmin
Permissions
Name | Description | Role |
---|---|---|
pagetemplatesadmin-viewspecialpage | Access to the Special:PageTemplatesAdmin special page, where page templates can be managed | admin, maintenanceadmin, structuremanager |
Configuration
Name | Value |
---|---|
PageTemplatesExcludeNs | array ( 0 => -2, 1 => -1, 2 => 6, 3 => 7, 4 => 8, 5 => 9, 6 => 10, 7 => 11, 8 => 14, 9 => 15, ) |
PageTemplatesForceNamespace | false |
PageTemplatesHideDefaults | false |
PageTemplatesHideIfNotInTargetNs | true |
API Modules
- bs-pagetemplate-tags-store
- bs-pagetemplates-store
- bs-pagetemplates-tasks
Hooks
- BSApiNamespaceStoreMakeData
- BSUEModulePDFBeforeAddingStyleBlocks
- BSUsageTrackerRegisterCollectors
- BeforePageDisplay
- HtmlPageLinkRendererBegin
- LoadExtensionSchemaUpdates
- MWStakeCommonUIRegisterSkinSlotComponents
- MediaWikiPerformAction
- MessagesPreLoad
- NamespaceManager::editNamespace
- NamespaceManager::getMetaFields
- NamespaceManagerBeforePersistSettings
- SkinTemplateNavigation::Universal
Accessibility
Test status: | 2-testing complete |
---|---|
Checked for: | Web, Authoring tool |
Last test date: | 2022-08-05 |
WCAG level: | AA |
WCAG support: | partially supports (workaround: no) |
Comments: |
keyboard access works. Screenreader: Extjs: Pagination in grids not announcing button labels at top and pagination buttons at bottom; actions menu has no keyboard support. switching between browse/focus modes enables finding out how many pages there are and moving to the next page. |
Extension type: | core |
Extension focus: | admin |