BlueSpiceExpiry

Extension: BlueSpiceExpiry

Overview
Description:	Pages can be marked as expired.
State:	stable	Dependency:	BlueSpice
Developer:	HalloWelt	License:	GPL-3.0-onlyProperty "BSExtensionInfoLicense" (as page type) with input value "</br>GPL-3.0-only" contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process.
Type:	BlueSpice	Category:	Quality Assurance
Edition:	BlueSpice pro, BlueSpice Farm, BlueSpice Cloud
View help page

Features

Expiry marks — after a certain period of time — a chosen article as "obsolete". The article can be updated by editing or by confirming that the article is still up-to-date. Expiry is the ideal basis for an archiving system. Outdated articles can be moved to an archive after being queried.

• An author can add an expiration date to an article.
• The expiry date can automatically be postponed to the future for a specific period of time.
• Several authors: There can only be one expiration date. The user who originally entered the expiration date will be informed of the change.
• There is no limit to the number of expiration dates with respect to users.

Technical Information

This information applies to BlueSpice 3 . Technical details for BlueSpice cloud can differ in some cases.

Requirements

• MediaWiki: 1.31

• BlueSpiceFoundation: 3.2

BlueSpiceReminder: 3.2

Integrates into

• BlueSpiceEchoConnector
• BlueSpiceReminder
• BlueSpiceSMWConnector

Special pages

• Expiry

Permissions

Name	Description	Role
expirearticle	Expire pages	admin, editor, maintenanceadmin
expiry-delete	Remove expiration from pages	admin, editor, maintenanceadmin

Configuration

Name	Value
ExpiryEnablePDFWatermark	true
ExpiryEnablePageWatermark	true
ExpiryEnablePrintWatermark	true

API Modules

• bs-expiry-store
• bs-expiry-tasks

Hooks

• BSUEModulePDFBeforeAddingStyleBlocks
• BSUEModulePDFgetPage
• BeforePageDisplay
• LoadExtensionSchemaUpdates
• SkinTemplateNavigation
• SkinTemplateOutputPageBeforeExec
• wgQueryPages