8.1 Approval

Latest revision as of 13:59, 6 November 2024

ContentStabilization is available from BlueSpice 4.3. Up to version 4.2, approvals are handled by the extension FlaggedRevs.

The ContentStabilization extension is a MediaWiki extension that activates an approval mechanism. New versions of a page are initially marked as drafts. These remain in place until a user with approval rights reviews and approves the page.

Enable page approval

Drafts are activated via the namespace administration. A user with administrator rights checks whether Approval is enabled for a namespace. This is done under Global Actions > Administration > Namespaces.

Click the edit icon (wrench) in the Actions column. The namespace dialog opens. Select approval and click Done.

Activated Approval feature for a namespace

Existing Pages

After Approval is activated for a namespace, all existing pages in the namespace appear in draft mode. The pages now show the status First draft.

First draft

By default, the page status is displayed in the title area of every page with approval function .

Alternatively, the status info can be moved below the page content from the Config manager.

First drafts

When a new page is created and saved for the first time, it will appear as first draft. By default, first drafts are visible to all users with read permissions. However, this can be restricted to individual user groups from the Config manager.

Drafts

If a page is edited and saved multiple times in draft mode, each edit is logged in the page history:

Drafts are shown in the revision history

Drafts are highlighted in color in the version history. In addition, they are marked with "Release pending".

Accepting a page

A user with reviewer permissions can approve the page from the status message in the title area of the page. The approval comment is logged in the page's version history.

Approval from the title area

The new approval status is shown accordingly in the title area.

Approved page status

Configuration

The following settings are made in the Config manager in combination with namespace settings.

Changes to templates, embedded files and transclusions

If a page uses templates or contains other files such as images and embedded PDFs, or if content from other pages is transcluded and modified after the page was approved, those changes must also be approved. There are two mechanisms to accomplish the approval:

The embedded resource is in a namespace without approval mechanism: If the embedded resource is in a namespace without its own approval function, the approved version of the page shows the resource version that was embedded at the time of the page approval. An implicit draft version shows the most recent version of the embedded resource.
The embedded resource is in a namespace with approval mechanism: The approval is done directly for the resource itself to avoid approval on all affected content pages.

Important!If the approval mechanism is activated in a resource namespace (e.g. Template, File) in retrospect, all existing pages in the resource namespace are then in first draft. If the wiki is configured so that not all users can see drafts, the resources may need to be initially approved via server script if this cannot be accomplished manually.

About approvals via server script.

Setting

Behaviour of the approved content page -

No resource approval mechanism

Resource without approval feature

Behaviour of the approved content page -

Approval mechanism via resource namespace

Resource with approval feature

Versions that were current at the time of approval

(Default)

Resource display:

the embedded version at the time of approval is shown on the approved page:

Approved page version with the version of the resource that was embedded at the time of page approval
an implicit draft with the latest version of the resource exists:

Page draft due to change of embedded resource

Resource approval:

the implicit draft must be approved on the content page. If the resource is embedded/linked on multiple pages in the wiki, all pages must be approved separately.

Resource display:

the embedded version at the time of approval is shown:

Approved page version with the version of the resource that was valid at the time of page approval
an implicit draft with the latest version of the resource exists:

Page draft due to change of embedded resource

Resource approval:

The implicit draft can only be approved on the content page. If the resource is embedded on multiple pages in the wiki, all pages must be approved separately.

Approved versions of included pages

This setting has no effect if the resource itself has no approval mechanism. The page shows the same behavior as for "Versions that were current at the time of approval" (see above).

Resource display:

the approved version of the resource is shown on page.

The currently approved version of the resource is shown.

Resource approval:

Takes place exclusively via the resource itself. The page contains no indication whether a draft version of the resource exists.

Current versions of included pages

Resource display:

the current version of the resource is shown:

Approved page with the current version of the resource

Resource approval:

the resource itself cannot be approved

Resource display:

the current version of the resource is shown:

Approved page with the current version of the resource

Resource approval:

The approval status of the resource has no effect on the page and should therefore not be used in combination with an activated approval mechanism in the resource namespace.

Reading permissions for drafts

By default, all users can see a page's drafts, including users with only read permissions.

To hide drafts from users, the user group must be removed from the configuration. This setting then applies to the entire wiki and cannot be further restricted to specific namespaces.

