hw>Mlink-rodrigue No edit summary |
m (Text replacement - "BlueSpice Cloud" to "BlueSpice cloud") |
||
| (5 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
{{BSExtensionInfo | {{BSExtensionInfo | ||
|status=stable | |status=stable | ||
|developer=HalloWelt | |developer=HalloWelt | ||
|type=BlueSpice | |type=BlueSpice | ||
|edition=BlueSpice pro, BlueSpice | |edition=BlueSpice pro, BlueSpice farm, BlueSpice cloud | ||
|compatible=BlueSpice | |compatible=BlueSpice | ||
|category=Quality Assurance | |category=Quality Assurance | ||
| Line 14: | Line 13: | ||
*Several authors: There can only be one expiration date. The user who originally entered the expiration date will be informed of the change. | *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. | *There is no limit to the number of expiration dates with respect to users. | ||
|desc=Pages can be marked as expired. | |||
}} | |||
{{wcagCheck | |||
|wcagStatus=2-testing complete | |||
|wcagCheckedfor=Web, Authoring tool | |||
|wcagTestdate=2022-08-05 | |||
|wcagLevel=AA | |||
|wcagSupport=supports | |||
|wcagComments=[https://support.hallowelt.com/issues/27714 erm:27714] (fix: 4.2.4) | |||
|extensionType=core | |||
|extensionFocus=reader | |||
}} | }} | ||
Latest revision as of 10:51, 7 June 2024
Extension: BlueSpiceExpiry
| 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: | 4.1+ |
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 4. Technical details for BlueSpice cloud can differ in some cases.
Requirements
- MediaWiki: 1.39.0
- BlueSpiceFoundation: 4.3
BlueSpiceReminder: 4.3
Integrates into
- BlueSpiceEchoConnector
- BlueSpiceReminder
- BlueSpiceSMWConnector
- Notifications
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
Accessibility
| Test status: | 2-testing complete |
|---|---|
| Checked for: | Web, Authoring tool |
| Last test date: | 2022-08-05 |
| WCAG level: | AA |
| WCAG support: | supports |
| Comments: |
erm:27714 (fix: 4.2.4) |
| Extension type: | core |
| Extension focus: | reader |
