| Overview | |||
|---|---|---|---|
| Description: |
Pages can be marked as expired. | ||
| State: | stable | Dependency: | BlueSpice |
| Developer: | HalloWelt | License: | GPL-3.0-only |
| Type: | BlueSpice | Category: | Quality Assurance |
| Edition: | BlueSpice pro, BlueSpice farm, BlueSpice cloud | Version: | |
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
Technical details for BlueSpice cloud can differ in some cases.
Requirements
- MediaWiki: 1.43.0
- BlueSpiceFoundation: 5.0.0
- BlueSpiceReminder: 5.0.0
- OOJSPlus: 3.0.0
Integrates into
- BlueSpiceEchoConnector
- BlueSpiceReminder
- BlueSpiceSMWConnector
- NotifyMe
- PDFCreator
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 |
API Modules
- bs-expiry-store
- bs-expiry-tasks
Hooks
- BeforePageDisplay
- BlueSpiceDiscoveryTemplateDataProviderAfterInit
- LoadExtensionSchemaUpdates
- MWStakeCommonUIRegisterSkinSlotComponents
- SkinTemplateNavigation::Universal
- StandardDialogsRegisterPageInfoPanelModules
- wgQueryPages
Notifications
| Name | Buckets |
|---|---|
| bs-expiry-today | qm |
| bs-expiry-one-week | qm |