An administrator changes the groups that can see drafts in the Show draft versions for the following groups box.

Warning!If the group user is off is removed from the configuration, users in this group cannot see draft versions even if they are assigned a workflow task.

After removing the group user, the desired group(s ), e.g. B. the group editor, can be added to the configuration and saved.

Note:If no user groups are specified in the configuration field, even users with share rights and sysop users will not see a visual status indicator of the page. Instead, you have access to drafts through the page's history.

In order for administrators to see the status directly on the page, they must be added to a group listed here in the configuration.

Read permissions for first drafts

By default, first drafts are visible to all users who have read permissions in a namespace. However, if first drafts are only visible to those users who can generally view page drafts, this can be done in the configuration management by selecting Allow viewing of first draft version for users who can normally not see drafts to be disabled.

Summary: Read Permissions for Draft Pages

Define groups:

Group user: Only the user groups that have been given this right in the configuration management can see first drafts and other drafts. By default, this is the user group (=all users who are logged into the wiki and have the appropriate reading rights in a namespace).
Adjust groups: In the configuration management, the reading rights for (first) drafts can be restricted to other groups.
Group sysop: Users in group sysop can always view drafts through the history. The sysop group can therefore not be set explicitly in the configuration. If sysop users can directly see the approval status on the page, they need to be added to a group with read permissions for drafts.

Export draft pages:

Single page export: Users with reading rights on a draft page can print it directly as a PDF.
Book export: Only approved pages are exported. If there is only a first draft of a page, it will be exported. Exception: If the book is printed by a user who does not have access to the first draft, the first draft will not be printed out in the book. Instead, the PDF shows the following message:

Permissions error PDF export

Effects on Semantic MediaWiki properties

If a namespace has SemanticMediaWiki Semantic MediaWiki activated, the following SMW queries are available depending on the approval status of the page:

Document state	Available properties
First draft	Current values
Approved	Values of the approved (stable) version
Draft	Values of the approved (stable) version (default setting)
Implicit draft^[1]	Values of the approved (stable) version

The availability of the semantic properties is determined by the following configuration setting:

$bsgFlaggedRevsConnectorStabilizeSMWPropertyValues = true;

The value for this setting can be set to false in the LocalSettings.php of the server file system. If set to false, the property values of the draft version are used for semantic queries instead of the values for the stable version.

Quality management overview

The Special page Special:Quality_management_overview allows all users with reviewer permissions to view and filter a list of wiki pages and their review status. Pages for which a user does not have read permissions are not shown.

Special page "Quality management overview"

Approving a page when the title area is hidden

When the title area is hidden, you can approve the page from the ...all actions menu:

Switch to the draft version of the page (this not necessary when the page is in First draft status). v4.3.2+

Switching to first draft url

Before v.4.3.2, this switch-link is not available. In that case, go to the page history and click on the latest time stamp to switch to the draft version of the page.

The latest time stamp in the page history links to the draft page.
Approve the page via ...all actions -> Approve page .

All actions menu with approval link highlighted

Related info

↑ An approved page has an implicit draft, if there have been changes to embedded resources (e.g., a template or an image) since the last page approval.

Technical Reference: ContentStabilization

To submit feedback about this documentation, visit our community forum.

[1] An approved page has an implicit draft, if there have been changes to embedded resources (e.g., a template or an image) since the last page approval.

[1]

@@ Line 2: / Line 2: @@
 {{BSVersion|bsvFrom=4.3|bsvTo=|bsvFeature=ContentStabilization|info=Up to version 4.2, approvals are handled by the extension [[Manual:Extension/FlaggedRevs|FlaggedRevs]].}}
