You are viewing an old version of this page. Return to the latest version.
Difference between revisions of "Reference:BlueSpiceExpiry"
(→User manual) |
(Tag: 2017 source edit) |
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 | ||
Features
Contents
Description[edit | edit source]
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[edit source]
This information
applies to BlueSpice 3 . Technical details for BlueSpice cloud can differ in some cases.
Requirements[edit source]
- MediaWiki: 1.31
- BlueSpiceFoundation: 3.2
BlueSpiceReminder: 3.2
Integrates into[edit source]
- BlueSpiceEchoConnector
- BlueSpiceReminder
- BlueSpiceSMWConnector
Special pages[edit
- Expiry
Permissions[edit
Requirements[edit | edit source]
User manual[edit | edit source]
For detailed description and usage please visit our user manual.
Try free our BlueSpice[edit | edit source]
| Name | Description | Role |
|---|---|---|
| expirearticle | Expire pages | admin, editor, maintenanceadmin |
| expiry-delete | Remove expiration from pages | admin, editor, maintenanceadmin |
Configuration[edit source]
| Name | Value |
|---|---|
| ExpiryEnablePDFWatermark | true |
| ExpiryEnablePageWatermark | true |
| ExpiryEnablePrintWatermark | true |
API Modules[edit source]
- bs-expiry-store
- bs-expiry-tasks
Hooks[edit source]
{{BSExtensionInfoboxBSExtensionInfo
|desc=<span style="color: #222222; font-family: sans-serif;">Pages can be marked as expired.</span>
|status=stable
|developer=HalloWelt
|type=BlueSpice
|edition=BlueSpice pro
|compatible=BlueSpice
|package=Reminder
|category=Quality Assurance
|docu=https://www.mediawiki.org/wiki/Extension:Expiry
}}
__TOC__
==Description==
'''Expiry''' marks , BlueSpice Farm, BlueSpice Cloud
|compatible=BlueSpice
|category=Quality Assurance
|license=GPL v3 only
|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.
==Usege / Features==
*An author can add an expiration date to an article.
*One week before expiration, the user will be notified by e-mailExpiry 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.
==Technical information==
===Configuration===
===Rights (permissions)===
===Requirements===
==User manual==
For detailed description and usage please visit our [https://en.help.bluespice.com/wiki/Extensions/Expiry user manual.]
==Try free our BlueSpice==
[https://en.demo.bluespice.com/wiki/Main_Page BlueSpice Demo.]
[[de:{{FULLPAGENAME}}]][[en:{{FULLPAGENAME}}]]
[[Category:Extension]]*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.
}}| (23 intermediate revisions by 5 users not shown) | |||
| Line 1: | Line 1: | ||
| − | {{ | + | {{BSExtensionInfo |
| − | |desc= | + | |desc=Pages can be marked as expired. |
|status=stable | |status=stable | ||
|developer=HalloWelt | |developer=HalloWelt | ||
|type=BlueSpice | |type=BlueSpice | ||
| − | |edition=BlueSpice pro | + | |edition=BlueSpice pro, BlueSpice Farm, BlueSpice Cloud |
|compatible=BlueSpice | |compatible=BlueSpice | ||
| − | |||
|category=Quality Assurance | |category=Quality Assurance | ||
| − | | | + | |license=GPL v3 only |
| − | + | |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. | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | = | ||
| − | |||
| − | '''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. | ||
| − | |||
| − | |||
*An author can add an expiration date to an article. | *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. | *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. | |
| − | + | }} | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||