-The '''ContentStabilization''' extension is a MediaWiki extension that enables a sharing mechanism. New versions of a page are initially marked as drafts. These remain in place until a user with sharing rights reviews and approves the page.
+The '''ContentStabilization''' extension is a MediaWiki extension that activates an approval mechanism. New versions of a page are initially marked as drafts. These remain in place until a user with approval rights reviews and approves the page.
-==Enable page sharing==
+==Enable page approval==
-Drafts are activated via the namespace administration. A user with administrator rights checks whether ''sharing'' is enabled for a namespace. This is done under ''Global Actions > Administration > Namespace Administration''. Click the edit icon (wrench) in the ''Actions'' column. The namespace dialog opens. Select Sharing and click ''Done''.
+Drafts are activated via the namespace administration. A user with administrator rights checks whether A''pproval'' is enabled for a namespace. This is done under ''Global Actions > Administration > Namespaces''.
-[[File:Manual:release-namespace.png|centered|mini|450x450px|enable sharing for a namespace|alternative text=enable sharing for a namespace]]
+Click the edit icon (wrench) in the ''Actions'' column. The namespace dialog opens. Select approval and click ''Done''.
+[[File:Manual:approval-namespace.png|alt=Namespace settings screen|center|thumb|450x450px|Activated Approval feature for a namespace]]
 ===Existing Pages===
-When ''sharing'' is activated for a namespace, all existing pages in the namespace are put into draft mode. The pages are now all in status ''First Draft.''[[File:Manual:flaggedrevs-first draft.png|centered|300x300px|mini|First Draft|alternative text=First Draft]]By default, the page status is displayed in the title area of every page with approval function .
+After ''Approval'' is activated for a namespace, all existing pages in the namespace appear in  draft mode. The pages now show the status ''First draft.''
+[[File:Manual:flaggedrevs-firstdraft.png|alt=First draft indicator in the title area|center|thumb|250x250px|First draft]]
-Alternatively, the view can be moved below the page content via the [[Manual:Extension/BlueSpiceConfigManager#Positioning of skin elements|Configuration management]].
-===First draft===
-When a new page is created and saved for the first time, it will appear as '''First Draft'''. By default, first drafts are visible to all users with read permissions. However, via a [[Page Draft:Extension/ContentStabilization#Setting in Configuration Management|Setting in Configuration Management]] this can be restricted to users who can see drafts on the wiki.
-=== Drafts ===
-If a page is edited and saved multiple times in draft mode, each edit is logged in the revision history:<br />[[File:Manual:flaggedrevs-revisions.png|centered|650x650px|mini|draft revisions in the revision history|alternative text=draft revisions in the History]]
+By default, the page status is displayed in the title area of every page with approval function .
-Drafts are framed and highlighted in color in the version history. In addition, they are marked with "Release pending".
+Alternatively, the status info can be moved below the page content from the [[Manual:Extension/BlueSpiceConfigManager#Positioning of skin elements|Config manager]].
-==Accepting a page==
+===First drafts===
-A user with [[Manual:Extension/BlueSpicePermissionManager|Release rights]] can release the page via the release function in the title area of the page. The release comment is logged in the page's version history.<br />
+When a new page is created and saved for the first time, it will appear as '''first draft'''. By default, first drafts are visible to all users with read permissions. However,  this can be restricted to individual user groups from the [[Manual:Extension/BlueSpiceConfigManager#ContentStabilization|Config manager.]]
-[[File:Manual:Share Page.png|centered|277x277px|mini|Page share via title area]]
+===Drafts===
+If a page is edited and saved multiple times in draft mode, each edit is logged in the page history:
+[[File:Manual:flaggedrevs-revisions.png|alt=Highlighted revisions in the page history|center|thumb|550x550px|Drafts are shown in the revision history]]
+<br />
+Drafts are highlighted in color in the version history. In addition, they are marked with "Release pending".
-The new approval status is displayed accordingly in the title area.<br />[[File:Manual:a2.png|centered|350x350px|mini|Approval status display|alternative text=Approval status display]]
+==Accepting a page==
+A user with [[Manual:Extension/BlueSpicePermissionManager|reviewer permissions]] can approve the page  from the status message in the title area of the page. The approval comment is logged in the page's version history.<br />
+[[File:Manual:flaggedrevs-acceptdraft.png|alt=approval feature in the title area|center|thumb|250x250px|Approval from the title area]]
+The new approval status is shown accordingly in the title area.
+[[File:Manual:flagged-revs-accepted.png|alt=Approval status indication|center|thumb|Approved page status]]
+<br />
 ==Configuration==
+The following settings are made in the [[Manual:Extension/BlueSpiceConfigManager#ContentStabilization|Config manager]]  in combination with namespace settings.
 ===Changes to templates, embedded files and transclusions===
-If a page uses templates or contains other files such as images and embedded PDFs, or if content from other pages is transcluded and modified after the page was approved, those changes must also be approved. There are two ways to do the sharing:
+If a page uses templates or contains other files such as images and embedded PDFs, or if content from other pages is transcluded and modified after the page was approved, those changes must also be approved. There are two mechanisms to accomplish the approval:
-#'''The embedded resource is in a namespace without a release mechanism:''' If the embedded resource is in a namespace without its own release function, the released version of the page shows the resource version at the time the page was released. Similarly, the draft version shows the most recent version of the embedded resource. <br />
-#'''The embedded resource is in a namespace with a sharing mechanism:''' Sharing is done directly at the resource to avoid sharing on all affected content pages.{{Note box|boxtype=Important|icon=|Note text= If the release mechanism is subsequently activated in a resource namespace (e.g. template, file), all existing pages are moved to the first draft. If the wiki is configured so that not all users can see drafts, the resources may need to be scripted for the first time.
-[[Manual:Extension/flaggedRevs/Server script|About automatic bulk release via server script.]]|bgcolor=}}
+#'''The embedded resource is in a namespace without approval mechanism:''' If the embedded resource is in a namespace without its own approval function, the approved version of the page shows the resource version that was embedded at the time of the page approval. An implicit draft version shows the most recent version of the embedded resource. <br />
+#'''The embedded resource is in a namespace with approval mechanism:''' The approval is done directly for the resource itself to avoid approval on all affected content pages.
+{{Messagebox|boxtype=important|icon=|Note text= If the approval mechanism is activated in a resource namespace (e.g. Template, File) in retrospect, all existing pages in the resource namespace are then in first draft. If the wiki is configured so that not all users can see drafts, the resources may need to be initially approved via server script if this cannot be accomplished manually.<br><br>[[Manual:Extension/FlaggedRevs/Server script|About approvals via server script.]]|bgcolor=}}
 {| class="contenttable" style="width: 100%;"
-!'''Attitude'''
-!Behaviour of shared content page -
-'''No resource sharing mechanism'''[[File:CS namespace without sharing.png|alternative text=screenshot of namespace setting without sharing mechanism|centered|mini|400x400px|resource without sharing mechanism]]
-! style="width:500px;" |Behaviour of shared content page -
-'''Release mechanism via resource'''[[File:CS namespace with release.png|alternative text=screenshot of the namespace setting without release mechanism|centered|mini|400x400px|resources with release mechanism]]
 |-
-!Released version
+!'''Setting'''
-(Default)
+!Behaviour of the approved content page -
-| style="background-color:#f2f3f9;" class="" |'''This setting has no effect if the resource itself has no sharing mechanism.'''
+'''No resource approval mechanism'''
+[[File:CS namespace resource no approval.png|alt=Namespace settings dialog|center|thumb|450x450px|Resource without approval feature]]
+! style="width:500px;" |Behaviour of  the approved content page -
+'''Approval mechanism via resource namespace'''
-Same behavior as "Time-bound version" (see below).
+[[File:CS namespace resource with approval.png|alt=Namespace manager settings|center|thumb|450x450px|Resource with approval feature]]
+|-
+!'''Versions that were current at the time of approval'''
+'''(Default)'''
+|  class="" |'''Resource display:'''
+*the '''embedded version at the time of approval''' is shown on the approved page:[[File:CS resource yes stable1.png|alt=screenshot of the approved page with the frozen resource|center|thumb|450x450px|Approved page version with the version of the resource that was embedded at the time of page approval]]
+*an implicit draft with the latest version of the resource exists:
+[[File:CS resource yes stable0.png|alt=Page draft with preview of changed resource and resource change banner|center|thumb|450x450px|Page draft due to change of embedded resource]]'''Resource approval:'''
+*the implicit draft '''must be approved on the content page'''. If the resource is embedded/linked on multiple pages in the wiki, all pages must be approved separately.
 | style="width:500px;" |'''Resource display:'''
-* the '''released version''' of the resource is displayed.[[File:CSresource yes stable standard.png|reference=https://en.wiki.bluespice.com/wiki/File:CSresource%20yes%20stable% 20standard.png|alternativetext=Screenshot of the released page with the currently released version of the resource.|centered|mini|400x400px|Released page with the currently released version of the resource.]]
+* the '''embedded version at the time of approval''' is shown:[[File:CS resource yes stable1.png|alt=screenshot of the approved page with the frozen resource|center|thumb|450x450px|Approved page version with the version of the resource that was valid at the time of page approval]]
-'''Release of resource:'''
+*an implicit draft with the latest version of the resource exists:[[File:CS resource yes stable0.png|alt=Page draft with preview of changed resource and resource change banner|center|thumb|450x450px|Page draft due to change of embedded resource]]
-* takes place exclusively via the resource itself. The page contains no indication whether a draft version of the resource exists.
+'''Resource approval:'''
+*The implicit draft '''can only be approved on the content page'''. If the resource is embedded on multiple pages in the wiki, all pages must be approved separately.
 |-
-!Time-bound version
+!Approved versions of included pages
-|'''Resource display:'''
+| style="background-color:#f2f3f9;"  class="" |'''This setting has no effect if the resource itself has no approval mechanism. The page shows the same behavior as for "Versions that were current at the time of approval" (see above).'''
-* the '''embedded version''' of the resource is shown:[[File:CSresource yes stable1.png|reference=https://en.wiki.bluespice.com/wiki/File:CSresource%20yes %20stable1.png|alternative text=CSresource yes stable1|centered|mini|400x400px|Released page with version of resource included at time of page release.]]
-* an implicit draft with the latest version of the resource is created:[[File:CSresource yes stable0.png|reference=https://en.wiki.bluespice.com/wiki/File:CSresource%20yes%20stable0.png|alternative text =CSresource yes stable1|centered|mini|400x400px|Released page with current released version of resource.]]
-'''Release of resource:'''
-* the implicit draft '''must be approved on the content page'''. If the resource is embedded on multiple pages in the wiki, all pages must be released separately.
 | style="width:500px;" |'''Resource display:'''
-* the '''embedded version''' of the resource is shown:[[File:CSresource yes stable1.png|reference=https://en.wiki.bluespice.com/wiki/File:CSresource%20yes %20stable1.png|alternative text=CSresource yes stable1|centered|mini|400x400px|Released page with version of resource included at time of page release.]]
+*the '''approved version of the resource''' is shown on  page.[[File:CS resource yes stable standard.png|alt=Approved page with currently approved version of the resource.|center|thumb|450x450px|The currently approved version of the resource is shown.]]
-* an implicit draft with the latest version of the resource is created:[[File:CSresource yes stable0.png|reference=https://en.wiki.bluespice.com/wiki/File:CSresource%20yes%20stable0.png|alternative text =CSresource yes stable1|centered|mini|400x400px|Released page with current released version of resource.]]
+'''Resource approval:'''
-'''Release of resource:'''
+*Takes place exclusively via the resource itself. The page contains no indication whether a draft version of the resource exists.
-*''Case A:'' the implicit draft '''can be shared on the content page'''. If the resource is embedded on multiple pages in the wiki, all pages must be released separately.
-*''<span class="col-turquoise">'''Case B (normal case):'''</span>'' is now '''the resource itself released''', '''the implicit Draft removed from all affected content pages. These no longer have to be released separately, since the resource itself has been released.'''
 |-
-!Current version
+!Current versions of included pages
 |'''Resource display:'''
-*'''the current version''' of the resource is displayed:
+*'''the current version''' of the resource is shown:
+[[File:CS resource yes current.png|alt=Approved page with approved status|center|thumb|450x450px|Approved page with the current version of the resource]]'''Resource approval:'''
-[[File:CSresource yes current.png|reference=https://de.wiki.bluespice.com/wiki/File:CSresource%20yes%20current.png|alternative text=Screenshot of the shared page with the current version of the included resource.| centered|mini|400x400px|Shared page with current version of included resource.]]
+*the resource itself cannot be approved
+| style="background-color:#f2f3f9;" class="" |'''Resource display:'''
+*'''the current version''' of the resource is shown:
-'''Release of resource:'''
+[[File:CS resource yes current.png|alt=Approved page with approved status|center|thumb|450x450px|Approved page with the current version of the resource]]'''Resource approval:'''
+*The approval status of the resource has no effect on the page and should therefore not be used in combination with an activated approval mechanism in the resource namespace.
-* No release of the resource possible
-| style="background-color:#f2f3f9;width:500px;" class="" |'''Resource display:'''
-*'''the current version''' of the resource is displayed:
-[[File:CSresource yes current.png|alternative text=Screenshot of shared page with current version of included resource.|centered|mini|400x400px|Shared page with current version of included resource.]]
-'''Release of resource:'''
-* The resource release status has no effect on the page and should therefore not be used in combination with release in the resource namespace.
 |}
 ===Reading permissions for drafts===
-By default, all users can see a page's drafts, including users with read rights.
+By default, all users can see a page's drafts, including users with only read permissions.
 To hide drafts from users, the ''user'' group must be removed from the configuration. This setting then applies to the entire wiki and cannot be further restricted to specific namespaces.
-An administrator changes the groups that can see drafts in the ''Show draft versions for the following groups'' box.''<br />{{Note box|boxtype=warning|icon=|Note text=If the group ''user'' is off is removed from the configuration, users in this group cannot see draft versions even if they are assigned a workflow task.|bgcolor=}}After removing the group ''user'', the desired group(s ), e.g. B. the group ''editor'', can be added to the configuration and saved.
+An administrator changes the groups that can see drafts in the ''Show draft versions for the following groups'' box.''<br />{{Messagebox|boxtype=warning|icon=|Note text=If the group ''user'' is off is removed from the configuration, users in this group cannot see draft versions even if they are assigned a workflow task.|bgcolor=}}After removing the group ''user'', the desired group(s ), e.g. B. the group ''editor'', can be added to the configuration and saved.
-{{Note box|boxtype=note|icon=|Note text=If no user groups are specified in the configuration field, even users with share rights and sysop users will not see a visual status indicator of the page. Instead, you have access to drafts through the page's history.
+{{Messagebox|boxtype=note|icon=|Note text=If no user groups are specified in the configuration field, even users with share rights and sysop users will not see a visual status indicator of the page. Instead, you have access to drafts through the page's history.
 In order for administrators to see the status directly on the page, they must be added to a group listed here in the configuration.|bgcolor=}}
-=== Read permissions for first drafts ===
+=== Read permissions for first drafts===
-By default, first drafts are visible to all users who have read permissions in a namespace. However, if first drafts are only visible to those users who can generally view page drafts, this can be done in the configuration management by selecting ''<span class="col-red ve-pasteProtect">Allow viewing of first draft version</span> '' to be disabled.
+By default, first drafts are visible to all users who have read permissions in a namespace. However, if first drafts are only visible to those users who can generally view page drafts, this can be done in the configuration management by selecting ''Allow viewing of first draft version for users who can normally not see drafts''  to be disabled.
 ===Summary: Read Permissions for Draft Pages===
 '''Define groups:'''
@@ Line 109: / Line 110: @@
 '''Export draft pages:'''
 *'''Single page export:''' Users with reading rights on a draft page can print it directly as a PDF.
-*'''Book export:''' Only approved pages are exported. If there is only a first draft of a page, it will be exported. '''Exception:''' If the book is printed by a user who does not have access to the first draft, the first draft will not be printed out in the book. Instead, the PDF shows the following message:[[File:Book-First Draft.png|alternative text=Permission Error PDF Export|centered|mini|550x550px|Permission Error PDF Export|reference=https://de.wiki.bluespice.com/wiki/ File:Book-First Draft.png]]
+*'''Book export:''' Only approved pages are exported. If there is only a first draft of a page, it will be exported. '''Exception:''' If the book is printed by a user who does not have access to the first draft, the first draft will not be printed out in the book. Instead, the PDF shows the following message:[[File:CS first draft export.png|alt=Error message in the PDF|center|thumb|550x550px|Permissions error PDF export]]
+Effects on Semantic MediaWiki properties
-== Effects on semantic attributes ==
+If a namespace has SemanticMediaWiki [[Manual:Semantic_MediaWiki|Semantic MediaWiki]] activated, the following SMW queries are available depending on the approval status of the page:
-If [[Manual:Semantic MediaWiki|Semantic MediaWiki]] is activated in a namespace at the same time as page release, the following attributes are available for SMW queries depending on the release status of the page:
+{| class="wikitable" style="width:950px;"
-{| class="wikitable" style="width:100%;"
+! style="background-color:rgb(234, 236, 240);text-align:center;box-sizing:inherit;padding:0.2em 0.4em;border:1px solid rgb(162, 169, 177);" class="" |Document state
-!page status
+! style="background-color:rgb(234, 236, 240);text-align:center;box-sizing:inherit;padding:0.2em 0.4em;border:1px solid rgb(162, 169, 177);" class="" |Available properties
-!Available attributes
+|- style="box-sizing: inherit;"
-|-
+| style="box-sizing:inherit;padding:0.2em 0.4em;border:1px solid rgb(162, 169, 177);" |First draft
-|First draft
+| style="box-sizing:inherit;padding:0.2em 0.4em;border:1px solid rgb(162, 169, 177);" |Current values
-|Current values
+|- style="box-sizing: inherit;"
-|-
+| style="box-sizing:inherit;padding:0.2em 0.4em;border:1px solid rgb(162, 169, 177);" |Approved
-| Approved
+| style="box-sizing:inherit;padding:0.2em 0.4em;border:1px solid rgb(162, 169, 177);" |Values of the approved (stable) version
-|Current values
+|- style="box-sizing: inherit;"
-|-
+| style="box-sizing:inherit;padding:0.2em 0.4em;border:1px solid rgb(162, 169, 177);" |Draft
-|Draft
+| style="box-sizing:inherit;padding:0.2em 0.4em;border:1px solid rgb(162, 169, 177);" |Values of the approved (stable) version (default setting)
-|Released version values (default). This can be changed via the [[Page Design:Extension/ContentStabilization#Settings in Configuration Management|Configuration Management]] so that the values of the draft version apply.
+|- style="box-sizing: inherit;"
-|-
+| style="box-sizing:inherit;padding:0.2em 0.4em;border:1px solid rgb(162, 169, 177);" |Implicit draft<ref>An approved page has an implicit draft, if there have been changes to embedded resources (e.g., a template or an image) since the last page approval.</ref>
-|Implicit draft
+| style="box-sizing:inherit;padding:0.2em 0.4em;border:1px solid rgb(162, 169, 177);" |Values of the approved (stable) version
-(changes to included resources)
-|Released version values
 |}
-==Quality management overview ==
+The availability of the semantic properties is determined by the following configuration setting:
-The special page ''Special:Quality Management_Overview'' allows all users to see the release status of all wiki pages and to filter accordingly. Only pages that users have read access to are displayed.
+ $bsgFlaggedRevsConnectorStabilizeSMWPropertyValues = true;
-<br />[[File:Manual:qm-overview-DE.png|centered|mini|650x650px|special page quality management overview]]
+The value for this setting can be set to ''false'' in the ''LocalSettings.php'' <span>of the server file system</span>. If set to ''false,'' the property values of the draft version are used for semantic queries instead of the values for the stable version.
+==Quality management overview==
+The Special page ''Special:Quality_management_overview'' allows all users  with ''reviewer'' permissions to view and filter a list of wiki pages and their review status. Pages for which a user does not have read permissions are not shown.
+[[File:QM overview page.png|center|thumb|650x650px|Special page "Quality management overview"]]
+== Approving a page when the title area is hidden ==
+When the title area is hidden, you can approve the page from the .<code>..all actions</code> menu:
+# '''Switch''' to the draft version of the page (this not necessary when  the page is in ''First draft'' status).{{Bsvs|bsvFrom=4.3.2}}[[File:ContentStabilization hidetitle-firstdraft.png|thumb|550x550px|alt=all actions dialog|center|Switching to first draft url]]<br/>Before v.4.3.2, this switch-link is not available. In that case, go to the page history and click on the latest time stamp to switch to the draft version of the page.[[File:ContentStabilization pagehistory.png|alt=page history screenshot|center|thumb|550x550px|The latest time stamp in the page history links to the draft page.]]
+#Approve the page via <code>...all actions -> Approve page</code> .
+[[File:BlueSpiceHideTitle-pageapproval.png|thumb|center|550x550px|All actions menu with approval link highlighted]]
 {{Box Links-en
 |Topic1=[[Manual:Quality_management|Quality management tools]]
@@ Line 140: / Line 153: @@
 |Topic3=[[Reference:BlueSpiceFlaggedRevsConnector]]|Topic4=[[Manual:Semantic MediaWiki]]}}
 {{translation}}
-[[Category:Qualität]]
 <references />
+[[Category:Quality]]