BlueSpice - User contributions [en]

Form:Portal flex

2025-10-09T06:10:56Z

Lhuyghe:

<noinclude>This is the form "Portal flexbox". 

{{#forminput:form=Portal flex}}
</noinclude><includeonly><div id="wikiPreview" style="display: none; padding-bottom: 25px; margin-bottom: 25px; border-bottom: 1px solid #AAAAAA;"></div><templatestyles src="Template:Portal flex/styles.css" />
{{{standard input|save}}} {{{standard input|preview}}} {{{standard input|cancel}}}
{{{standard input|free text|class=bs-mwvisualeditor}}}
{{{for template|Portal flex/Start}}}
{| class="formtable" style="width:100%;"
! style="width:200px;" |Number of columns:
| style="width:150px;" |{{{field|colnum|input type=radiobutton|mandatory|default=2|values=2,3}}}
! style="width:200px;" |Colour scheme:
| style="width:350px;" |{{{field|color|input type=dropdown||mandatory|default=grau|values=blau,gelb,grau,grün,lila,orange,rot, weiß}}}
|-
!First box full page width:
|{{{field|fullfirst|input type=radiobutton|mandatory|default=nein|values=ja,nein}}}
!Stil der Box:
|{{{field|boxstyle|input type=radiobutton|mandatory|default=Rahmen|values=Rahmen,Hintergrund,ohne}}}
|-
!Last box full page width:
|{{{field|fulllast|input type=radiobutton|mandatory|default=nein|values=ja,nein}}}
!Box headings (h2):
|{{{field|showhd|input type=radiobutton||mandatory|default=unterstrichen |values=unterstrichen,Hintergrund,verstecken}}}
|-
!Show table of contents:
|{{{field|showtoc|input type=radiobutton|mandatory|default=ja|values=ja,nein}}}
!
|
|}
{{{end template}}}
{{{for template|Portal_flex/Box|multiple|add button text=Neue Box}}}
{| class="formtable"
!Heading:
|{{{field|heading|size=50}}}
|-
!Content:
|{{{field|content|input type=bs-mwvisualeditor}}}
|-
!Background colour (optional):
|{{{field|boxcolor|input type=dropdown|values=blau,gelb,grau,grün,lila,orange,rot, weiß}}}
|-
!Heading:
|{{{field|hdstatus|input type=checkbox|label=Überschrift nicht anzeigen}}}

|}
{{{end template}}}
{{{for template|Portal_flex/End}}}
{| class="formtable" style="width:100%;"
|-
! style="width:250px;" ||Add empty boxes at the end:
|{{{field|emptybox|input type=radiobutton|mandatory|default=nein|values=nein,1,2}}}
|}
{{{end template}}}
{{{standard input|save}}} {{{standard input|preview}}} {{{standard input|cancel}}}</includeonly>

Manual:Extension/BlueSpiceTranslationTransfer

2025-08-28T07:00:03Z

Lhuyghe:

{{DISPLAYTITLE:Translations in a Wiki farm (TranslationTransfer)}}

{{Textbox|boxtype=important|header=DeepL API key required:|text=This feature requires a valid DeepL API key, which is not provided by BlueSpice. The key is entered in the [[Manual:Extension/BlueSpiceConfigManager#BlueSpiceTranslationTransfer_(farm)|Config manager of the translation source wiki]].|icon=yes}}

== Determining the source wiki and the target wikis ==
The translation mechanism requires one source and one or multiple target wiki. The content language of the source wiki determines what wiki instance is the source wiki in the farm. For example, if the root wiki is installed as a German wiki (DE as content language), then there '''must be an instance in the wiki named DE.''' This is the source wiki from which translations can be pushed to other language wikis.

The translation mechanism requires a source wiki and one or more target wikis.

The content language of the root wiki determines which wiki instance in the farm serves as the source wiki for translations. The root wiki is the wiki from which the other instances are generated from the page ''Special:FarmManager''.

For example, if the root wiki is installed as a German wiki (with the content language DE), '''an additional instance named DE must exist in the wiki'''. This DE instance now functions as the source wiki for translations. From there, translations of wiki pages into other language wikis can be generated.

The page tools of the wiki pages therefore automatically displays a translation link, even if no DeepL API key has been entered.

==== Creating the target wikis ====
Language wikis are always created with their [[wikipedia:ISO_639-1|two-letter ISO 639-1 language code]] (e.g., DE for the German language instance, FR for the French one). During translation, any translation instance supported by the DeepL translation service can be created.

This also means that a wiki instance named IT is automatically recognized as a language wiki. An instance must then be created for the IT department that does not correspond to the language code for Italian (e.g., IT-Wiki).

If a wiki farm requires a different setup, the server configuration must be adjusted accordingly by a server administrator (only possible for on-premises installations).

<drawio filename="translation_wikis" alt="Diagram showing a root wiki and four other wikis in the same farm">

</drawio>

== Translation of a page ==
Pages can be translated from the source wiki and automatically created in another language wiki instance.

To translate a page:
# '''Click''' on the ''Translate'' link in the page tools. A dialog opens.
# '''Select''' a target language.
# '''Click''' ''Translate'' to start the translation.
# '''Check''' the suggested page name in the target wiki and change it if necessary. This dialog box only appears for the first translation of the page.
# '''Click''' ''Translate'' again to save the page name. The translation is displayed.
# '''Click''' ''Save'' to save the translated page in the target wiki. You can now go directly to the page in the target wiki, translate it into another language (if configured) or close the dialog box without taking any further action.
<gallery widths="220" heights="200">
File:Manual:Extension BlueSpiceTranslationTransfer 1743770053694.png|Translation button
File:Manual:Extension BlueSpiceTranslationTransfer 1743770108045.png|Language selection dialogue
File:Manual:Extension BlueSpiceTranslationTransfer 1743770150061.png|Customise page title
File:Manual:Extension BlueSpiceTranslationTransfer 1743770194009.png|Page translation display and confirmation
File:Manual:Extension BlueSpiceTranslationTransfer 1743769862375.png|Link between the language versions
</gallery>

== Merge page content ==
If a page has already been translated, subsequent translations overwrite the previous page.

However, it is possible to configure in the server to first store subsequent translations in a draft namespace. Users than have to merge any changes between the translation revisions manually. In this case, see the [[Manual:Extension/MergeArticles|documentation of the MergeArticles extension]].

== Translated elements ==
The translated content during the translation process includes:

* Page text
* Page title (the title can be adjusted during the initial translation)
* Display title
* Categories
** The categories specified on a page are translated during the initial translation of the page, unless the categories have already been translated via another wiki page.
** If a category from the source wiki already exists in the target wiki due to a previous translation of the page or due to a translation via another page, it is excluded from further translation. This prevents the category from being replaced by the translation service with a new, different translation.
* Internal links
** A link to a wiki page links to the original page in the source wiki if it does not exist in the target wiki.
** Example: If the English page A links to the English page B, the German translation page A will link to the German translation page B.
* Embedded files are transferred to the target wiki:
** The file name is retained
** The description and alternative text of embedded files are translated
* Magic words are translated into their canonical name (EN)
* Transcluded pages are transferred even without translation
* Code blocks themselves are not translated; comments within code blocks are translated.
* Limitation: If a page is too large, the DeepL API cannot translate it. The best option is to split the page into smaller subpages.

== Non-translated or transferred elements ==
The following elements are not considered for translation:

* '''Template contents:''' Templates are transferred to the target wiki during translation, but the content is not translated.

* '''Forms for templates ([[Reference:Page Forms|Page Forms]]):''' Forms must be manually transferred to the target wikis (see [[Manual:Extension/ContentTransfer|ContentTransfer]]) and manually translated.

* '''File attachments:''' Files are not transferred to the target wiki if they are only displayed as attachments on a page using the <code><nowiki><attachments></nowiki></code> tag.

== Excluding files from translation ==
A tag can be inserted on the source page to exclude all included files for a specific page from the translation process.

This way, changes made to files in the target system will not be overwritten during the next translation.

Steps to exclude files from translation:

# '''Insert''' the tag <code><nowiki>___BS_NO_AUTOMATIC_DOCUMENT_TRANSLATION___</nowiki></code> in the source code of the page to be translated.
# '''Translate''' the page into the target language. The source wiki files are still displayed in the preview, but they will not be transferred.
# '''Check''' the target page. The file link has been retained with the original name in the source code. The file itself has not been transferred. The file is displayed on the page as a "required file" (redlink). This makes it clear that files are missing and may need to be replaced.

Note: If the file already exists on the target wiki, it will still be displayed as correct.

== Translation overview ==
An overview of all translations is available under <code>Special:TranslationsOverview</code>.
[[File:Manual:Extension BlueSpiceTranslationTransfer 1743771014879.png|center|thumb|700x700px|Translation overview]]

== Translation dictionary ==
The dictionary with all page titles and links can be viewed under <code>Special:TranslationDictionary</code>.

If the title of a target page needs to be adapted after the first translation, this can be done on this special page.
[[File:Manual:Extension BlueSpiceTranslationTransfer 1743771305481.png|center|thumb|600x600px|Translation Dictionary ]]
If a source page is renamed, the titles are automatically retranslated and the title translations are updated in the database and in the wiki.

The different translation versions are still linked correctly. The redirect selected on the source page is also set up on the corresponding target pages.

== Translation glossary ==
Glossary entries for the translation can be maintained on the <code>Special:TranslationsGlossary</code> page. This ensures that certain terms from the source language are always translated with a specific term from the target language. This applies to both the page title and the normal page content.

The maintained wiki glossary is transferred to the DeepL glossary and used in the translation.

([https://developers.deepl.com/docs/api-reference/glossaries#list-supported-glossary-language-pairs See the list of supported glossary languages in the DeepL documentation])
[[File:Manual:Extension BlueSpiceTranslationTransfer 1743771485615.png|center|thumb|600x600px|Translation glossary]]

Please follow these recommendations for defining glossary terms (provided by the DeepL service):

* In general, we recommend to use use idiomatic capitalization when adding an entry in the glossary. Please capitalize/lowercase when it is appropriate in the respective language.
* Since in English, nouns are generally with a lowercase, we highly recommend to use the glossary pair "cat - Katze". Otherwise, the AI will recognise "Cat" (with a capital letter) as a name.

Best practises for glossaries:

* no plural
* no past tense
* use idiomatic capitalization (capitalize/lowercase when it’s appropriate in the respective language)
* use of prefixed articles for nouns is irrelevant and can be ignored
* use infinitive markers with verbs, such as “to” in English to avoid “misunderstandings” ( ''Example: to rain → regnen; rain → Regen)''

== Additional information ==
==== Configuration of wiki structure and namespaces ====

*The translation processes (i.e. which wiki/language can be translated into which wiki/language) must be configured.
*The farm may contain some wiki instances that do not use translation workflows.
*Caution: DeepL translation is not available in all existing languages.

The links between the source and target namespaces must be maintained under <code>Special:BlueSpiceConfigManager</code> and <code>BlueSpiceTranslationTransfer</code> extension.

For example, the pages from the DE source namespace ‘Finanzen’ must be translated into the EN target namespace ‘Finance’.
[[File:Manual:Extension BlueSpiceTranslationTransfer 1743771917649.png|center|thumb|600x600px|Namespace configuration]]
If the pages must first be created in the draft namespace after translation, this must also be [[Reference:MergeArticles|configured in the backend]].

==== Configuration DeepL API ====
The configuration is required in the source wiki.

{{#dpl:title=Manual:Extension/BlueSpiceConfigManager|include=#DeepL API}}

== Error messages ==
There can be some translation conflicts between source and target wikis when pages are deleted or renamed without a redirect. For example:

# '''Source page has been moved:''' A page was moved in an English source wiki from <code>A new page</code> to <code>A new page 1</code> without a redirect. The page was originally translated to the German wiki from page <code>Eine neue Seite</code>. When the user wants to translate <code>A new page 1</code> to <code>Eine neue Seite</code>, the wiki shows an error message that the suggested targt page already exists:[[File:translationtransfer error1.png|alt=page cannot be translated to selected page title because target page already exists|center|thumb|450x450px|Translation transfer error message]]'''Solution:''' It is necessary to delete the original mapping between the two pages <code>A new page</code> and <code>Eine neue Seite</code> from the [[Manual:Extension/BlueSpiceTranslationTransfer#Translation dictionary|Translation dictionary]]. After that, it is possible to set the translation target for <code>A new page 1</code> without problems to <code>Eine neue Seite</code> without getting an error message. The target page <code>Eine neue Seite</code> will keep its version history.

== Ad-hoc Translation ==
In a wiki instance with a configured DeepL API key, ad-hoc translations are possible. This meaans that users whose language settings differ from the wiki's content language are shown a link to translate the page in their language . This translation is only valid until the page is reloaded. See the documentation for [[Manual:Extension/AdhocTranslation|ad-hoc translations]].

{{Box Links-en|Topic1=[[Manual:Extension/ContentTransfer]]|Topic2=[[Manual:Extension/MergeArticles]]|Topic3=[[Manual:Extension/AdhocTranslation]]}}

{{translation}}

Manual:Extension/BlueSpiceTranslationTransfer

2025-08-28T06:59:15Z

Lhuyghe:

{{DISPLAYTITLE:Translations in a Wiki farm (TranslationTransfer)}}

{{Textbox|boxtype=important|header=DeepL API key required:|text=This feature requires a valid DeepL API key, which is not provided by BlueSpice. The key is entered in the [[Manual:Extension/BlueSpiceConfigManager#BlueSpiceTranslationTransfer_(farm)|Config manager of the translation source wiki]].|icon=yes}}

== Determining the source wiki and the target wikis ==
The translation mechanism requires one source and one or multiple target wiki. The content language of the source wiki determines what wiki instance is the source wiki in the farm. For example, if the root wiki is installed as a German wiki (DE as content language), then there '''must be an instance in the wiki named DE.''' This is the source wiki from which translations can be pushed to other language wikis.

The translation mechanism requires a source wiki and one or more target wikis.

The content language of the root wiki determines which wiki instance in the farm serves as the source wiki for translations. The root wiki is the wiki from which the other instances are generated from the page ''Special:FarmManager''.

For example, if the root wiki is installed as a German wiki (with the content language DE), '''an additional instance named DE must exist in the wiki'''. This DE instance now functions as the source wiki for translations. From there, translations of wiki pages into other language wikis can be generated.

The page tools of the wiki pages therefore automatically displays a translation link, even if no DeepL API key has been entered.

==== Creating the target wikis ====
Language wikis are always created with their [[wikipedia:ISO_639-1|two-letter ISO 639-1 language code]] (e.g., DE for the German language instance, FR for the French one). During translation, any translation instance supported by the DeepL translation service can be created.

This also means that a wiki instance named IT is automatically recognized as a language wiki. An instance must then be created for the IT department that does not correspond to the language code for Italian (e.g., IT-Wiki).

If a wiki farm requires a different setup, the server configuration must be adjusted accordingly by a server administrator (only possible for on-premises installations).

<drawio filename="translation_wikis" alt="Diagram showing a root wiki and four other wikis in the same farm">

</drawio>

== Translation of a page ==
Pages can be translated from the source wiki and automatically created in another language wiki instance.

To translate a page:
# '''Click''' on the ''Translate'' link in the page tools. A dialog opens.
# '''Select''' a target language.
# '''Click''' ''Translate'' to start the translation.
# '''Check''' the suggested page name in the target wiki and change it if necessary. This dialog box only appears for the first translation of the page.
# '''Click''' ''Translate'' again to save the page name. The translation is displayed.
# '''Click''' ''Save'' to save the translated page in the target wiki. You can now go directly to the page in the target wiki, translate it into another language (if configured) or close the dialog box without taking any further action.
<gallery widths="220" heights="200">
File:Manual:Extension BlueSpiceTranslationTransfer 1743770053694.png|Translation button
File:Manual:Extension BlueSpiceTranslationTransfer 1743770108045.png|Language selection dialogue
File:Manual:Extension BlueSpiceTranslationTransfer 1743770150061.png|Customise page title
File:Manual:Extension BlueSpiceTranslationTransfer 1743770194009.png|Page translation display and confirmation
File:Manual:Extension BlueSpiceTranslationTransfer 1743769862375.png|Link between the language versions
</gallery>

== Merge page content ==
If a page has already been translated, subsequent translations overwrite the previous page.

However, it is possible to configure in the server to first store subsequent translations in a draft namespace. Users than have to merge any changes between the translation revisions manually. In this case, see the [[Manual:Extension/MergeArticles|documentation of the MergeArticles extension]].

== Translated elements ==
The translated content during the translation process includes:

* Page text
* Page title (the title can be adjusted during the initial translation)
* Display title
* Categories
** The categories specified on a page are translated during the initial translation of the page, unless the categories have already been translated via another wiki page.
** If a category from the source wiki already exists in the target wiki due to a previous translation of the page or due to a translation via another page, it is excluded from further translation. This prevents the category from being replaced by the translation service with a new, different translation.
* Internal links
** A link to a wiki page links to the original page in the source wiki if it does not exist in the target wiki.
** Example: If the English page A links to the English page B, the German translation page A will link to the German translation page B.
* Embedded files are transferred to the target wiki:
** The file name is retained
** The description and alternative text of embedded files are translated
* Magic words are translated into their canonical name (EN)
* Transcluded pages are transferred even without translation
* Code blocks themselves are not translated; comments within code blocks are translated.
* Limitation: If a page is too large, the DeepL API cannot translate it. The best option is to split the page into smaller subpages.

== Non-translated or transferred elements ==
The following elements are not considered for translation:

* '''Template contents:''' Templates are transferred to the target wiki during translation, but the content is not translated.

* '''Forms for templates ([[Reference:Page Forms|Page Forms]]):''' Forms must be manually transferred to the target wikis (see [[Manual:Extension/ContentTransfer|ContentTransfer]]) and manually translated.

* '''File attachments:''' Files are not transferred to the target wiki if they are only displayed as attachments on a page using the <code><nowiki><attachments></nowiki></code> tag.

== Excluding files from translation ==
A tag can be inserted on the source page to exclude all included files for a specific page from the translation process.

This way, changes made to files in the target system will not be overwritten during the next translation.

Steps to exclude files from translation:

# '''Insert''' the tag <code><nowiki>___BS_NO_AUTOMATIC_DOCUMENT_TRANSLATION___</nowiki></code> in the source code of the page to be translated.
# '''Translate''' the page into the target language. The source wiki files are still displayed in the preview, but they will not be transferred.
# '''Check''' the target page. The file link has been retained with the original name in the source code. The file itself has not been transferred. The file is displayed on the page as a "required file" (redlink). This makes it clear that files are missing and may need to be replaced.

Note: If the file already exists on the target wiki, it will still be displayed as correct.

== Excluding files from translation ==
A tag can be inserted on the source page to exclude all embedded files for a specific page from the translation process.

This way, changes made to files in the target system will not be overwritten during the next translation.

Steps to exclude files from translation:

# '''Insert''' the tag <code><nowiki>__BS_NO_AUTOMATIC_DOCUMENT_TRANSLATION__</nowiki></code> in the source code of the page to be translated.
# '''Translate''' the page into the target language. The source wiki files will still be displayed in the preview, but they will not be transferred.
# '''Check''' the target page. The file link has been retained with the original name in the source code. The file itself has not been transferred. The file is displayed on the page as a "required file" (redlink). This makes it clear that files are missing and may need to be replaced.

Note: If the file already exists on the target wiki, it will be displayed.

== Translation overview ==
An overview of all translations is available under <code>Special:TranslationsOverview</code>.
[[File:Manual:Extension BlueSpiceTranslationTransfer 1743771014879.png|center|thumb|700x700px|Translation overview]]

== Translation dictionary ==
The dictionary with all page titles and links can be viewed under <code>Special:TranslationDictionary</code>.

If the title of a target page needs to be adapted after the first translation, this can be done on this special page.
[[File:Manual:Extension BlueSpiceTranslationTransfer 1743771305481.png|center|thumb|600x600px|Translation Dictionary ]]
If a source page is renamed, the titles are automatically retranslated and the title translations are updated in the database and in the wiki.

The different translation versions are still linked correctly. The redirect selected on the source page is also set up on the corresponding target pages.

== Translation glossary ==
Glossary entries for the translation can be maintained on the <code>Special:TranslationsGlossary</code> page. This ensures that certain terms from the source language are always translated with a specific term from the target language. This applies to both the page title and the normal page content.

The maintained wiki glossary is transferred to the DeepL glossary and used in the translation.

([https://developers.deepl.com/docs/api-reference/glossaries#list-supported-glossary-language-pairs See the list of supported glossary languages in the DeepL documentation])
[[File:Manual:Extension BlueSpiceTranslationTransfer 1743771485615.png|center|thumb|600x600px|Translation glossary]]

Please follow these recommendations for defining glossary terms (provided by the DeepL service):

* In general, we recommend to use use idiomatic capitalization when adding an entry in the glossary. Please capitalize/lowercase when it is appropriate in the respective language.
* Since in English, nouns are generally with a lowercase, we highly recommend to use the glossary pair "cat - Katze". Otherwise, the AI will recognise "Cat" (with a capital letter) as a name.

Best practises for glossaries:

* no plural
* no past tense
* use idiomatic capitalization (capitalize/lowercase when it’s appropriate in the respective language)
* use of prefixed articles for nouns is irrelevant and can be ignored
* use infinitive markers with verbs, such as “to” in English to avoid “misunderstandings” ( ''Example: to rain → regnen; rain → Regen)''

== Additional information ==
==== Configuration of wiki structure and namespaces ====

*The translation processes (i.e. which wiki/language can be translated into which wiki/language) must be configured.
*The farm may contain some wiki instances that do not use translation workflows.
*Caution: DeepL translation is not available in all existing languages.

The links between the source and target namespaces must be maintained under <code>Special:BlueSpiceConfigManager</code> and <code>BlueSpiceTranslationTransfer</code> extension.

For example, the pages from the DE source namespace ‘Finanzen’ must be translated into the EN target namespace ‘Finance’.
[[File:Manual:Extension BlueSpiceTranslationTransfer 1743771917649.png|center|thumb|600x600px|Namespace configuration]]
If the pages must first be created in the draft namespace after translation, this must also be [[Reference:MergeArticles|configured in the backend]].

==== Configuration DeepL API ====
The configuration is required in the source wiki.

{{#dpl:title=Manual:Extension/BlueSpiceConfigManager|include=#DeepL API}}

== Error messages ==
There can be some translation conflicts between source and target wikis when pages are deleted or renamed without a redirect. For example:

# '''Source page has been moved:''' A page was moved in an English source wiki from <code>A new page</code> to <code>A new page 1</code> without a redirect. The page was originally translated to the German wiki from page <code>Eine neue Seite</code>. When the user wants to translate <code>A new page 1</code> to <code>Eine neue Seite</code>, the wiki shows an error message that the suggested targt page already exists:[[File:translationtransfer error1.png|alt=page cannot be translated to selected page title because target page already exists|center|thumb|450x450px|Translation transfer error message]]'''Solution:''' It is necessary to delete the original mapping between the two pages <code>A new page</code> and <code>Eine neue Seite</code> from the [[Manual:Extension/BlueSpiceTranslationTransfer#Translation dictionary|Translation dictionary]]. After that, it is possible to set the translation target for <code>A new page 1</code> without problems to <code>Eine neue Seite</code> without getting an error message. The target page <code>Eine neue Seite</code> will keep its version history.

== Ad-hoc Translation ==
In a wiki instance with a configured DeepL API key, ad-hoc translations are possible. This meaans that users whose language settings differ from the wiki's content language are shown a link to translate the page in their language . This translation is only valid until the page is reloaded. See the documentation for [[Manual:Extension/AdhocTranslation|ad-hoc translations]].

{{Box Links-en|Topic1=[[Manual:Extension/ContentTransfer]]|Topic2=[[Manual:Extension/MergeArticles]]|Topic3=[[Manual:Extension/AdhocTranslation]]}}

{{translation}}

Archive:Manual:Extension/BlueSpiceGroupManager

2025-06-30T07:25:00Z

Lhuyghe:

<bookshelf src="Book:Admin manual" />
{{DISPLAYTITLE:Group manager}}
The interface for the Group manager is provided by the extension '''GroupManager'''. It allows adding, renaming and deleting groups.

== When are groups created? ==
Groups can be created in the wiki for the following purposes:

* '''Special authorisation of a namespace:''' The pages in a namespace can be allocated by assigning different roles to this namespace via individual groups.
* '''Special authorisation of a page:''' The [[Reference:BlueSpicePageAccess|PageAcess]] extension can be used to restrict reading rights on an individual page to certain groups.
* '''[[Manual:Extension/Workflows|Workflows]]:''' Workflow tasks can be assigned to user groups.

==Functionality==
Users with the right ''groupmanager-viewspecialpage'' (in roles: ''admin, maintenanceadmin, accountmanager'') can access the page ''Special:GroupManager'' in the menu ''Global actions > Administration> Groups''.

An administrator can go to ''Global actions > Management > Group manager''. This opens the page ''Special:GroupManager''.
[[File:Manual:groupmanager.png|alt=Group manager|center|thumb|750x750px|Group manager]]
 

The group manager has the following features:
*'''Viewing groups:''' All existing groups in the wiki are listed.
*'''Creating new groups:''' Clicking on the "plus" button opens a dialog for adding a new group.
*'''Renaming groups:''' A group can be renamed by selecting it and then clicking the wrench icon. System groups and groups declared by other extensions cannot be renamed.
*'''Deleting a group:''' A group can be deleted by selecting it and then clicking the "x" button. System groups cannot be deleted.

== Assigning roles and users to groups ==
* To assign users to groups, use the [[Manual:Extension/BlueSpiceUserManager|User manager]].
* To assign roles (permissions) to groups, use the [[Manual:Extension/BlueSpicePermissionManager|Permission manager]].

{{Box Links-en
|Topic1=[[Reference:BlueSpiceGroupManager]]
|Topic2=[[Manual:Extension/BlueSpicePermissionManager|Managing permissions]]}}
 
{{translation}}

__FORCETOC__
[[Category:Permissions]]

Manual:Error messages

2025-06-30T07:16:29Z

Lhuyghe:

<bookshelf src="Book:Admin manual" />
The wiki contains a number of system error messages. These messages can be customized to your needs.

For example, if a wiki has a lot of visitors with anonymous read-access only, these visitors get a permissions error when they try to access a page that does not exist:
[[File:permissionerror-default.png|alt=Default permission error message|center|thumb|650x650px|Default permission error message]]

This creates the impression that a page with that name exists, but the visitor does not have sufficient rights to view the page. In reality, the page simply does not exist and a user with write-permissions could now log in and create the page.

Therefore, we want to distinguish between anonymous visitors and users with write-access and show a tailored error message.

==Creating a custom 404 error page==
If a page does not exist yet, you can display a custom message.

'''To create the message:'''

#Create the page ''MediaWiki:Noarticletext-nopermission''
#Add your custom message in edit mode.
#Save the page.
#To test the message, try to access a page that does not exist.Make sure you are not logged in, because this message is displayed to anonymous users only.

==How to update an error message==
The text for the error pages on the wiki is stored in the form of system notifications. You can access these error messages from the page <code>Special:AllMessages</code>.

To find the message or the messages that are being used on a particular error page, add <code>?uselang=qqx</code> or, if the url already contains a question mark, <code>&uselang=qqx</code> to the page url. This will expose the actual sources for the error messages on the page:
[[File:permissionerror-sourceinfo.png|alt=Show system messages|center|thumb|650x650px|Show system messages]]

In the above example, there are two error messages on the page:

*''permissionserrortext-withaction:'' displays the text "You do not have permission to edit this page, for the following reason"
*''badaccess-groups:'' displays the text "The action you have requested is limited to users in one of the groups: Administrators, Editors, Reviewers.

These pages do not actually exist, and therefore the standard text message from the database is displayed. If you want to change a message, you must first create the page.

'''To update a system message:'''

#Go to the special page "System messages" (<code>Special:AllMessages</code> )[[File:permissionerror-find.png|alt=Customize the message text.|center|thumb|650x650px|Customize the message text.]]
Enter the full name of the system message in the "Prefix" field of the filter: The link to the system message apears in red.
#Click on the name to create a page for this system message
#Enter your custom error message and save the page. The system message has now been customized.
#Continue to update any other system messages on the page.
{{Messagebox|boxtype=note|Note text=Many of these messages use parameters (e.g., "$1"), which should be considered when you change the default text. If something went wrong, you can also delete the custom error pages you created - then the default text from the database will be used again.}}
{{Box Links-en|Topic1=https://www.mediawiki.org/wiki/Manual:Interface/Noarticletext |mediawiki.org/wiki/Manual:Interface/Noarticletext}}
[[en:{{FULLPAGENAME}}]]
[[De:Fehlermeldungen]]
[[Category:Customization]]

Manual:Error messages

2025-06-30T07:16:00Z

Lhuyghe:

<bookshelf src="Book:Admin manual" />
The wiki contains a number of system error messages. These messages can be customized to your needs.

For example, if a wiki has a lot of visitors with anonymous read-access only, these visitors get a permissions error when they try to access a page that does not exist:
[[File:permissionerror-default.png|alt=Default permission error message|center|thumb|650x650px|Default permission error message]]

This creates the impression that a page with that name exists, but the visitor does not have sufficient rights to view the page. In reality, the page simply does not exist and a user with write-permissions could now log in and create the page.

Therefore, we want to distinguish between anonymous visitors and users with write-access and show a tailored error message.

==Creating a custom 404 error page==
If a page does not exist yet, you can display a custom message.

'''To create the message:'''

#Create the page ''MediaWiki:Noarticletext-nopermission''
#Add your custom message in edit mode.
#Save the page.
#To test the message, try to access a page that does not exist.Make sure you are not logged in, because this message is displayed to anonymous users only.

==How to update an error message==
The text for the error pages on the wiki is stored in the form of system notifications. You can access these error messages from the page <code>Special:AllMessages</code>.

To find the message or the messages that are being used on a particular error page, add <code>?uselang=qqx</code> or, if the url already contains a question mark, <code>&uselang=qqx</code> to the page url. This will expose the actual sources for the error messages on the page:
[[File:permissionerror-sourceinfo.png|alt=Show system messages|center|thumb|650x650px|Show system messages]]

In the above example, there are two error messages on the page:

*''permissionserrortext-withaction:'' displays the text "You do not have permission to edit this page, for the following reason"
*''badaccess-groups:'' displays the text "The action you have requested is limited to users in one of the groups: Administrators, Editors, Reviewers.

These pages do not actually exist, and therefore the standard text message from the database is displayed. If you want to change a message, you must first create the page.

'''To update a system message:'''

#Go to the special page "System messages" (<code>Special:AllMessages</code> )
#[[File:permissionerror-find.png|alt=Customize the message text.|center|thumb|650x650px|Customize the message text.]]Enter the full name of the system message in the "Prefix" field of the filter: The link to the system message apears in red.
#Click on the name to create a page for this system message
#Enter your custom error message and save the page. The system message has now been customized.
#Continue to update any other system messages on the page.
{{Messagebox|boxtype=note|Note text=Many of these messages use parameters (e.g., "$1"), which should be considered when you change the default text. If something went wrong, you can also delete the custom error pages you created - then the default text from the database will be used again.}}
{{Box Links-en|Topic1=https://www.mediawiki.org/wiki/Manual:Interface/Noarticletext |mediawiki.org/wiki/Manual:Interface/Noarticletext}}
[[en:{{FULLPAGENAME}}]]
[[De:Fehlermeldungen]]
[[Category:Customization]]

File:permissionerror-find.png

2025-06-30T07:14:35Z

Lhuyghe: (username removed) (log details removed)

Manual:Extension/BlueSpiceConfigManager

2025-06-20T14:25:35Z

Lhuyghe:

{{DISPLAYTITLE:Config manager}}
{{TOClimit|limit=2}}
__TOC__

With the Config manager, a wiki user with ''sysop'' rights can manage wiki-wide settings in one place. In the [[Manual:Extension/BlueSpiceDiscovery/Main navigation|navigation]], it is located at ''Global navigation > Administration > Configuration''. This link loads the page ''Special:BluespiceConfigManager.''

==Layout==

===Filter options===
All settings can be accessed through the following filter options:

*'''Feature:''' group by type of functionality the setting belongs to (search, administration...)
*'''Extension:''' group by extension name
*'''Package:''' group by BlueSpice edition and services (BlueSpice free, BlueSpice pro, Matomo) 
[[File:Manual:ConfigManager2a.png|alt=config manager filters|center|thumb|401x401px|config manager filter]]

All settings are available in any type of grouping. Changing the grouping type does not add or remove setting options. It just groups them differently. After settings are adjusted, they can be saved by clicking''Save'', or cancelled by clicking ''Reset''.

{{Messagebox|boxtype=note|Note text=If a server administrator has configured a setting to no longer be writable, it will be shown as greyed-out in the config manager. You will have to talk to your server administrator about changing such a setting.}}

===Searching for settings===
A search bar is located above the list of settings. Type in a keyword such as "logo" to find the corresponding setting. The search returns settings regardless of the currently selected group. {{Messagebox|boxtype=note|Note text=The search field has to be empty if you want to see the filter menu instead of the search.}} 
[[File:Manual:configmanager-search.png|alt=Config manager search box|center|thumb|400x400px|Config manager search box]]

==Settings by extension==

=== AI Editing Assistant ===
*'''Provider type:''' One of the supported providers is selected here (OpenAI or Ollama). OpenAI requires its own account, which provides an API key.
* '''Connection params:''' The API key of the provider is entered here (OpenAI) or the endpoint URL (Ollama)

=== BlueSpiceArticleInfo ===
''BlueSpiceArticleInfo'', together with ''[[Manual:Extension/BlueSpiceAuthors|BlueSpiceAuthors]], [[Manual:Extension/BlueSpiceReaders|BlueSpiceReaders]], and [[Manual:Extension/BlueSpiceExtendedSearch|BlueSpiceExtendedSearch]]'' is part of the ''Page information'' in the quality management tools.

* '''Update interval in seconds:''' Sets the refresh rate for the "Last edit" value. By default, this date is updated every 10 seconds via JavaScript.
[[File:Manual:ArticleInfo.png|link=link=Special:FilePath/ArticleInfo3.jpg|alt=|center|thumb|374x374px|article info]]

===BlueSpiceAvatars===
[[File:Manual:configmanager-instantavatar.png|thumb|101x101px|InstantAvatar|link=Special:FilePath/Manual:configmanager-instantavatar.png]]
An avatar image is automatically generated if the user does not upload a profile picture or if the user decides to create an avatar image in the preferences.

*'''Generator'''
**'''InstantAvatar:''' Generates an avatar image based on using the initials of the Real name or the Username
**'''[[wikipedia:Identicon|Identicon:]]''' Generates an avatar image based on parts of the user's IP address. [[File:Manual:configmanager-identicon.png|alt=Identicon|center|thumb|500x500px|Identicon]]

===BlueSpiceBookshelf ===

==== Book ====
*'''Show chapter pager after content:''' Displays previous/next book page navigation at the end of each book page. (1)
*'''Show chapter pager before content:''' Displays previous/next book page navigation at the beginning of each book page. (2) [[File:Manual:book-pagenav.png|alt=Book navigation|center|thumb|450x450px|Book navigation ]] 
*'''Use display title from book source on article:''' Shows the title from the book navigation as page title instead of the page name. 
[[File:Manual:bookdisplaytitle.png|alt=book display title|center|thumb|450x450px|book display title]]
{{Messagebox|boxtype=note|Note text=If the page additionally contains a <nowiki>{{DISPLAYTITLE}}</nowiki> tag, the display title of the page is shown on the page and in the book navigation instead of the page label provided in the book page.}}

* '''Show book chapter numbers in table of contents and headlines:''' The page TOC does not start with the main heading 1, but with the actual number from the book chapter (see screenshot).

[[File:prepand TOC with book chapter.png|alt=Prepended chapter numbers|center|thumb|650x650px|Prepended chapter numbers]]

==== Export ====

* '''Default export template for books:''' The default template for books is used if the export template is not explicitely set for a book export (e.g. in the book metadata).

==== Skinning ====

* '''Show entrypoint "Books":''' Adds a link to the page Special:Books to the main navigation entrypoints.

===BlueSpiceChecklist===

*'''Mark checklist changes as minor edit:''' If this setting is active, changes to a checklist (for example, checking a checkbox) in view mode are logged as minor edits. If this setting is inactive, a change to the checklist is recorded as a regular version in the page history.

=== BlueSpiceDiscovery ===
* '''Activating/Deactivating the Entrypoint links:''' Depending on the BlueSpice version, various links to special pages can be activated for the main navigation. They are called entrypoint links.

[[File:discovery-entrypoint links.png|alt=Entrypoint links for Discovery skin|center|thumb|650x650px|Entrypoint links for Discovery skin]]

* '''[[Manual:Extension/BlueSpiceDiscovery/Main navigation#Choosing a menu type for the main navigation|Menu in main panel of primary sidebar:]]'''
** ''MediaWiki sidebar:'' Activates the M''ediaWiki:Sidebar'' page, which can display a flat list of links.
** ''Namespace main page list'': The pages with the page name "Main Page" for each namespace are automatically linked in the main navigation. It is not possible to add links manually to the navigation.
** ''Subpage tree:'' In the main navigation, the pages with the page name "Main Page" are automatically linked in the respective namespaces. It is not possible to add links manually to the navigation.
** ''Enhanced MediaWiki sidebar'': Activates the M''ediaWiki:Sidebar.json'' page, which can display a more dynamic and hierarchical list of links.
* '''Elements below the page title and below the page content:'''
** page-sentence: display of page status ([[Manual:Extension/FlaggedRevs|Approval status]], [[Manual:Extension/BlueSpiceExpiry|Expiry]])
** categories: display of [[:de:Handbuch:Kategorien_erstellen_und_nutzen|page categories]]
** rating: display of [[Manual:Extension/BlueSpiceRating|page ratings]]
** recommendations: display of [[Manual:Extension/BlueSpiceRating|page recommendations]]
[[File:BlueSpice-Discovery2.png|alt=positioning skin elements|center|thumb|600x600px|positioning skin elements]]

=== BlueSpiceExpiry ===
==== Export ====
*'''Show watermark in PDF:''' Shows the watermark for expired pages in PDFs.

==== Quality assurance ====
* '''Show watermark''' : Shows a watermark on the wiki page itself. [[File:Manual:configmanager-watermark.png|alt=watermark|center|thumb|250x250px|watermark]]

===BlueSpiceExtendedSearch ===

*'''External file paths''': External locations to scan for and index files from. These locations are entered in key/value pairs of Physical path and URL prefix.
**''Physical path: S''torage path. For mounted drives, for example: ''X:\Documents''
**''URL prefix:'' All files indexed from the indexed physical location are prefixed in the search results. It should be used if files are available from a web server. By default, the URL prefix is set to the same value as ''Physical path''.

{| class="wikitable" style="width:100%;"
|+Examples for external file paths
! style="" |Example file
! style="" | Phys. Path
! style="" | URL Prefix
! style="" |Link in results list
|-
| rowspan="3" style="" |S:\Sales\Info\glossaryy.pdf
| rowspan="3" style="" |S:\
| style="" |<nowiki>file:///S:/</nowiki>
| style="" |<nowiki>file:///S:/Sales/Info/glossary.pdf</nowiki>
|-
| style="" |https://sharepoint/Sales/
documents/
| style="" |https://sharepoint/Sales/
documents/Sales/Info/glossary.pdf
|-
| style="" |https://intranet/showdocs
inline.aspx?path=
| style="" |https://intranet/showdocsinline.aspx?
path=/Sales/Info/glossary.pdf
|-
| style="" |/var/www/bluespice/w/mounted_
share/Sales/Info/glossary.pdf
| style="" |/var/www/bluespice/w/
mounted_share/
| style="" |
| style="" |https://wiki.company.local/w/mounted_
share/Sales/Info/glossary.pdf
|}
[[File:Manual:configmanager-addfilepath.png|alt=Add an external file path|center|thumb|650x650px|Add an external file path: (1) confirm the checkmark and (2) save the settings.]]
 

*'''Automatically set language filter''': The search only returns pages whose language (PageLanguage) is identical to the user language (Language). Users can set their language in their [[Manual:Preferences|preferences]]. By default, the language of content pages is the same as the installation language (ContentLanguage) of the wiki. Some extensions can set the language of individual pages independently of the content language of the wiki.. (See: https://www.mediawiki.org/wiki/Manual:Language#Page_content_language). In many wikis, activating this filter has little effect. 
*'''Exclude patterns:''' Files at external file locations can be exluded from search based on regular expression patterns.

=== BlueSpiceFoundation ===

==== Skinning====
{{Messagebox|boxtype=note|icon=|Note text=Since BlueSpice 4.2, the logo and favicon can also be managed via the page [[Manual:Extension/FlexiSkin|Special:Flexiskin]] together with further skin customizations.|bgcolor=}}
*'''Logo path:''' The logo image should be stored in the /images folder of your installation. If you store it in the /skins folder of your BlueSpice installation, it could be overwritten with an upgrade.

'''To upload the logo directly in the wiki:'''

#'''Upload''' the logo on the page from the menu ''Global actions'' > ''File list'' (''Special:ExtendedFilelist'').
#'''Click''' on the thumbnail image of the logo. This opens the logo on a separate page. [[File:Manual:config-logo1.png|alt=logo thumbnail image|center|thumb|280x280px|logo thumbnail image]]
# '''Copy''' the relative logo path from the address bar. In a typical Wiki configuration, this path starts with ''/w/....'' . [[File:Manual:config-logo2.png|alt=relative image path|center|thumb|450x450px|relative image path]]
#'''Paste''' the logo path into the text field for the logo. [[File:Manual:config-logo3.png|alt=logo path|center|thumb|450x450px|logo path]]
#'''Click''' ''Save''.
#'''Refresh''' the page (Strg+F5). If the uploaded logo is too large, you can add the following code snippet to the page ''MediaWiki:Common.css''. This automatically adjusts the image to the height of the main toolbar:<syntaxhighlight lang="css">
.bs-logo a {background-size: contain;}
</syntaxhighlight>

*'''Favicon path:''' The favicon image should be stored in the ''/images'' folder of your installation. If you store it in the /skins folder of your BlueSpice installation, it could be overwritten with an upgrade. [https://de.wikipedia.org/wiki/Favicon Favicon images] have the file extension ''.ico''.

====System====

*'''Allowed file extensions:''' For security reasons, the types of files that users can upload are restricted. Here, you can allow additional file formats. If a file format is blacklisted in the server configuration, adding this file extension here will not allow this file type to be uploaded. See [https://mediawikiwiki:Manual:$wgFileExtensions mediawiki.org/wiki/Manual:$wgFileExtensions] for more info.
{{Xml upload}}

*'''Allowed image extensions:''' The standard web image types are listed here. In general, you want to restrict image uploads to web images. See [https://developer.mozilla.org/en-US/docs/Web/Media/Formats/Image_types developer.mozilla.org/en-US/docs/Web/Media/Formats/Image_types] for more on browser-supported image types.

===BlueSpiceInsertCategory===

*'''Insert category with its parents:''' When a category is inserted on a page, its parent categories are automatically inserted as well.
* '''Set page categories as default in upload dialog:''' When a file is uploaded to the wiki via the visual editor, the categories of the paged are automatically inserted on the file page.

===BlueSpiceInterwikiSearch===

* '''Enable interwiki search:''' Activates interwiki search in this wiki instance. Only farm instances where interwiki search is enabled in the Farm Manager are included in the search results. To prevent this wiki instance from being globally searchable, it must be disabled in the Farm Manager.

* '''Skip over wikis that cannot be accessed or otherwise cannot return results without showing it to the user:''' In the search center, only those wikis are shown to the user in which he or she is logged in. If this setting is deactivated, all wikis with interwiki search that have matching results are listed, but with a warning that the results cannot be shown to the user.

[[File:Interwikisearch config.png|alt=search center interwiki search results with blocked wiki instances.|center|thumb|750x750px|No wikis are skipped for the interwiki search. Results are only shown if the user is authenticated.]]

=== BlueSpiceMatomoConnector ===
If the web analysis service Matomo is available, the corresponding ''Site ID'' for the wiki and the link to Matomo (base URL, e.g., <nowiki>https://analytics.mysite.com/</nowiki>) are entered here.

* '''Show opt-out link in footer:''' Users can opt out of web analytics via the ''Analysis Services'' link in the wiki footer. The target page is ''Special:OptOut''.
* '''BlueSpicePrivacy integration:''' The page SpecialOptOut includes a checkbox for users to opt out of the tracking service.

{{Textbox|boxtype=important|header=Prerequisite:|text=In order to control the Matomo tracking policy using BlueSpicePrivacy, your Matomo installation requires the "AjaxOptOut" plugin module to be installed and activated. Download the plugin from https://plugins.matomo.org/AjaxOptOut and copy it to the /plugins directory of your Matomo installation.|icon=yes}}

=== BlueSpicePageTemplates ===
* '''Force target namespace:''' The page is always created in the target namespace that is associated with the template, even if the user provided a different namespace prefix. In the screenshot below, the user wants to create the page "NewPage" and then selects a template for the QM namespace. The page is, therefore, created as "QM:NewPage" if this setting is activated. [[File:force namespace from template.png|alt=force the namespace of the template|center|thumb|650x650px|force the namespace of the template]]

*'''Hide default templates:''' Hides the default ''Empty page'' template.
*'''Hide template if the page is not to be created in the target namespace:''' Depending on the namespace prefix of the page to be created, templates that are associated with other namespaces will not be shown to the user for selection.

=== BlueSpicePrivacy ===
* '''Enable mandatory cookies:''' Users have to explicitely accept the mandatory cookies to get access to the wiki. If this setting is not activated, users accept the mandatory cookies implicitly.
* '''Enable mandatory "Privacy policy" and "Terms of service"''': Users have to consent to the "Privacy policy" and "Terms of service" to get and to keep access.
* '''Accept "Privacy policy" and "Terms of service" on login''': Accepting the "Privacy policy" and "Terms of service" is integrated into the login process. It is required on first login and everytime a user deactivates the consent in the user preferences.

=== BlueSpiceProDistributionConnector ===
*'''BlueSpice subscription key:''' Sets the number of users as specified in the subscription contract. If this entry is missing, the number of users is limited to 25.
*'''OAuth2 public key, OAuth private key:''' Required if user authentication is configured via [[Referenz:OAuth|OAuth]].v

===BlueSpiceRSSFeeder===

*'''URL whitelist:''' RSS feeds need to be whitelisted here by an administrator before they can be displayed in a wiki page.
*'''Maximum number of allowed redirects:''' If there are URL redirects for any of the whitelisted URLs, the number of redirects needs to be adjusted (usually to 1 or 2).

[[File:Manual:configmanager-RSS.png|alt=RSS Feed settings|center|thumb|450x450px|RSS Feed settings]]

=== BlueSpiceSaferEdit ===
*'''Interval for edit check (seconds):''' Sets the time in seconds for checking if another person is editing the page.
* '''Show current editor:''' Shows or hides the name of the user who is currently editing the page.

=== BlueSpiceTranslationTransfer (farm) ===

* Wenn sich die Namensräume in zwischen Quell- und Zielwiki unterscheiden, müssen sie einander für die Übertragung der Seiten korrekt zugeordnet werden.
* Für jeden Namensraum wird der Quellnamensraum, die Sprache des Zielwikis und der Zielnamensraum angegeben.
* Über die "Hinzufügen"-Schaltfläche können so mehrere Namensräume zugeordnet.
* Am Ende werden die Namensraumzuordnungen über die "Speichern"-Schaltfläche der Konfigurationsverwaltung übernommen.

===BlueSpiceVisualEditorConnector===

*'''Enable VisualEditor for BlueSpice extensions:''' Disabling this setting removes VisualEditor from extensions such as Page Forms or BlueSpiceSocial extensions.
* '''Upload type'''
**''Original:'' User permissions are verified during file upload; file name and namespace of the file can be changed; a category can be assigned and a description of the file is required
**''Simple:'' User permissions are not verified during file upload; the name and namespace of the file can be changed; a category and a description of the file can be provided
**''One click:'' User permissions are not verified during file upload; the image cannot be renamed and no category can be assigned. Only the namespace can, but does not have to be adjusted before uploading) 

===BlueSpiceWhoIsOnline ===

*'''Time in seconds until a user is marked as offline:''' The system checks every ''x'' seconds if a user logged out and no longer displayed as online. This can be less frequent than the update inteval for newly logged-in users.
*'''Update interval in seconds:''' The system checks every ''x'' seconds for users.

=== Cognitive Process Designer ===

* '''Show Processes entry point:''' Displays a link to the process overview page in the entrypoint links of the main navigation.

=== ContentStabilization ===
====Quality assurance====
*'''Include handling:''' If resources are embedded in a page '''and these resource namespace itself has approval enabled''', the following settings can be selected:
{| class="wikitable" style="width:100%;" "
! style="width:220px;" |
! style="" |Behavior
|-
| style="width:220px;" |Versions that were current at the time of release
| style="" |Creates an implicit draft when the resource changes after page approval. The resource will be approved together with the next page approval.
|-
| style="width:220px;" |Approved versions of included pages
| style="" |Only applies if the resource itself can be approved. The latest approved version is displayed on the approved wiki page.
|-
| style="width:220px;" |Current versions of included pages
| style="" |Always shows the most current version of a resource. An implicit draft is not generated.
|}
*'''Show not approved pages for following groups:''' If the <code>user</code> group has been removed from the configuration, users in this group cannot see draft versions. This also applies if they are added as reviewers in a namespace. In this case, only users with the <code>sysop</code> and <code>reviewer</code> permissions can access drafts, unless other groups are specified. These system groups can then only access drafts via the page's version history. All groups that can see page drafts anywhere in the wiki must be explicitly specified here. This setting applies to the entire wiki and cannot be restricted to namespaces.
*'''Allow viewing of first draft version for users who can normally not see drafts:''' If this setting is enabled, all users with read permissions can see the first draft. If disabled, only groups from the setting "The following groups can see draft versions" can see first drafts.
*'''Update semantic properties from approved versions only:''' The attribute value of the page is set from the stable version of the page and not from the draft version.

====Search and navigation====
*'''Index only approved versions:''' Page names and contents of draft pages are not taken into account by the search. If this checkbox is activated, the search index has to be recreated.
====Export====
*'''Show stabilization information in PDF export''': Prints the timestamp for the last approved version below the page headings in the PDF (date of approval and date of last edit before approval). [[File:Manual:configmanager-bookshelf-flaggedrevsinfo.png|centered|mini|400x400px|FlaggedRevs info under the heading]]
=== EnhancedUpload ===
Sets the defaults for the [[Manual:Extension/VisualEditor/Insert images#Advanced settings|advanced image settings]] when uploading and embedding an image into the wiki via drag-and-drop functionality. The default settings determine the orientation, type, and size of the image. These can be adjusted after embedding via the "Advanced settings" of the image on the page.

[[File:Manual:ext enhancedupload en.png|alt=Screenshot of the "Enhanced Upload" configuration|center|thumb|450x450px|Configuration settings for the Enhanced upload]]

*'''Allow mismatched MIME types (potential security risk):''' If the file extension of a file does not match the actual file type, it will still be uploaded if it is listed as an allowed file extension in the wiki.

=== EventBus ===
Eventbus sends notifications to external urls in case something happens in the wiki. For example, if a page is created, an external service could then be started and create a pdf of that page. See the extension's page on [[mediawikiwiki:Extension:EventBus|mediawiki.org]].

=== NumberHeadings ===
* '''Enable heading numbering:''' Displays the numbering from the table of contents before the section headings on a page.[[File:ConfigManager NumberHeadings.png|alt=Selected checkbox for the extension NumberHeadings|center|thumb|550x550px|Number headings]][[File:ConfigManager numbered headings on page.png|alt=Headings of an example page|center|thumb|550x550px|Activated heading numbers]]

===PDFCreator===
[[File:PDFCreator_config.png|alt=Konfiguration for the default page export template and default cover image|center|thumb|650x650px|PDFCreator Konfiguration]]
:
'''Hide namespace prefix in PDF:''' Removes the namespace prefix from titles and from template parameter "title" in the PDF output.
* '''Default export template for pages:''' The default template is shown when users select an export template in "Page" mode. It is also used when clicking on the PDF link for the [[Manual:Extension/ContentDroplets|Content Droplet]] ''PDF Link'' .

* '''Default cover background image'''

Admins can also set a default cover background image. It is applied whenever the document preface of the template contains the standard "intro"-wrapper:<syntaxhighlight lang="html">
<div class="pdfcreator-intro">
....
</div>
</syntaxhighlight>Default image:

<code>/app/bluespice/w/extensions/BlueSpiceBookshelf/data/common/images/bs-cover.png</code>

Output:
[[File:Manual:Standard PDF cover.png|alt=Image of an enlarged keyboard key with book symbol|center|thumb|Default PDF cover image]]

The image path can be deleted. In this case, no image will be output by default.

Alternatively, an uploaded image file can be specified (without a namespace prefix), for example: <code>industry.jpg</code>
[[File:PDFCreator_config_cover.png|alt=Example default image on an exported cover sheet.|center|thumb|424x424px|Default image for the cover sheet]]
If a book has its own bookshelf-image, this will be generated in the PDF when exporting directly from the special page "Books".

=== PluggableAuth ===

== Other settings ==

=== DeepL API ===
The DeepL API configuration can be accessed from the Feature ''Content Structuring.''[[File:Manual:Extension_AdhocTranslation_1743685074718.png|center|thumb|450x450px|DeepL API Key Configuration]]
{{translation}}
[[Category:Administration]]

File:discovery-entrypoint links.png

2025-06-20T14:24:24Z

Lhuyghe: (username removed) (log details removed)

Manual:Extension/BlueSpiceConfigManager

2025-06-20T14:21:54Z

Lhuyghe:

{{DISPLAYTITLE:Config manager}}
{{TOClimit|limit=2}}
__TOC__

With the Config manager, a wiki user with ''sysop'' rights can manage wiki-wide settings in one place. In the [[Manual:Extension/BlueSpiceDiscovery/Main navigation|navigation]], it is located at ''Global navigation > Administration > Configuration''. This link loads the page ''Special:BluespiceConfigManager.''

==Layout==

===Filter options===
All settings can be accessed through the following filter options:

*'''Feature:''' group by type of functionality the setting belongs to (search, administration...)
*'''Extension:''' group by extension name
*'''Package:''' group by BlueSpice edition and services (BlueSpice free, BlueSpice pro, Matomo) 
[[File:Manual:ConfigManager2a.png|alt=config manager filters|center|thumb|401x401px|config manager filter]]

All settings are available in any type of grouping. Changing the grouping type does not add or remove setting options. It just groups them differently. After settings are adjusted, they can be saved by clicking''Save'', or cancelled by clicking ''Reset''.

{{Messagebox|boxtype=note|Note text=If a server administrator has configured a setting to no longer be writable, it will be shown as greyed-out in the config manager. You will have to talk to your server administrator about changing such a setting.}}

===Searching for settings===
A search bar is located above the list of settings. Type in a keyword such as "logo" to find the corresponding setting. The search returns settings regardless of the currently selected group. {{Messagebox|boxtype=note|Note text=The search field has to be empty if you want to see the filter menu instead of the search.}} 
[[File:Manual:configmanager-search.png|alt=Config manager search box|center|thumb|400x400px|Config manager search box]]

==Settings by extension==

=== AI Editing Assistant ===
*'''Provider type:''' One of the supported providers is selected here (OpenAI or Ollama). OpenAI requires its own account, which provides an API key.
* '''Connection params:''' The API key of the provider is entered here (OpenAI) or the endpoint URL (Ollama)

=== BlueSpiceArticleInfo ===
''BlueSpiceArticleInfo'', together with ''[[Manual:Extension/BlueSpiceAuthors|BlueSpiceAuthors]], [[Manual:Extension/BlueSpiceReaders|BlueSpiceReaders]], and [[Manual:Extension/BlueSpiceExtendedSearch|BlueSpiceExtendedSearch]]'' is part of the ''Page information'' in the quality management tools.

* '''Update interval in seconds:''' Sets the refresh rate for the "Last edit" value. By default, this date is updated every 10 seconds via JavaScript.
[[File:Manual:ArticleInfo.png|link=link=Special:FilePath/ArticleInfo3.jpg|alt=|center|thumb|374x374px|article info]]

===BlueSpiceAvatars===
[[File:Manual:configmanager-instantavatar.png|thumb|101x101px|InstantAvatar|link=Special:FilePath/Manual:configmanager-instantavatar.png]]
An avatar image is automatically generated if the user does not upload a profile picture or if the user decides to create an avatar image in the preferences.

*'''Generator'''
**'''InstantAvatar:''' Generates an avatar image based on using the initials of the Real name or the Username
**'''[[wikipedia:Identicon|Identicon:]]''' Generates an avatar image based on parts of the user's IP address. [[File:Manual:configmanager-identicon.png|alt=Identicon|center|thumb|500x500px|Identicon]]

===BlueSpiceBookshelf ===

==== Book ====
*'''Show chapter pager after content:''' Displays previous/next book page navigation at the end of each book page. (1)
*'''Show chapter pager before content:''' Displays previous/next book page navigation at the beginning of each book page. (2) [[File:Manual:book-pagenav.png|alt=Book navigation|center|thumb|450x450px|Book navigation ]] 
*'''Use display title from book source on article:''' Shows the title from the book navigation as page title instead of the page name. 
[[File:Manual:bookdisplaytitle.png|alt=book display title|center|thumb|450x450px|book display title]]
{{Messagebox|boxtype=note|Note text=If the page additionally contains a <nowiki>{{DISPLAYTITLE}}</nowiki> tag, the display title of the page is shown on the page and in the book navigation instead of the page label provided in the book page.}}

* '''Show book chapter numbers in table of contents and headlines:''' The page TOC does not start with the main heading 1, but with the actual number from the book chapter (see screenshot).

[[File:prepand TOC with book chapter.png|alt=Prepended chapter numbers|center|thumb|650x650px|Prepended chapter numbers]]

==== Export ====

* '''Default export template for books:''' The default template for books is used if the export template is not explicitely set for a book export (e.g. in the book metadata).

==== Skinning ====

* '''Show entrypoint "Books":''' Adds a link to the page Special:Books to the main navigation entrypoints.

===BlueSpiceChecklist===

*'''Mark checklist changes as minor edit:''' If this setting is active, changes to a checklist (for example, checking a checkbox) in view mode are logged as minor edits. If this setting is inactive, a change to the checklist is recorded as a regular version in the page history.

=== BlueSpiceDiscovery ===
* '''Deactivating the Entrypoint links:''' Depending on the BlueSpice version, various links to special pages can be activated for the main navigation. They are called entrypoint links.

[[File:discovery-entrypoint links.png|alt=Entrypoint links for Discovery skin|center|thumb|650x650px|Entrypoint links for Discovery skin]]

* '''Menu in main panel of primary sidebar:'''
** ''MediaWiki sidebar:'' Activates the M''ediaWiki:Sidebar'' page, which can display a flat list of links.
** ''Namespace main page list'': The pages with the page name "Main Page" for each namespace are automatically linked in the main navigation. It is not possible to add links manually to the navigation.
** ''Subpage tree:'' In the main navigation, the pages with the page name "Main Page" are automatically linked in the respective namespaces. It is not possible to add links manually to the navigation.
** ''Enhanced MediaWiki sidebar'': Activates the M''ediaWiki:Sidebar.json'' page, which can display a more dynamic and hierarchical list of links.
* '''Elements below the page title and below the page content:'''
** page-sentence: display of page status ([[Manual:Extension/FlaggedRevs|Approval status]], [[Manual:Extension/BlueSpiceExpiry|Expiry]])
** categories: display of [[:de:Handbuch:Kategorien_erstellen_und_nutzen|page categories]]
** rating: display of [[Manual:Extension/BlueSpiceRating|page ratings]]
recommendations: display of [[Manual:Extension/BlueSpiceRating|page recommendations]][[File:BlueSpice-Discovery2.png|alt=positioning skin elements|center|thumb|600x600px|positioning skin elements]]

=== BlueSpiceExpiry ===
==== Export ====
*'''Show watermark in PDF:''' Shows the watermark for expired pages in PDFs.

==== Quality assurance ====
* '''Show watermark''' : Shows a watermark on the wiki page itself. [[File:Manual:configmanager-watermark.png|alt=watermark|center|thumb|250x250px|watermark]]

===BlueSpiceExtendedSearch ===

*'''External file paths''': External locations to scan for and index files from. These locations are entered in key/value pairs of Physical path and URL prefix.
**''Physical path: S''torage path. For mounted drives, for example: ''X:\Documents''
**''URL prefix:'' All files indexed from the indexed physical location are prefixed in the search results. It should be used if files are available from a web server. By default, the URL prefix is set to the same value as ''Physical path''.

{| class="wikitable" style="width:100%;"
|+Examples for external file paths
! style="" |Example file
! style="" | Phys. Path
! style="" | URL Prefix
! style="" |Link in results list
|-
| rowspan="3" style="" |S:\Sales\Info\glossaryy.pdf
| rowspan="3" style="" |S:\
| style="" |<nowiki>file:///S:/</nowiki>
| style="" |<nowiki>file:///S:/Sales/Info/glossary.pdf</nowiki>
|-
| style="" |https://sharepoint/Sales/
documents/
| style="" |https://sharepoint/Sales/
documents/Sales/Info/glossary.pdf
|-
| style="" |https://intranet/showdocs
inline.aspx?path=
| style="" |https://intranet/showdocsinline.aspx?
path=/Sales/Info/glossary.pdf
|-
| style="" |/var/www/bluespice/w/mounted_
share/Sales/Info/glossary.pdf
| style="" |/var/www/bluespice/w/
mounted_share/
| style="" |
| style="" |https://wiki.company.local/w/mounted_
share/Sales/Info/glossary.pdf
|}
[[File:Manual:configmanager-addfilepath.png|alt=Add an external file path|center|thumb|650x650px|Add an external file path: (1) confirm the checkmark and (2) save the settings.]]
 

*'''Automatically set language filter''': The search only returns pages whose language (PageLanguage) is identical to the user language (Language). Users can set their language in their [[Manual:Preferences|preferences]]. By default, the language of content pages is the same as the installation language (ContentLanguage) of the wiki. Some extensions can set the language of individual pages independently of the content language of the wiki.. (See: https://www.mediawiki.org/wiki/Manual:Language#Page_content_language). In many wikis, activating this filter has little effect. 
*'''Exclude patterns:''' Files at external file locations can be exluded from search based on regular expression patterns.

=== BlueSpiceFoundation ===

==== Skinning====
{{Messagebox|boxtype=note|icon=|Note text=Since BlueSpice 4.2, the logo and favicon can also be managed via the page [[Manual:Extension/FlexiSkin|Special:Flexiskin]] together with further skin customizations.|bgcolor=}}
*'''Logo path:''' The logo image should be stored in the /images folder of your installation. If you store it in the /skins folder of your BlueSpice installation, it could be overwritten with an upgrade.

'''To upload the logo directly in the wiki:'''

#'''Upload''' the logo on the page from the menu ''Global actions'' > ''File list'' (''Special:ExtendedFilelist'').
#'''Click''' on the thumbnail image of the logo. This opens the logo on a separate page. [[File:Manual:config-logo1.png|alt=logo thumbnail image|center|thumb|280x280px|logo thumbnail image]]
# '''Copy''' the relative logo path from the address bar. In a typical Wiki configuration, this path starts with ''/w/....'' . [[File:Manual:config-logo2.png|alt=relative image path|center|thumb|450x450px|relative image path]]
#'''Paste''' the logo path into the text field for the logo. [[File:Manual:config-logo3.png|alt=logo path|center|thumb|450x450px|logo path]]
#'''Click''' ''Save''.
#'''Refresh''' the page (Strg+F5). If the uploaded logo is too large, you can add the following code snippet to the page ''MediaWiki:Common.css''. This automatically adjusts the image to the height of the main toolbar:<syntaxhighlight lang="css">
.bs-logo a {background-size: contain;}
</syntaxhighlight>

*'''Favicon path:''' The favicon image should be stored in the ''/images'' folder of your installation. If you store it in the /skins folder of your BlueSpice installation, it could be overwritten with an upgrade. [https://de.wikipedia.org/wiki/Favicon Favicon images] have the file extension ''.ico''.

====System====

*'''Allowed file extensions:''' For security reasons, the types of files that users can upload are restricted. Here, you can allow additional file formats. If a file format is blacklisted in the server configuration, adding this file extension here will not allow this file type to be uploaded. See [https://mediawikiwiki:Manual:$wgFileExtensions mediawiki.org/wiki/Manual:$wgFileExtensions] for more info.
{{Xml upload}}

*'''Allowed image extensions:''' The standard web image types are listed here. In general, you want to restrict image uploads to web images. See [https://developer.mozilla.org/en-US/docs/Web/Media/Formats/Image_types developer.mozilla.org/en-US/docs/Web/Media/Formats/Image_types] for more on browser-supported image types.

===BlueSpiceInsertCategory===

*'''Insert category with its parents:''' When a category is inserted on a page, its parent categories are automatically inserted as well.
* '''Set page categories as default in upload dialog:''' When a file is uploaded to the wiki via the visual editor, the categories of the paged are automatically inserted on the file page.

===BlueSpiceInterwikiSearch===

* '''Enable interwiki search:''' Activates interwiki search in this wiki instance. Only farm instances where interwiki search is enabled in the Farm Manager are included in the search results. To prevent this wiki instance from being globally searchable, it must be disabled in the Farm Manager.

* '''Skip over wikis that cannot be accessed or otherwise cannot return results without showing it to the user:''' In the search center, only those wikis are shown to the user in which he or she is logged in. If this setting is deactivated, all wikis with interwiki search that have matching results are listed, but with a warning that the results cannot be shown to the user.

[[File:Interwikisearch config.png|alt=search center interwiki search results with blocked wiki instances.|center|thumb|750x750px|No wikis are skipped for the interwiki search. Results are only shown if the user is authenticated.]]

=== BlueSpiceMatomoConnector ===
If the web analysis service Matomo is available, the corresponding ''Site ID'' for the wiki and the link to Matomo (base URL, e.g., <nowiki>https://analytics.mysite.com/</nowiki>) are entered here.

* '''Show opt-out link in footer:''' Users can opt out of web analytics via the ''Analysis Services'' link in the wiki footer. The target page is ''Special:OptOut''.
* '''BlueSpicePrivacy integration:''' The page SpecialOptOut includes a checkbox for users to opt out of the tracking service.

{{Textbox|boxtype=important|header=Prerequisite:|text=In order to control the Matomo tracking policy using BlueSpicePrivacy, your Matomo installation requires the "AjaxOptOut" plugin module to be installed and activated. Download the plugin from https://plugins.matomo.org/AjaxOptOut and copy it to the /plugins directory of your Matomo installation.|icon=yes}}

=== BlueSpicePageTemplates ===
* '''Force target namespace:''' The page is always created in the target namespace that is associated with the template, even if the user provided a different namespace prefix. In the screenshot below, the user wants to create the page "NewPage" and then selects a template for the QM namespace. The page is, therefore, created as "QM:NewPage" if this setting is activated. [[File:force namespace from template.png|alt=force the namespace of the template|center|thumb|650x650px|force the namespace of the template]]

*'''Hide default templates:''' Hides the default ''Empty page'' template.
*'''Hide template if the page is not to be created in the target namespace:''' Depending on the namespace prefix of the page to be created, templates that are associated with other namespaces will not be shown to the user for selection.

=== BlueSpicePrivacy ===
* '''Enable mandatory cookies:''' Users have to explicitely accept the mandatory cookies to get access to the wiki. If this setting is not activated, users accept the mandatory cookies implicitly.
* '''Enable mandatory "Privacy policy" and "Terms of service"''': Users have to consent to the "Privacy policy" and "Terms of service" to get and to keep access.
* '''Accept "Privacy policy" and "Terms of service" on login''': Accepting the "Privacy policy" and "Terms of service" is integrated into the login process. It is required on first login and everytime a user deactivates the consent in the user preferences.

=== BlueSpiceProDistributionConnector ===
*'''BlueSpice subscription key:''' Sets the number of users as specified in the subscription contract. If this entry is missing, the number of users is limited to 25.
*'''OAuth2 public key, OAuth private key:''' Required if user authentication is configured via [[Referenz:OAuth|OAuth]].v

===BlueSpiceRSSFeeder===

*'''URL whitelist:''' RSS feeds need to be whitelisted here by an administrator before they can be displayed in a wiki page.
*'''Maximum number of allowed redirects:''' If there are URL redirects for any of the whitelisted URLs, the number of redirects needs to be adjusted (usually to 1 or 2).

[[File:Manual:configmanager-RSS.png|alt=RSS Feed settings|center|thumb|450x450px|RSS Feed settings]]

=== BlueSpiceSaferEdit ===
*'''Interval for edit check (seconds):''' Sets the time in seconds for checking if another person is editing the page.
* '''Show current editor:''' Shows or hides the name of the user who is currently editing the page.

=== BlueSpiceTranslationTransfer (farm) ===

* Wenn sich die Namensräume in zwischen Quell- und Zielwiki unterscheiden, müssen sie einander für die Übertragung der Seiten korrekt zugeordnet werden.
* Für jeden Namensraum wird der Quellnamensraum, die Sprache des Zielwikis und der Zielnamensraum angegeben.
* Über die "Hinzufügen"-Schaltfläche können so mehrere Namensräume zugeordnet.
* Am Ende werden die Namensraumzuordnungen über die "Speichern"-Schaltfläche der Konfigurationsverwaltung übernommen.

===BlueSpiceVisualEditorConnector===

*'''Enable VisualEditor for BlueSpice extensions:''' Disabling this setting removes VisualEditor from extensions such as Page Forms or BlueSpiceSocial extensions.
* '''Upload type'''
**''Original:'' User permissions are verified during file upload; file name and namespace of the file can be changed; a category can be assigned and a description of the file is required
**''Simple:'' User permissions are not verified during file upload; the name and namespace of the file can be changed; a category and a description of the file can be provided
**''One click:'' User permissions are not verified during file upload; the image cannot be renamed and no category can be assigned. Only the namespace can, but does not have to be adjusted before uploading) 

===BlueSpiceWhoIsOnline ===

*'''Time in seconds until a user is marked as offline:''' The system checks every ''x'' seconds if a user logged out and no longer displayed as online. This can be less frequent than the update inteval for newly logged-in users.
*'''Update interval in seconds:''' The system checks every ''x'' seconds for users.

=== Cognitive Process Designer ===

* '''Show Processes entry point:''' Displays a link to the process overview page in the entrypoint links of the main navigation.

=== ContentStabilization ===
====Quality assurance====
*'''Include handling:''' If resources are embedded in a page '''and these resource namespace itself has approval enabled''', the following settings can be selected:
{| class="wikitable" style="width:100%;" "
! style="width:220px;" |
! style="" |Behavior
|-
| style="width:220px;" |Versions that were current at the time of release
| style="" |Creates an implicit draft when the resource changes after page approval. The resource will be approved together with the next page approval.
|-
| style="width:220px;" |Approved versions of included pages
| style="" |Only applies if the resource itself can be approved. The latest approved version is displayed on the approved wiki page.
|-
| style="width:220px;" |Current versions of included pages
| style="" |Always shows the most current version of a resource. An implicit draft is not generated.
|}
*'''Show not approved pages for following groups:''' If the <code>user</code> group has been removed from the configuration, users in this group cannot see draft versions. This also applies if they are added as reviewers in a namespace. In this case, only users with the <code>sysop</code> and <code>reviewer</code> permissions can access drafts, unless other groups are specified. These system groups can then only access drafts via the page's version history. All groups that can see page drafts anywhere in the wiki must be explicitly specified here. This setting applies to the entire wiki and cannot be restricted to namespaces.
*'''Allow viewing of first draft version for users who can normally not see drafts:''' If this setting is enabled, all users with read permissions can see the first draft. If disabled, only groups from the setting "The following groups can see draft versions" can see first drafts.
*'''Update semantic properties from approved versions only:''' The attribute value of the page is set from the stable version of the page and not from the draft version.

====Search and navigation====
*'''Index only approved versions:''' Page names and contents of draft pages are not taken into account by the search. If this checkbox is activated, the search index has to be recreated.
====Export====
*'''Show stabilization information in PDF export''': Prints the timestamp for the last approved version below the page headings in the PDF (date of approval and date of last edit before approval). [[File:Manual:configmanager-bookshelf-flaggedrevsinfo.png|centered|mini|400x400px|FlaggedRevs info under the heading]]
=== EnhancedUpload ===
Sets the defaults for the [[Manual:Extension/VisualEditor/Insert images#Advanced settings|advanced image settings]] when uploading and embedding an image into the wiki via drag-and-drop functionality. The default settings determine the orientation, type, and size of the image. These can be adjusted after embedding via the "Advanced settings" of the image on the page.

[[File:Manual:ext enhancedupload en.png|alt=Screenshot of the "Enhanced Upload" configuration|center|thumb|450x450px|Configuration settings for the Enhanced upload]]

*'''Allow mismatched MIME types (potential security risk):''' If the file extension of a file does not match the actual file type, it will still be uploaded if it is listed as an allowed file extension in the wiki.

=== EventBus ===
Eventbus sends notifications to external urls in case something happens in the wiki. For example, if a page is created, an external service could then be started and create a pdf of that page. See the extension's page on [[mediawikiwiki:Extension:EventBus|mediawiki.org]].

=== NumberHeadings ===
* '''Enable heading numbering:''' Displays the numbering from the table of contents before the section headings on a page.[[File:ConfigManager NumberHeadings.png|alt=Selected checkbox for the extension NumberHeadings|center|thumb|550x550px|Number headings]][[File:ConfigManager numbered headings on page.png|alt=Headings of an example page|center|thumb|550x550px|Activated heading numbers]]

===PDFCreator===
[[File:PDFCreator_config.png|alt=Konfiguration for the default page export template and default cover image|center|thumb|650x650px|PDFCreator Konfiguration]]
:
'''Hide namespace prefix in PDF:''' Removes the namespace prefix from titles and from template parameter "title" in the PDF output.
* '''Default export template for pages:''' The default template is shown when users select an export template in "Page" mode. It is also used when clicking on the PDF link for the [[Manual:Extension/ContentDroplets|Content Droplet]] ''PDF Link'' .

* '''Default cover background image'''

Admins can also set a default cover background image. It is applied whenever the document preface of the template contains the standard "intro"-wrapper:<syntaxhighlight lang="html">
<div class="pdfcreator-intro">
....
</div>
</syntaxhighlight>Default image:

<code>/app/bluespice/w/extensions/BlueSpiceBookshelf/data/common/images/bs-cover.png</code>

Output:
[[File:Manual:Standard PDF cover.png|alt=Image of an enlarged keyboard key with book symbol|center|thumb|Default PDF cover image]]

The image path can be deleted. In this case, no image will be output by default.

Alternatively, an uploaded image file can be specified (without a namespace prefix), for example: <code>industry.jpg</code>
[[File:PDFCreator_config_cover.png|alt=Example default image on an exported cover sheet.|center|thumb|424x424px|Default image for the cover sheet]]
If a book has its own bookshelf-image, this will be generated in the PDF when exporting directly from the special page "Books".

=== PluggableAuth ===

== Other settings ==

=== DeepL API ===
The DeepL API configuration can be accessed from the Feature ''Content Structuring.''[[File:Manual:Extension_AdhocTranslation_1743685074718.png|center|thumb|450x450px|DeepL API Key Configuration]]
{{translation}}
[[Category:Administration]]

Manual:Extension/BlueSpiceConfigManager

2025-06-20T14:19:55Z

Lhuyghe:

{{DISPLAYTITLE:Config manager}}
{{TOClimit|limit=2}}
__TOC__

With the Config manager, a wiki user with ''sysop'' rights can manage wiki-wide settings in one place. In the [[Manual:Extension/BlueSpiceDiscovery/Main navigation|navigation]], it is located at ''Global navigation > Administration > Configuration''. This link loads the page ''Special:BluespiceConfigManager.''

==Layout==

===Filter options===
All settings can be accessed through the following filter options:

*'''Feature:''' group by type of functionality the setting belongs to (search, administration...)
*'''Extension:''' group by extension name
*'''Package:''' group by BlueSpice edition and services (BlueSpice free, BlueSpice pro, Matomo) 
[[File:Manual:ConfigManager2a.png|alt=config manager filters|center|thumb|401x401px|config manager filter]]

All settings are available in any type of grouping. Changing the grouping type does not add or remove setting options. It just groups them differently. After settings are adjusted, they can be saved by clicking''Save'', or cancelled by clicking ''Reset''.

{{Messagebox|boxtype=note|Note text=If a server administrator has configured a setting to no longer be writable, it will be shown as greyed-out in the config manager. You will have to talk to your server administrator about changing such a setting.}}

===Searching for settings===
A search bar is located above the list of settings. Type in a keyword such as "logo" to find the corresponding setting. The search returns settings regardless of the currently selected group. {{Messagebox|boxtype=note|Note text=The search field has to be empty if you want to see the filter menu instead of the search.}} 
[[File:Manual:configmanager-search.png|alt=Config manager search box|center|thumb|400x400px|Config manager search box]]

==Settings by extension==

=== AI Editing Assistant ===
*'''Provider type:''' One of the supported providers is selected here (OpenAI or Ollama). OpenAI requires its own account, which provides an API key.
* '''Connection params:''' The API key of the provider is entered here (OpenAI) or the endpoint URL (Ollama)

=== BlueSpiceArticleInfo ===
''BlueSpiceArticleInfo'', together with ''[[Manual:Extension/BlueSpiceAuthors|BlueSpiceAuthors]], [[Manual:Extension/BlueSpiceReaders|BlueSpiceReaders]], and [[Manual:Extension/BlueSpiceExtendedSearch|BlueSpiceExtendedSearch]]'' is part of the ''Page information'' in the quality management tools.

* '''Update interval in seconds:''' Sets the refresh rate for the "Last edit" value. By default, this date is updated every 10 seconds via JavaScript.
[[File:Manual:ArticleInfo.png|link=link=Special:FilePath/ArticleInfo3.jpg|alt=|center|thumb|374x374px|article info]]

===BlueSpiceAvatars===
[[File:Manual:configmanager-instantavatar.png|thumb|101x101px|InstantAvatar|link=Special:FilePath/Manual:configmanager-instantavatar.png]]
An avatar image is automatically generated if the user does not upload a profile picture or if the user decides to create an avatar image in the preferences.

*'''Generator'''
**'''InstantAvatar:''' Generates an avatar image based on using the initials of the Real name or the Username
**'''[[wikipedia:Identicon|Identicon:]]''' Generates an avatar image based on parts of the user's IP address. [[File:Manual:configmanager-identicon.png|alt=Identicon|center|thumb|500x500px|Identicon]]

===BlueSpiceBookshelf ===

==== Book ====
*'''Show chapter pager after content:''' Displays previous/next book page navigation at the end of each book page. (1)
*'''Show chapter pager before content:''' Displays previous/next book page navigation at the beginning of each book page. (2) [[File:Manual:book-pagenav.png|alt=Book navigation|center|thumb|450x450px|Book navigation ]] 
*'''Use display title from book source on article:''' Shows the title from the book navigation as page title instead of the page name. 
[[File:Manual:bookdisplaytitle.png|alt=book display title|center|thumb|450x450px|book display title]]
{{Messagebox|boxtype=note|Note text=If the page additionally contains a <nowiki>{{DISPLAYTITLE}}</nowiki> tag, the display title of the page is shown on the page and in the book navigation instead of the page label provided in the book page.}}

* '''Show book chapter numbers in table of contents and headlines:''' The page TOC does not start with the main heading 1, but with the actual number from the book chapter (see screenshot).

[[File:prepand TOC with book chapter.png|alt=Prepended chapter numbers|center|thumb|650x650px|Prepended chapter numbers]]

==== Export ====

* '''Default export template for books:''' The default template for books is used if the export template is not explicitely set for a book export (e.g. in the book metadata).

==== Skinning ====

* '''Show entrypoint "Books":''' Adds a link to the page Special:Books to the main navigation entrypoints.

===BlueSpiceChecklist===

*'''Mark checklist changes as minor edit:''' If this setting is active, changes to a checklist (for example, checking a checkbox) in view mode are logged as minor edits. If this setting is inactive, a change to the checklist is recorded as a regular version in the page history.

=== BlueSpiceDiscovery ===
* '''Deactivating the Entrypoint links:''' Depending on the BlueSpice version, various links to special pages can be activated for the main navigation. They are called entrypoint links.

[[File:discovery-entrypoint links.png|alt=Entrypoint links for Discovery skin|center|thumb|650x650px|Entrypoint links for Discovery skin]]

* '''Menu in main panel of primary sidebar:'''
** ''MediaWiki sidebar:'' Activates the M''ediaWiki:Sidebar'' page, which can display a flat list of links.
** ''Namespace main page list'': The pages with the page name "Main Page" for each namespace are automatically linked in the main navigation. It is not possible to add links manually to the navigation.
** ''Subpage tree:'' In the main navigation, the pages with the page name "Main Page" are automatically linked in the respective namespaces. It is not possible to add links manually to the navigation.
** ''Enhanced MediaWiki sidebar'': Activates the M''ediaWiki:Sidebar.json'' page, which can display a more dynamic and hierarchical list of links.
* '''Elements below the page title and below the page content:'''
** page-sentence: display of page status ([[Manual:Extension/FlaggedRevs|Approval status]], [[Manual:Extension/BlueSpiceExpiry|Expiry]])
** categories: display of [[:de:Handbuch:Kategorien_erstellen_und_nutzen|page categories]]
** rating: display of [[Manual:Extension/BlueSpiceRating|page ratings]]
recommendations: display of [[Manual:Extension/BlueSpiceRating|page recommendations]][[File:BlueSpice-Discovery2.png|alt=positioning skin elements|center|thumb|600x600px|positioning skin elements]]

=== BlueSpiceExpiry ===
==== Export ====
*'''Show watermark in PDF:''' Shows the watermark for expired pages in PDFs.

==== Quality assurance ====
* '''Show watermark''' : Shows a watermark on the wiki page itself. [[File:Manual:configmanager-watermark.png|alt=watermark|center|thumb|250x250px|watermark]]

===BlueSpiceExtendedSearch ===

*'''External file paths''': External locations to scan for and index files from. These locations are entered in key/value pairs of Physical path and URL prefix.
**''Physical path: S''torage path. For mounted drives, for example: ''X:\Documents''
**''URL prefix:'' All files indexed from the indexed physical location are prefixed in the search results. It should be used if files are available from a web server. By default, the URL prefix is set to the same value as ''Physical path''.

{| class="wikitable" style="width:100%;"
|+Examples for external file paths
! style="" |Example file
! style="" | Phys. Path
! style="" | URL Prefix
! style="" |Link in results list
|-
| rowspan="3" style="" |S:\Sales\Info\glossaryy.pdf
| rowspan="3" style="" |S:\
| style="" |<nowiki>file:///S:/</nowiki>
| style="" |<nowiki>file:///S:/Sales/Info/glossary.pdf</nowiki>
|-
| style="" |https://sharepoint/Sales/
documents/
| style="" |https://sharepoint/Sales/
documents/Sales/Info/glossary.pdf
|-
| style="" |https://intranet/showdocs
inline.aspx?path=
| style="" |https://intranet/showdocsinline.aspx?
path=/Sales/Info/glossary.pdf
|-
| style="" |/var/www/bluespice/w/mounted_
share/Sales/Info/glossary.pdf
| style="" |/var/www/bluespice/w/
mounted_share/
| style="" |
| style="" |https://wiki.company.local/w/mounted_
share/Sales/Info/glossary.pdf
|}
[[File:Manual:configmanager-addfilepath.png|alt=Add an external file path|center|thumb|650x650px|Add an external file path: (1) confirm the checkmark and (2) save the settings.]]
 

*'''Automatically set language filter''': The search only returns pages whose language (PageLanguage) is identical to the user language (Language). Users can set their language in their [[Manual:Preferences|preferences]]. By default, the language of content pages is the same as the installation language (ContentLanguage) of the wiki. Some extensions can set the language of individual pages independently of the content language of the wiki.. (See: https://www.mediawiki.org/wiki/Manual:Language#Page_content_language). In many wikis, activating this filter has little effect. 
*'''Exclude patterns:''' Files at external file locations can be exluded from search based on regular expression patterns.

=== BlueSpiceFoundation ===

==== Skinning====
{{Messagebox|boxtype=note|icon=|Note text=Since BlueSpice 4.2, the logo and favicon can also be managed via the page [[Manual:Extension/FlexiSkin|Special:Flexiskin]] together with further skin customizations.|bgcolor=}}
*'''Logo path:''' The logo image should be stored in the /images folder of your installation. If you store it in the /skins folder of your BlueSpice installation, it could be overwritten with an upgrade.

'''To upload the logo directly in the wiki:'''

#'''Upload''' the logo on the page from the menu ''Global actions'' > ''File list'' (''Special:ExtendedFilelist'').
#'''Click''' on the thumbnail image of the logo. This opens the logo on a separate page. [[File:Manual:config-logo1.png|alt=logo thumbnail image|center|thumb|280x280px|logo thumbnail image]]
# '''Copy''' the relative logo path from the address bar. In a typical Wiki configuration, this path starts with ''/w/....'' . [[File:Manual:config-logo2.png|alt=relative image path|center|thumb|450x450px|relative image path]]
#'''Paste''' the logo path into the text field for the logo. [[File:Manual:config-logo3.png|alt=logo path|center|thumb|450x450px|logo path]]
#'''Click''' ''Save''.
#'''Refresh''' the page (Strg+F5). If the uploaded logo is too large, you can add the following code snippet to the page ''MediaWiki:Common.css''. This automatically adjusts the image to the height of the main toolbar:<syntaxhighlight lang="css">
.bs-logo a {background-size: contain;}
</syntaxhighlight>

*'''Favicon path:''' The favicon image should be stored in the ''/images'' folder of your installation. If you store it in the /skins folder of your BlueSpice installation, it could be overwritten with an upgrade. [https://de.wikipedia.org/wiki/Favicon Favicon images] have the file extension ''.ico''.

====System====

*'''Allowed file extensions:''' For security reasons, the types of files that users can upload are restricted. Here, you can allow additional file formats. If a file format is blacklisted in the server configuration, adding this file extension here will not allow this file type to be uploaded. See [https://mediawikiwiki:Manual:$wgFileExtensions mediawiki.org/wiki/Manual:$wgFileExtensions] for more info.
{{Xml upload}}

*'''Allowed image extensions:''' The standard web image types are listed here. In general, you want to restrict image uploads to web images. See [https://developer.mozilla.org/en-US/docs/Web/Media/Formats/Image_types developer.mozilla.org/en-US/docs/Web/Media/Formats/Image_types] for more on browser-supported image types.

===BlueSpiceInsertCategory===

*'''Insert category with its parents:''' When a category is inserted on a page, its parent categories are automatically inserted as well.
* '''Set page categories as default in upload dialog:''' When a file is uploaded to the wiki via the visual editor, the categories of the paged are automatically inserted on the file page.

===BlueSpiceInterwikiSearch===

* '''Enable interwiki search:''' Activates interwiki search in this wiki instance. Only farm instances where interwiki search is enabled in the Farm Manager are included in the search results. To prevent this wiki instance from being globally searchable, it must be disabled in the Farm Manager.

* '''Skip over wikis that cannot be accessed or otherwise cannot return results without showing it to the user:''' In the search center, only those wikis are shown to the user in which he or she is logged in. If this setting is deactivated, all wikis with interwiki search that have matching results are listed, but with a warning that the results cannot be shown to the user.

[[File:Interwikisearch config.png|alt=search center interwiki search results with blocked wiki instances.|center|thumb|750x750px|No wikis are skipped for the interwiki search. Results are only shown if the user is authenticated.]]

=== BlueSpiceMatomoConnector ===
If the web analysis service Matomo is available, the corresponding ''Site ID'' for the wiki and the link to Matomo (base URL, e.g., <nowiki>https://analytics.mysite.com/</nowiki>) are entered here.

* '''Show opt-out link in footer:''' Users can opt out of web analytics via the ''Analysis Services'' link in the wiki footer. The target page is ''Special:OptOut''.
* '''BlueSpicePrivacy integration:''' The page SpecialOptOut includes a checkbox for users to opt out of the tracking service.

{{Textbox|boxtype=important|header=Prerequisite:|text=In order to control the Matomo tracking policy using BlueSpicePrivacy, your Matomo installation requires the "AjaxOptOut" plugin module to be installed and activated. Download the plugin from https://plugins.matomo.org/AjaxOptOut and copy it to the /plugins directory of your Matomo installation.|icon=yes}}

=== BlueSpicePageTemplates ===
* '''Force target namespace:''' The page is always created in the target namespace that is associated with the template, even if the user provided a different namespace prefix. In the screenshot below, the user wants to create the page "NewPage" and then selects a template for the QM namespace. The page is, therefore, created as "QM:NewPage" if this setting is activated. [[File:force namespace from template.png|alt=force the namespace of the template|center|thumb|650x650px|force the namespace of the template]]

*'''Hide default templates:''' Hides the default ''Empty page'' template.
*'''Hide template if the page is not to be created in the target namespace:''' Depending on the namespace prefix of the page to be created, templates that are associated with other namespaces will not be shown to the user for selection.

=== BlueSpicePrivacy ===
* '''Enable mandatory cookies:''' Users have to explicitely accept the mandatory cookies to get access to the wiki. If this setting is not activated, users accept the mandatory cookies implicitly.
* '''Enable mandatory "Privacy policy" and "Terms of service"''': Users have to consent to the "Privacy policy" and "Terms of service" to get and to keep access.
* '''Accept "Privacy policy" and "Terms of service" on login''': Accepting the "Privacy policy" and "Terms of service" is integrated into the login process. It is required on first login and everytime a user deactivates the consent in the user preferences.

=== BlueSpiceProDistributionConnector ===
*'''BlueSpice subscription key:''' Sets the number of users as specified in the subscription contract. If this entry is missing, the number of users is limited to 25.
*'''OAuth2 public key, OAuth private key:''' Required if user authentication is configured via [[Referenz:OAuth|OAuth]].v

===BlueSpiceRSSFeeder===

*'''URL whitelist:''' RSS feeds need to be whitelisted here by an administrator before they can be displayed in a wiki page.
*'''Maximum number of allowed redirects:''' If there are URL redirects for any of the whitelisted URLs, the number of redirects needs to be adjusted (usually to 1 or 2).

[[File:Manual:configmanager-RSS.png|alt=RSS Feed settings|center|thumb|450x450px|RSS Feed settings]]

=== BlueSpiceSaferEdit ===
*'''Interval for lookup for concurrent editings:''' Sets the time in seconds for checking if another person is editing the page.
* '''Show name of current editor:''' Shows or hides the name of the user who is currently editing the page.

=== BlueSpiceTranslationTransfer (farm) ===

* Wenn sich die Namensräume in zwischen Quell- und Zielwiki unterscheiden, müssen sie einander für die Übertragung der Seiten korrekt zugeordnet werden.
* Für jeden Namensraum wird der Quellnamensraum, die Sprache des Zielwikis und der Zielnamensraum angegeben.
* Über die "Hinzufügen"-Schaltfläche können so mehrere Namensräume zugeordnet.
* Am Ende werden die Namensraumzuordnungen über die "Speichern"-Schaltfläche der Konfigurationsverwaltung übernommen.

===BlueSpiceVisualEditorConnector===

*'''Enable VisualEditor for BlueSpice extensions:''' Disabling this setting removes VisualEditor from extensions such as Page Forms or BlueSpiceSocial extensions.
* '''Upload type'''
**''Original:'' User permissions are verified during file upload; file name and namespace of the file can be changed; a category can be assigned and a description of the file is required
**''Simple:'' User permissions are not verified during file upload; the name and namespace of the file can be changed; a category and a description of the file can be provided
**''One click:'' User permissions are not verified during file upload; the image cannot be renamed and no category can be assigned. Only the namespace can, but does not have to be adjusted before uploading) 

===BlueSpiceWhoIsOnline ===

*'''Time in seconds until a user is marked as offline:''' The system checks every ''x'' seconds if a user logged out and no longer displayed as online. This can be less frequent than the update inteval for newly logged-in users.
*'''Update interval in seconds:''' The system checks every ''x'' seconds for users.

=== Cognitive Process Designer ===

* '''Show Processes entry point:''' Displays a link to the process overview page in the entrypoint links of the main navigation.

=== ContentStabilization ===
====Quality assurance====
*'''Include handling:''' If resources are embedded in a page '''and these resource namespace itself has approval enabled''', the following settings can be selected:
{| class="wikitable" style="width:100%;" "
! style="width:220px;" |
! style="" |Behavior
|-
| style="width:220px;" |Versions that were current at the time of release
| style="" |Creates an implicit draft when the resource changes after page approval. The resource will be approved together with the next page approval.
|-
| style="width:220px;" |Approved versions of included pages
| style="" |Only applies if the resource itself can be approved. The latest approved version is displayed on the approved wiki page.
|-
| style="width:220px;" |Current versions of included pages
| style="" |Always shows the most current version of a resource. An implicit draft is not generated.
|}
*'''Show not approved pages for following groups:''' If the <code>user</code> group has been removed from the configuration, users in this group cannot see draft versions. This also applies if they are added as reviewers in a namespace. In this case, only users with the <code>sysop</code> and <code>reviewer</code> permissions can access drafts, unless other groups are specified. These system groups can then only access drafts via the page's version history. All groups that can see page drafts anywhere in the wiki must be explicitly specified here. This setting applies to the entire wiki and cannot be restricted to namespaces.
*'''Allow viewing of first draft version for users who can normally not see drafts:''' If this setting is enabled, all users with read permissions can see the first draft. If disabled, only groups from the setting "The following groups can see draft versions" can see first drafts.
*'''Update semantic properties from approved versions only:''' The attribute value of the page is set from the stable version of the page and not from the draft version.

====Search and navigation====
*'''Index only approved versions:''' Page names and contents of draft pages are not taken into account by the search. If this checkbox is activated, the search index has to be recreated.
====Export====
*'''Show stabilization information in PDF export''': Prints the timestamp for the last approved version below the page headings in the PDF (date of approval and date of last edit before approval). [[File:Manual:configmanager-bookshelf-flaggedrevsinfo.png|centered|mini|400x400px|FlaggedRevs info under the heading]]
=== EnhancedUpload ===
Sets the defaults for the [[Manual:Extension/VisualEditor/Insert images#Advanced settings|advanced image settings]] when uploading and embedding an image into the wiki via drag-and-drop functionality. The default settings determine the orientation, type, and size of the image. These can be adjusted after embedding via the "Advanced settings" of the image on the page.

[[File:Manual:ext enhancedupload en.png|alt=Screenshot of the "Enhanced Upload" configuration|center|thumb|450x450px|Configuration settings for the Enhanced upload]]

*'''Allow mismatched MIME types (potential security risk):''' If the file extension of a file does not match the actual file type, it will still be uploaded if it is listed as an allowed file extension in the wiki.

=== EventBus ===
Eventbus sends notifications to external urls in case something happens in the wiki. For example, if a page is created, an external service could then be started and create a pdf of that page. See the extension's page on [[mediawikiwiki:Extension:EventBus|mediawiki.org]].

=== NumberHeadings ===
* '''Enable heading numbering:''' Displays the numbering from the table of contents before the section headings on a page.[[File:ConfigManager NumberHeadings.png|alt=Selected checkbox for the extension NumberHeadings|center|thumb|550x550px|Number headings]][[File:ConfigManager numbered headings on page.png|alt=Headings of an example page|center|thumb|550x550px|Activated heading numbers]]

===PDFCreator===
[[File:PDFCreator_config.png|alt=Konfiguration for the default page export template and default cover image|center|thumb|650x650px|PDFCreator Konfiguration]]
:
'''Hide namespace prefix in PDF:''' Removes the namespace prefix from titles and from template parameter "title" in the PDF output.
* '''Default export template for pages:''' The default template is shown when users select an export template in "Page" mode. It is also used when clicking on the PDF link for the [[Manual:Extension/ContentDroplets|Content Droplet]] ''PDF Link'' .

* '''Default cover background image'''

Admins can also set a default cover background image. It is applied whenever the document preface of the template contains the standard "intro"-wrapper:<syntaxhighlight lang="html">
<div class="pdfcreator-intro">
....
</div>
</syntaxhighlight>Default image:

<code>/app/bluespice/w/extensions/BlueSpiceBookshelf/data/common/images/bs-cover.png</code>

Output:
[[File:Manual:Standard PDF cover.png|alt=Image of an enlarged keyboard key with book symbol|center|thumb|Default PDF cover image]]

The image path can be deleted. In this case, no image will be output by default.

Alternatively, an uploaded image file can be specified (without a namespace prefix), for example: <code>industry.jpg</code>
[[File:PDFCreator_config_cover.png|alt=Example default image on an exported cover sheet.|center|thumb|424x424px|Default image for the cover sheet]]
If a book has its own bookshelf-image, this will be generated in the PDF when exporting directly from the special page "Books".

=== PluggableAuth ===

== Other settings ==

=== DeepL API ===
The DeepL API configuration can be accessed from the Feature ''Content Structuring.''[[File:Manual:Extension_AdhocTranslation_1743685074718.png|center|thumb|450x450px|DeepL API Key Configuration]]
{{translation}}
[[Category:Administration]]

Manual:Extension/Rating

2025-06-20T13:49:15Z

Lhuyghe: Redirected page to Manual:Extension/BlueSpiceRating

#REDIRECT [[Manual:Extension/BlueSpiceRating]]<bookshelf src="Book:User manual" />

Manual:Extension/Page Forms

2025-06-20T13:48:44Z

Lhuyghe:

'''Page Forms''' allows you to enter parameter values for [[Manual:Templates|templates]] via a form.

The use of the extension is [[mediawikiwiki:Extension:Page_Forms|documented extensively on MediaWiki]].

==Main features==

*'''Definition pages in the namespace ''Form''''' The New forms can be created using the special page <code>Special: CreateForm</code>. Here, users select an existing template which provides the paramaters for the form. This means that before a form is created, the required template is always created first. All created form definition pages are saved in the ''Form'' namespace. Subsequent edits to the form definition page have to be made in source editing mode.
*'''Application example: info boxes''' Page Forms is often used to add and edit infoboxes on a wiki page. If [https://www.semantic-mediawiki.org/wiki/Semantic_MediaWiki Semantic MediaWiki] is used, the collected data in the templates can be stored and retrieved.
*'''Edit existing forms values via menu item''' Existing values in a template can be updated using the menu item "Edit with form" of the page edit button, for example.
*'''Automatic completion of fields''' Users Users are offered existing values when entering them, depending on the form input type. This reduces problems with naming ambiguities, spelling, etc.
*'''Free text field''' Free text on the page that is not part of the template itself can be displayed in a separate input field called "Free text" for editing directly in forms mode.

== Getting Started ==
To make creating your first form easier, you can start with the documentation on the following pages:

* '''Create a form:''' After you have created a template, you can create the corresponding form using the ''Special:Create Form'' page. This special page supports you in creating the form. However, subsequent editing takes place directly in the form's source code.
* '''Form fields:''' [[mediawikiwiki:Extension:Page_Forms/Input_types|Types of form fields]]
* '''Link the form to the template:''' Since the template exists before the form, it must subsequently be manually linked to the new form
** [[mediawikiwiki:Extension:Page_Forms/Linking_to_forms|within the template]]
** As an additional [[mediawikiwiki:Extension:Page_Forms/The_"edit_with_form"_tab|edit link directly in the page's edit menu]]

==BlueSpice input types==
In addition to the [https://www.mediawiki.org/wiki/Extension:Page_Forms/Input_types?action=view#The_input_types default input types], BlueSpice offers the following additional input types:
{| class="contenttable-blue" style="width:950px;"
! style="background-color:rgb(239, 243, 249);text-align:inherit;box-sizing:inherit;padding:4px;border:1px solid rgb(177, 185, 207);color:rgb(62, 83, 137);" class="" |Input type
! style="background-color:rgb(239, 243, 249);text-align:inherit;box-sizing:inherit;padding:4px;border:1px solid rgb(177, 185, 207);color:rgb(62, 83, 137);" class="" |Result
! style="background-color:rgb(239, 243, 249);text-align:inherit;box-sizing:inherit;padding:4px;border:1px solid rgb(177, 185, 207);color:rgb(62, 83, 137);" class="" |Function
|- style="box-sizing: inherit; border: 1px solid rgb(177, 185, 207); border-spacing: 0px; border-collapse: collapse; padding: 10px;"
| style="box-sizing:inherit;padding:10px;border:1px solid rgb(177, 185, 207);border-spacing:0px;border-collapse:collapse;" |bs-grid{{Bsvs|bsvTo=4.5}}
| style="box-sizing:inherit;padding:10px;border:1px solid rgb(177, 185, 207);border-spacing:0px;border-collapse:collapse;" | -
| style="box-sizing:inherit;padding:10px;border:1px solid rgb(177, 185, 207);border-spacing:0px;border-collapse:collapse;" |-
|- style="box-sizing: inherit; border: 1px solid rgb(177, 185, 207); border-spacing: 0px; border-collapse: collapse; padding: 10px;"
| style="box-sizing:inherit;padding:10px;border:1px solid rgb(177, 185, 207);border-spacing:0px;border-collapse:collapse;" |bs-usercombo
| style="box-sizing:inherit;padding:10px;border:1px solid rgb(177, 185, 207);border-spacing:0px;border-collapse:collapse;" |User name (with link to the profile page)
| style="box-sizing:inherit;padding:10px;border:1px solid rgb(177, 185, 207);border-spacing:0px;border-collapse:collapse;" |(Single selection).
|- style="box-sizing: inherit; border: 1px solid rgb(177, 185, 207); border-spacing: 0px; border-collapse: collapse; padding: 10px;"
| style="box-sizing:inherit;padding:10px;border:1px solid rgb(177, 185, 207);border-spacing:0px;border-collapse:collapse;" |bs-usertags
| style="box-sizing:inherit;padding:10px;border:1px solid rgb(177, 185, 207);border-spacing:0px;border-collapse:collapse;" |Comma-separated user name
| style="box-sizing:inherit;padding:10px;border:1px solid rgb(177, 185, 207);border-spacing:0px;border-collapse:collapse;" |Menu that allows to select existing wiki users
(multiple selections possible).

Note: To link to the profile page, the corresponding parameter in the template needs to be formated accordingly:

<code style="box-sizing: inherit; font-family: monospace, Courier; font-size: 13.5px; padding: 1px 4px; color: black; background-color: rgb(249, 249, 249); border-radius: 2px; border: 1px solid rgb(221, 221, 221);"><nowiki>{{#arraymap:{{{myParameter|}}}|,|@@@|[[User:@@@|@@@]]}}</nowiki></code>
|- style="box-sizing: inherit; border: 1px solid rgb(177, 185, 207); border-spacing: 0px; border-collapse: collapse; padding: 10px;"
| style="box-sizing:inherit;padding:10px;border:1px solid rgb(177, 185, 207);border-spacing:0px;border-collapse:collapse;" |bs-mvvisualeditor
| style="box-sizing:inherit;padding:10px;border:1px solid rgb(177, 185, 207);border-spacing:0px;border-collapse:collapse;" |Formatted text
| style="box-sizing:inherit;padding:10px;border:1px solid rgb(177, 185, 207);border-spacing:0px;border-collapse:collapse;" |Text box with simplified [[:de:VisualEditor|VisualEditor]].
|}

==Special pages==
Page Forms defines some special pages that are used for data input and data maintenance.

Among others, the following [[mediawikiwiki:Extension:Page_Forms/Special_pages|special pages]] are important for data collection:
[[File:Erweiterung-Page Forms-12190872.drawio.png|center|512x512px]]

 
{{Box Links-en|Topic1=[[mediawikiwiki:Extension:Page_Forms/de|https://www.mediawiki.org/wiki/Extension:Page_Forms/en]]|Topic2=[[Reference:Page Forms]]}}
{{translation}}

Manual:Extension/DateTimeTools

2025-06-20T13:48:11Z

Lhuyghe:

{{BSVersion|bsvFrom=4.4|bsvFeature=The "Date" Content Droplet}}[[File:droplet-date-inspector.png|alt=Date inspector with Insert-button|center|thumb|350x350px|The "Date" Content Droplet]]

Manual:Extension/DateTimeTools

2025-06-20T13:48:01Z

Lhuyghe:

{{BSVersion|bsvFrom=4.4|bsvFeature=The "Date" Content Droplet}}[[File:droplet-date-inspector.png|alt=Date inspector with Insert-button|center|thumb|350x350px|The "Date" Content Droplet]]
{{translation}}

Manual:Extension/DrawioEditor

2025-06-20T13:47:22Z

Lhuyghe:

<bookshelf src="Book:User manual" />
{{DISPLAYTITLE:Drawio}}

'''Drawio''' offers extensive drawing possibilities for process flowcharts, infographics and other visualizations on a wiki page. Descriptive graphics like process chains or decision trees can be constructed directly on a wiki page.
==Embedding the Drawio editor==
'''To insert a drawing in the [[Manual:Extension/VisualEditor|visual editor]]:'''
#'''Create or choose''' a page where you want to insert a drawing.
#'''Open''' ''Content droplet'' menu from the editor toolbar.[[File:Manual:Manual Extension DrawioEditor 1748351104784.png|alt=Content Droplet dialog and selection of Diagram|center|thumb|400x400px|Diagram Content Droplet]]
#'''Choose''' ''diagram'' from the list of content droplets.
#'''Click''' ''Insert''.
#This opens a dialog box. '''Enter''' a name for your drawing. This name is used to version your diagram as a PNG file in the wiki.
#'''Click''' ''Insert.'' [[File:Manual:Manual Extension DrawioEditor 1748351273074.png|alt=drawio insert dialog|thumb|drawio insert dialog|center]]
# This inserts the tag <code><nowiki><drawio filename="<nameoffile>"></nowiki></code> in your source code.
#'''Save''' the page.
The drawio editor is now available on the page.
[[File:DrawioEditor placeholder.png|alt=Drawio placeholder and [Edit] link|center|thumb|600x600px|Drawio placeholder and [Edit] link]]

== Editing the diagram ==
{{Messagebox|boxtype=note|icon=|Note text=To open the drawio editor, you always click on the ''[Edit]'' link in '''page view mode'''.|bgcolor=}}
'''To edit the diagram:'''
#'''Click''' ''Edit'' on the saved page next to the drawio placeholder or your already saved diagram. [[File:800px-drawio-processchart.png|alt=draw.io chart|center|thumb|432x432px|the open drawio editor]]
#'''Add''' any needed shapes to your diagram.
#'''Click''' ''Save'' in the drawio window to save your drawing.
#'''Click''' ''Exit'' next to the ''Save'' button to close the editor.

=== Adding links to shapes ===
'''To add a link to a shape:'''

# '''Right-click''' to open the shape menu.
# '''Click''' Edit Link.[[File:DrawioEditor shape menu.png|alt=Shape menu|center|thumb|650x650px|Shape menu]]
# '''Provide''' the full path of the link. The full path must also be specified for internal wiki pages (example external link: <nowiki>https://bluespice.com</nowiki>, example internal link: <nowiki>https://de.wiki.bluespice.com/wiki/Manual:Extension/DrawioEditor</nowiki>). '''Note:''' The displayed dropdown menu currently has no function in BlueSpice.[[File:DrawioEditor edit link.png|alt=annotated screenshot of the "edit link" dialog|center|thumb|500x500px|(1) Enter full url link path (2) Link can be opened in new window (3) Dropdown is not used in BlueSpice.]]
# '''Click''' ''Apply''.
# '''Repeat''' steps 1-4 for other shapes in the diagram.
# '''Click''' ''Save''.
# '''Click''' ''Exit'' to close the editor.

If you don't see the changes yet, click F5 on your keyboard to refresh the page.

{{Textbox|boxtype=important|header=Avoid auto-resizing of linked shapes:|text=By default, drawio images are resized to always fit into the content area.

Since the links are implemented as map coordinates, the png image cannot be resized without breaking the link boundaries. To avoid this, you can disable automatic resizing of your drawio images with the following css.|icon=yes}}
===Remove auto-resizing auf drawio images===
Add the following rules to MediaWiki:Common.css<syntaxhighlight language="css">
/*Drawio png - do not auto-resize preview images when links are added directly to the shapes */
div[id*=drawio-img-box] {
overflow-x:scroll
}

/*Drawio png - do not auto-resize preview images when links are created as image maps from file description page */
div[id*=drawio-img-box] img {
height: initial;
max-width: initial;
width: initial;
}
</syntaxhighlight>

This will remove the auto-resizing behavior from all drawio preview images.

To apply this styling to only some drawio images, you could add a wrapper to these images in source editing mode. For example:
<syntaxhighlight language="text">
<div class="drawio-linked">
<drawio filename="processmap" alt="Processmap showing the management, core, and supporting processes ">
</drawio>
</div>
</syntaxhighlight>

In this case, do not add the above styles to your Common.css, but use these rules instead:

<syntaxhighlight language="css">
/*Drawio png - do not auto-resize drawio diagrams that are wrapped in a container with class drawio-linked */
.drawio-linked {
overflow-x:scroll
}

.drawio-linked img {
height: initial!important;
max-width: initial!important;
width: initial!important;
}
</syntaxhighlight>

==PNG and SVG format==
In BlueSpice, drawio diagrams are saved in PNG format by default. It is possible to [[Reference:DrawioEditor|configure "svg" as image type]].
== Import of existing diagrams ==
===Visio diagrams===
[[File:750px-drawio-import_vsdx.png|alt=Importing a .vsdx file|center|thumb|565x565px|Importing a .vsdx file]]
You can import files with the extension .vsdx directly into the drawio editor and edit them further. To do this, create a diagram on a wiki page. In the drawio editor, choose ''File> Import From> Device''. You can then edit the imported diagram. 

{{Box Links-en
|Topic1=[https://diagrams.net/ draw.io Website]
|Topic2=[[mw:Extension:DrawioEditor|mediawiki.org/wiki/Extension:DrawioEditor]]
|Topic3=[[Reference:DrawioEditor]]
|Topic4=Anja Ebersbach, [https://bluespice.com/draw-io-for-mediawiki-and-bluespice/ draw.io für MediaWiki und BlueSpice], BlueSpice News & Know How, February 13 2020.
}}
{{translation}}
[[Category:Editing]]

Manual:Extension/VisualEditor

2025-06-20T13:46:57Z

Lhuyghe:

<bookshelf src="Book:User manual" />
{{DISPLAYTITLE:Edit pages}}

BlueSpice uses a slightly customized version of the MediaWiki extension [[mediawikiwiki:Help:VisualEditor/User_guide|VisualEditor]] as editing tool. This editor supports all common edit tasks that are useful in a wiki environment. You can refer to the official documentation for basic help. Here in the BlueSpice Helpdesk, we only give some hints and tips for using the editor.

==What is the visual editor? ==

<section begin="training" /><div class="training">[[File:Manual:ve-EN.png|alt=Numbered annotations for the menu items in the editor toolbar|center|thumb|850x850px|Visual Editor]]The visual editor is optimized for editing wiki pages. Important characteristics and functions are:

#'''Close page''' without saving
#*Opens a dialogue to exit the page without saving the last changes. The ''Cancel'' button closes the dialogue without leaving the page. The ''Okay'' button exits the page and the changes are discarded.
#'''Undo / redo changes'''
#'''Page structuring''' with headings
#[[Manual:Extension/VisualEditor#Text formatting|'''Text''' '''formatting''' options]]
#[[Manual:Extension/VisualEditor/Insert links|'''Link''' to other pages]]
#'''List''' formatting
#'''[[Manual:Extension/VisualEditor#Insert special content|Insert special content]]''' (images / files, tables, templates, formulas)
#Select '''special characters'''
#Insert '''[[Manual:Extension/ContentDroplets|content droplets]]'''
#[[Manual:Extension/AtMentions|'''Mention''' another user]]
#[[Manual:Extension/VisualEditor#Page options|Select '''page options''']]
#[[Manual:Extension/VisualEditor#Switching between edit modes|Switch between '''edit modes'''.]]
#'''Save''' the page
#*Opens the dialogue for saving the page. A summary of the changes can be entered here for the version history (optional).
#*''This is a minor edit'' checkbox: By activating the checkbox, the version is marked as ‘minor’. This applies, for example, to correcting typos, adjusting formatting or rearranging text. The changes do not represent an actual change to the content.
</div><section end="training" />

=== Text editing ===
[[File:Manual:Manual Extension VisualEditor 1750150012716.png|alt=Menu in text editing with the icon of the AI editing assistant|thumb|Menu in text editing]]
Typical text formatting options such as bold, italics, or text color are available as a context menu. When you highlight text, a menu with common formatting elements appears.
For example, you can apply a different text color or styling, or use the [[Manual:Extension/AIEditingAssistant|AI editing assistant]]. 
[[File:BlueSpice_3.1_-_Notable_Changes_-_Text_colors.png|center|thumb|Applying text color|alt=Text formatting inspector showing color choices]]

===Switching between edit modes===
When creating or editing a page, the page usually loads in visual editing mode. If you are familiar with the formatting language of MediaWiki ("[[Manual:Wikitext|Wikitext]]"), you can easily switch to source editing mode using the "Switch editor" menu item and edit your page content there:
[[File:Manual:editing.png|alt=open menu actions for switching between edit modes|center|250x250px|edit modes]]{{Textbox|boxtype=note|header=Note|text=Unsaved changes cannot be restored using the ‘Undo’ button after switching between visual and source text editing!|icon=yes}}

== Menu options ==
VisualEditor is optimized for editing web pages. That's why it has exactly the features that are often needed to create a wiki page. The consistent formatting of content supports the readability of your wiki content.

===Text formatting===
{| class="wikitable" style=""
|-
! colspan="2" style="" |'''Text formatting'''
|-
| style="" |Undo function
[[File:Manual:error.png|frameless|112x112px|alt=undo actions ]]
| style="" |Left arrow: Undo last action (greyed out: there is no last action yet)
Right arrow: Restore last action (greyed out: there's nothing to restore yet)
|-
| style="" |Format Paragraph
[[File:Manual:paragraph.png|frameless|162x162px|]]
| style="" | Here text can be defined as heading or specific paragraph type. If you have more than three headings on a page, a table of contents is automatically displayed at the top of the page.
''Note:'' If you work in a [[Manual:Extension/VisualEditor/Insert tables|table]], the options will change accordingly (content cell and header cell):[[File:Manual:content cell.png|left|frameless|183x183px|alternative-text=VisualEditor-paragraph2]] 
|-
| style="" |Style text
[[File:Manual:VE character formatting.png]]

| style="" |[[File:Manual:Manual Extension VisualEditor 1748247619625.png|alt=The following additional options are available in the text formatting menu|thumb|440x440px|Text formatting]] There are ways to emphasise individual words, especially by using bold or italics.
The following additional options are available in the text formatting menu:
* ''Bold''
* ''Italic''
* ''Superscript''
* ''Subscript''
* ''Computer code'': <code>the text will be displayed as computer code</code>
* ''Strikethrough''
* ''Underline''
* ''Big''
* ''Small''
* ''Language''
* ''Text color'': different text colors can be selected via an inspector menu.
* ''Center align'': Text can be selected and centered paragraph by paragraph.
* ''Indent'': Text can be indented once (note: multiple indentation is only possible via the source text).
* ''Remove'': remove all formatting from the selected text

If no text has been selected before clicking on the "''''' A'''''" button, the text will be formatted from the current position of the cursor.

(More Info at https://www.mediawiki.org/wiki/Help:VisualEditor/User_guide/en#Getting_started:_the_visual_editor's_toolbar)
|-
| style="" |Insert hyperlink
[[File:Manual:VE Insert hyperlink.png]] 
| style="" |It is possible to [[Manual:Extension/VisualEditor/Insert links|insert 3 types of links]]:

* ''Wiki link'': A link to a page in the same wiki. Here it is also possible to create an [[Manual:Extension/BlueSpiceInterWikiLinks|interwiki link]] to a page in another wiki.
* ''External link'': A link to external websites can be set here. If no text has been selected to be linked, the link is generated with a number: <code>[1]</code>
* ''Link to file'': A link to a file description page in the wiki can be set here. Please note that modern browsers do not open direct links to network paths. The Network path button is therefore rather obsolete.

To subsequently change the description of the hyperlink, click on the link to open the editing menu. In a table cell, you must first double-click on the cell and then click on the hyperlink again.
|-
| style="" |Structure
[[File:Manual:VE structure new.png]]

| style="" |Formats ordered and unordered lists, as well as ''[[Manual:Extension/SimpleTasks|task lists]]''.
If paragraph breaks or images need to be inserted within a bullet point, use <code>Shift+Enter</code> to avoid creating a new list item.

If you want to style numbered lists like 1, 1.1, 1.1.1, etc., you need to add some [[Numbering ordered lists|additional CSS instructions]] to the page ''MediaWiki:Common.css''.[[File:Manual:Manual Extension VisualEditor 1748248852329.png|alt=The following additional options are available in the structure menu|center|thumb|Structure menu]]
|}

===Insert special content===
{| class="wikitable" style=""
|-
! colspan="2" style="" |'''Insert special content'''
|-
| style="" |Insert menu (+)
[[File:Manual:Manual Extension VisualEditor 1748249104537.png|alt=Insert menu button|frameless]]
| style="" |Use the "insert" menu to insert various media (images, videos) and text formats:
|-
| style="" |Images and media
[[File:Manual:VE media.png]]
| style="" |Inserting [[Manual:Extension/VisualEditor/Insert images|pictures]], [[Manual:Extension/VisualEditor/Insert files|files]], direct links to Office documents and videos.

*File formats with a preview option: jpg/jpeg, png, gif, pdf
*File formats without preview option are always inserted as links (e.g., Microsoft Office formats)

([[mediawikiwiki:Help:VisualEditor/User_guide/en#Getting_Started:_The_VisualEditor-ToolbarHelp:VisualEditor/User_guide/en#Editing_images_and_other_media_files|Details on MediaWiki]])
|-
| style="" |Template
[[File:Manual:VE template.png]]
| style="" |Include a [[Manual:Templates|template]] in the page.
|-
| style="" |Table
[[File:Manual:VE table.png]]
| style="" |[[Manual:Extension/VisualEditor/Tables|Tables]] are an important tool for formatting tabular page content.
|-
| style="" |Comment
[[File:Manual:VE comment.png]]
| style="" |Comments are not visible to readers, but only in edit mode. A comment can be inserted anywhere on a page. It is text-based and cannot be formatted.
|-
| style="" |Your signature
[[File:Manual:VE your signature.png]]
| style="" |This option allows to add your wiki signature (User name and timestamp) at any location in the page.
|-
| style="" |Code block
[[File:Manual:VE code block.png|150x150px]]
| style="" |With code block various code examples can be entered, like e.g. in HTML syntax. The code is then displayed properly formatted and can be copied directly to the clipboard.<pre>
red text
</pre>
|-
| style="" |Exclude content in PDF
| style="" |Inserts tags around content in the source text, which are then not printed in the PDF. Only a short text can be entered here in visual editing mode. However, the start and end tags can be subsequently moved in the source text. This extends the area that is not exported to the PDF.
|-
| style="" |[[Manual:Extension/TabberNeue|Tabber]]
| style="" |Allows text sections to be displayed in tabs.
|-
| style="" |[[Manual:Extension/TabberNeue|Tabber (transclusion)]]
| style="" |Allows the integration of other wiki pages in tabs.
|-
| style="" |Chemical formula
[[File:Manual:VE chemical formula.png]]
| style="" |The formula rendering uses an external service via Wikimedia's REST API. 
|-
| style="" |Math formula
[[File:Manual:VE math formula.png|150x150px]]
| style="" |It opens an editor for entering a mathematical formula.

More information [[mediawikiwiki:Help:VisualEditor/User_guide/en#Editing_mathematical_formulae|on MediaWiki]]
|-
| style="" |References list
[[File:Manual:VE refernces list.png|150x150px]] 
| style="" |This menu item creates a <nowiki><references /></nowiki> tag at the location where it is inserted. The footnote references up to this point are then displayed at that location instead of the end of the page. Remaining footnotes in the page are still shown at the end of the page.
|-
| style="" |Gallery
[[File:Manual:VE gallery.png]]
| style="" |Allows to display a set of images as a gallery. A simple picture gallery can support many process flows. Formatting examples for the different settings can be found at

[[mediawikiwiki:Help:Images#Gallery_syntax|mediawiki.org/wiki/Help:Images#Gallery_syntax]]
|-
| style="" |Soft hyphen
| style="" |A long word can be hyphenated here. The hyphen is only inserted in view mode if the word needs to be wrapped at the end of the line.
|-
| style="" |Line break (br />)
| style="" |Explicit insertion of a line break.
|-
| style="" |Basic reference
| style="" |You can use this to create footnotes for scientific articles.
|-
| style="" |Re-use reference
| style="" |Enables an existing footnote to be linked multiple times to different sections of text.
|-
| style="" |Special Characters
[[File:Manual:VE special characters.png]]
| style="" | Collection of international special characters.
Opens a panel to select special characters that are not available on your keyboard.
To close the panel, click the menu item again.
|-
| style="" |[[Manual:Extension/AtMentions|Mentions]]
| style="" |Users can be mentioned directly on a wiki page. This can be done in combination with a [[Manual:Extension/SimpleTasks|task]].
|-
| style="" |[[Manual:Extension/ContentDroplets|Content Droplets]]
| style="" |Collection of the most important special content that can be used on a page.
|}

=== Page options ===

{| class="wikitable" style=""
|-
! colspan="2" style="" |'''Page options'''
|-
| style="" |Options menu[[File:Manual:tool.png|left|frameless|69x69px|alternative text=VisualEditor-options]]

| style="" |The options menu allows editing of all page settings. It is not
|-
| style="" |Options
[[File:Manual:VE options.png]]
| style="" |This button allows the page settings and page information to be updated simultaneously within a dialog box. To change any page options on the page, you need to be in '''visual editing mode'''.
|-
| style="" |Categories
[[File:Manual:VE categories.png]]
| style="" |Here, you assign the page to one or more [[Manual:Creating and using categories|categories]] while in edit mode. The page will then appear accordingly on all linked category pages.
|-
| style="" | Page Settings
[[File:Manual:VE page settings.png]]
| style="" |
* ''Page redirection:'' When the page is redirected, the content of the page is no longer displayed, but the target page is loaded directly.
* ''Show Table of Contents:'' By default, a table of contents is shown if a page has more than three headings. You can use this setting to always force or suppress the table of contents.
|-
| style="" |Advanced Settings
[[File:Manual:VE advanced settings.png]]
| style="" |
*''Let this page be indexed by search engines:'' Only applies to public search engines. The wiki's internal search is not affected.
*''Show a tab on this page to add a new section:'' Not supported in BlueSpice 4 Discovery skin.
*''Display title:'' Sets a title that is shown as page heading. It can be found by the search and is used in page lists created by [[SMW queries|Semantic MediaWiki]] inline queries.
*''Title visibility:'' This setting hides the entire title section of a page and is often applied on the main page or other portal pages of the wiki. If the title is not visible, the edit button is also not available. In this case, you can click on <code>...all actions > Edit</code> in the page tools.
|-
| style="" |Languages
[[File:Manual:languages.png]]
| style="" |Menu item to access interlanguage linksShows wiki pages on different wikis that are connected via Interlanguage links. Depending on the wiki's skin, the links are shown in a specific location. In the BlueSpice 4 Discovery skin, the interlanguage links are shown in the top menu.

[[mediawikiwiki:Help:Links#Interwiki_links|mediawiki.org/wiki/Help:Links#Interwiki_links]]
|-
| style="" |Templates used
[[File:Manual:VE templates used.png]]
| style="" |List the templates that are embedded on the page.
|-
| style="" |Syntax highlighting
| style="" |Displays the source code highlighted in colour using the [[Reference:CodeMirror|CodeMirror]] extension.
|-
| style="" |View as right-to-left
[[File:Manual:VE view as right-to-left.png]]
| style="" |Support for languages that are read from right to left. Clicking this button right-side formats the page text. Click again to set the text flush left.
|-
| style="" |Find and replace[[File:Manual:VE find and replace.png]]
| style="" | Words or characters can be searched and replaced directly on the page. The "Undo" button can be used to cancel the change.
|-
| style="" |Leave feedback about this software
| style="" |Opens a form for submitting feedback.
|-
| style="" |Keyboard shotcuts
| style="" |Link to the keyboard shortcuts
|-
| style="" |Toolbar search
| style="" |Opens a search field with which you can search in all Visual Editor options and tools.
|-
| style="" |Read the user guide
| style="" |Link to the helpdesk
|}

== Tips ==

=== Pasting content from your clipboard ===
[[File:Manual:error.png|thumb|112x112px|Undo|alt=Undo / redo actions in the editor toolbar]]
If you paste content from your clipboard (e.g., copied from MS Word or MS Excel), you usually also paste many unnecessary formatting tags from the original application. To avoid, this you should paste the content as plaintext.

If you already pasted text which resulted in undesirable formatting, you can use the undo function in VisualEditor to remove the content again if you have not yet saved the page or switched between visual and source editing mode.

To paste content as plain text instead, use the shortcut <code>Ctrl+Shift+v</code>.

=== Shortcuts ===
If you want to apply multiple formatting options at the same time, shortcuts are often the quickest way. For example, to show text in bold and italic, highlight the text and press <code>Ctrl+b</code> (for "'''bold'''") and <code>Ctrl+i</code> (for "''italics''"). Even a link can be quickly inserted by pressing <code>Ctrl+k</code>. Pressing <code>Ctrl+b</code> again will cancel the bold. Multiple formats can be removed after text selection with <code>Ctrl+m</code>.

All available keyboard shortcuts are marked accordingly in VisualEditor next to each menu item.[[File:Manual:editing_tools.png|alt=opened text formatting menu showing the available shortcuts|center|thumb|350x350px|Menu items with shortcuts]]
For a list of all available shortcuts, click on "Keyboard shortcuts" in the Visual Editor [[Manual:Extension/VisualEditor#Page options|page options menu]].

=== Troubleshooting: Visual editing is disabled ===
If you only have the source editing option in your editor toolbar, please contact an administrator of your wiki. The following settings must be checked in this case:

*Global settings via the [[Manual:Extension/BlueSpiceConfigManager|configuration manager]]
*[[Manual:Extension/BlueSpiceNamespaceManager|Namespace manager]] settings

{{translation}}
[[Category:Editing]]

Manual:Extension/Maps

2025-06-20T13:46:00Z

Lhuyghe:

==Content droplet==
The [[Manual:Extension/ContentDroplets|Content droplet]] ''Map'' is based on the ''Maps'' extension and inserts a simple map on a page. Alternatively, you can work in source edit mode to insert a more complex map view.

There are two input fields available in the Content droplet dialog box:

*'''Center of map:''' Sets the specified location to the map center.
*'''Focus:''' Marks a location with a blue marker. This marker can display additional text when clicked.
**Multiple locations are separated with semicolons.
**Each location can have a label appended with <code>~</code>.

It is enough to specify one of the two values to display the map. The Focus location is automatically displayed in the map center. If a center point is also specified, the focus location may no longer be visible in the map area and will only appear after manual zooming.

The map shown here is created as follows:<syntaxhighlight lang="text">
Focus: London;London LHR~Heathrow Airport
</syntaxhighlight>The locations “London” and “London LHR” are marked. When you click on the airport marker, the information "Heathrow Airport" opens (with <code>~</code> appended to the location marker).

{{Map|London;London LHR~Heathrow Airport|}}

===Examples===
{| class="wikitable" style="width: 100%;"
|+Map examples for the Content droplet "Map"
!Center of map
!Focus
! style="width:650px;" |Map display
|-
|London
| -
| style="width:650px;" |[[File:Maps example1.png|alt=Center of map is "London". Output is a street view featuring the river Thames with the City of Westminster in the north.|650x650px]]
|-
| -
|London
| style="width:650px;" |[[File:Maps example2.png|alt=Street view of London with the river Thames and a blue marker in the map center.|650x650px]]
|-
| -
|London~Inhabitants:8.866.180;Cambridge~Inhabitants:125.063;Oxford
| style="width:650px;" |[[File:Maps example3.png|alt=Map view with blue markers for the locations London, Cambridge and Oxford.|650x650px]]
|-
| -
|Regensburg, Bruderwöhrdstr.27~Bruderwöhrdstr.27<nowiki> </nowiki>93055 Regensburg
|[[File:Manual:extension Maps bsp4.png|alt=Street map of Regensburg with marker for Bruderwöhrdstr. 27, 93055 Regensburg|middle|650x650px]]
|}

==Embed a map in source editing mode (parser function)==
If you need a more flexible integration of a map, you can insert the parser function <code>#display_map</code> directly in source editing mode instead of using the Content droplet.

==Embed a map in source editing mode (parser function)==
If you need a more flexible integration of a map, you can insert the parser function <code>#display_map</code> directly in source editing mode instead of using the Content droplet. The documentation can be found at https://maps.extension.wiki/wiki/Displaying_Leaflet_maps.

===Example===
In the following map, an area of the city of Amsterdam is marked with multiple concentric circles:
<syntaxhighlight lang="text">
{{#display_map:circles=
Amsterdam:500;
Amsterdam:100~I am a title~And I am a description~green~0.7~10~blue~0.5
| zoom=14
}}
</syntaxhighlight>

Output:
{{#display_map:circles=
Amsterdam:500;
Amsterdam:100~I am a title~And I am a description~green~0.7~10~blue~0.5
| zoom=14
}}

==Documentation==
The full documentation is available at: https://maps.extension.wiki/wiki/Maps_for_MediaWiki
{{translation}}

Manual:Extension/Forms temp

2025-06-20T13:45:50Z

Lhuyghe:

The '''Forms''' extension allows formatting a wiki page or a user dialog as a form. It is also used in conjunction with the [[Reference:Workflows|Workflows]] extension where it provides input forms for workflow data.

==Introduction==
To create a checklist as a form, for example, the following steps are necessary:

# '''Create and save the checklist form''' via the ''Special:Form_editor'' special page. The form serves as a template for all checklists that are created with it.
# '''Create and save checklist instances''' via the special page ''Special:Create_form_instance''.

Optionally, the styling of the form can be adjusted.

As an example, we are creating a small checklist for an event where food-related hygiene information has to be tracked.
[[File:checklist-event-screenshot.png|alt=Event checklist example|center|thumb|550x550px|Event checklist example]]

==Create a checklist form==

# '''Define''' the main properties of the form:
## '''Open''' the ''Special:Form editor'' page.
## '''Enter''' a name for the new form, e.g. ''EventChecklistHygiene''. This name is used as a unique identifier for the database. Therefore, do not use any special characters (apart from the hyphen "-").
## '''Enter''' a title, e.g. Event Checklist. This is displayed as the display title instead of the form name if you activate the Display title checkbox. [[File:Manual:Checklist-form properties.png|alt=Form properties|center|thumb|750x750px|Form properties]]
# '''Add''' a form section:
##'''Select''' the ''Section label'' element under ''Form Elements > Other'' and, holding down the left mouse button, drag it into the interactive form editor field below.
## '''Click''' the section heading radio button. The editing dialog opens.
## '''Enter''' a field name. This is saved as a field ID in the database and should therefore not contain any special characters.
## '''Enter''' the title for the heading. This is used as the display title in the form.[[File:Manual:Checklist-form element-section label.png|alt=Create section label|center|thumb|750x750px|Create section label]]
# '''Create''' the form fields for the Event section. Here we add a text box as an example.
## '''Drag''' the ''Text'' element under the section heading while holding down the left mouse button.
## '''Click''' the text box radio button.
## '''Enter''' a name. This is used as the database ID for this field and should therefore not contain any special characters.
## '''Enter''' a label. This is displayed as the label for the text field.
## '''Add''' more form elements.
# Define which form fields should be used to generate the page name of the form instances created with this form. As an example, we define the page name for the checklists as subpages to the form name with the values from the event name and date fields (both fields must exist in the form: <code>EventChecklistHygiene/<nowiki>{{ech-eventname}}</nowiki>-<nowiki>{{ech-date}}</nowiki></code>
##'''Mark''' ''event name'' and ''day of event'' as required so that these values always exist.
## '''Switch''' to the ''Target'' view in the form properties.
## '''Select''' "Json in a wiki page" as the target type.
## '''Enter''' your title syntax: <code>EventChecklistHygiene/<nowiki>{{ech-eventname}}</nowiki>-<nowiki>{{ech-date}}</nowiki></code>[[File:Manual:form target.png|alt=Define the page name syntax for form instances|center|thumb|750x750px|Define the page name syntax for form instances]]
## '''Click''' Submit at the bottom of the page to save the form. The form is now stored in the main namespace as ''EventChecklistHygiene.form''. [[File:Manual:Checklist-view.png|alt=Saved form|center|thumb|650x650px|Saved form]] To continue editing the form, switch to the editing mode of the page (1).

==Create a checklist instance==
To use the form, create your first checklist.

# '''Open''' the page ''Special:Create_form_instance''.
# '''Choose''' the form ''EventChecklistHygiene''.
# '''Fill out''' the form fields.
# '''Click''' ''Submit''.[[File:Manual:Checklist-create instance.png|alt=Create a checklist instance|center|thumb|650x650px|Create a checklist instance]]

The checklist is now saved in the wiki and can be edited further.
#

==Send email==
The form can also send an Email after being saved:
[[File:Manual:image.png|alt=Email target|center|thumb|650x650px|Email target]]

*'''Target type:''' Email
*'''Recipient:''' Possible recipients must have been configured on the server for security reasons. Example:
<syntaxhighlight lang="text">
$wgFormsTargetEMailRecipients = [

'Marketing' => "marketing@example.com",

'Administration' => 'WikiSysop'

];
</syntaxhighlight>

* '''Subject:''' Existing form fields can be used as variables here. The value is taken from the form.

* '''Content:''' As in the subject, existing form fields can also be used as variables here. The value is taken from the form.

[[mediawikiwiki:Help:Magic_words#Localisation|Localization messages]] in combination with form fields can also be used as subject or email body:<syntaxhighlight lang="text">
{{int:Mailsubject| {{{name}}}|{{{surname}}} }}
</syntaxhighlight>

==Adjust the styling==

===Common.css===
To style individual elements in the form, go to the styling tab in the options dialog. There, you can enter a css class name. The styling is then defined on the ''MediaWiki:Common.css'' page (admin rights are required).

To style the section heading:

#'''Open''' the styling tab in the options menu of the Event heading field.
#'''Add''' a new CSS class and enter a selector name (''CSS Classes'' field), e.g. ''frm-sectionhd''.[[File:Manual:forms-css-class-en.png|alt=Add a css class|center|thumb|650x650px|Add a css class]]
#'''Paste''' the following style declarations into the ''MediaWiki:Common.css'' page, e.g.:<syntaxhighlight lang="css">
border-bottom: 1px solid #a6a6a7; background:#f1f3f9; padding:6px;margin:30px 0;
</syntaxhighlight>[[File:Manual:forms-css-class-view-en.png|alt=Section label with customized styling|center|thumb|650x650px|Section label with customized styling]]

If you do not have permission to view this page, you can enter style information directly for each element in the form via inline styling.

===Inline styling===
Without access to ''MediaWiki:Common.css'', the style information can be entered directly in the form. However, with many recurring style declarations this is not efficient in contrast to the definition of CSS classes in ''MediaWiki:Common.css''.

As an example, let's apply the previous section heading example directly as inline styling. To do this, open the options menu of the ''ech-event'' form element again. Enter the following statement in the ''Styling'' field and save the change:<syntaxhighlight lang="css">
border-bottom: 1px solid #a6a6a7; background:#f1f3f9; padding:6px;margin:30px 0;
</syntaxhighlight>
[[File:Manual:forms-css-inlinestyling-en.png|alt=Inline styling of a form element|center|thumb|650x650px|Inline styling of a form element]]

Manual:Extension/Forms temp

2025-06-20T13:45:24Z

Lhuyghe:

Manual:Extension/Forms

2025-06-20T13:45:09Z

Lhuyghe:

The '''Forms''' extension allows formatting a wiki page or a user dialog as a form. It is also used in conjunction with the [[Reference:Workflows|Workflows]] extension where it provides input forms for workflow data.

==Introduction==
To create a checklist as a form, for example, the following steps are necessary:

# '''Create and save the checklist form''' via the ''Special:Form_editor'' special page. The form serves as a template for all checklists that are created with it.
# '''Create and save checklist instances''' via the special page ''Special:Create_form_instance''.

Optionally, the styling of the form can be adjusted.

As an example, we are creating a small checklist for an event where food-related hygiene information has to be tracked.
[[File:checklist-event-screenshot.png|alt=Event checklist example|center|thumb|550x550px|Event checklist example]]

==Create a checklist form==

# '''Define''' the main properties of the form:
## '''Open''' the ''Special:Form editor'' page.
## '''Enter''' a name for the new form, e.g. ''EventChecklistHygiene''. This name is used as a unique identifier for the database. Therefore, do not use any special characters (apart from the hyphen "-").
## '''Enter''' a title, e.g. Event Checklist. This is displayed as the display title instead of the form name if you activate the Display title checkbox. [[File:Manual:Checklist-form properties.png|alt=Form properties|center|thumb|750x750px|Form properties]]
# '''Add''' a form section:
##'''Select''' the ''Section label'' element under ''Form Elements > Other'' and, holding down the left mouse button, drag it into the interactive form editor field below.
## '''Click''' the section heading radio button. The editing dialog opens.
## '''Enter''' a field name. This is saved as a field ID in the database and should therefore not contain any special characters.
## '''Enter''' the title for the heading. This is used as the display title in the form.[[File:Manual:Checklist-form element-section label.png|alt=Create section label|center|thumb|750x750px|Create section label]]
# '''Create''' the form fields for the Event section. Here we add a text box as an example.
## '''Drag''' the ''Text'' element under the section heading while holding down the left mouse button.
## '''Click''' the text box radio button.
## '''Enter''' a name. This is used as the database ID for this field and should therefore not contain any special characters.
## '''Enter''' a label. This is displayed as the label for the text field.
## '''Add''' more form elements.
# '''Click''' Submit at the bottom of the page to save the form. The form is now stored in the main namespace as ''EventChecklistHygiene.form''. [[File:Manual:Checklist-view.png|alt=Saved form|center|thumb|650x650px|Saved form]] To continue editing the form, switch to the editing mode of the page (1).

==Create a checklist instance==
To use the form, create your first checklist.

# '''Open''' the page ''Special:Edit_with_form''.
# '''Choose''' the form ''EventChecklistHygiene''.
# '''Fill out''' the form fields.
# '''Click''' ''Submit''.[[File:Manual:Checklist-create instance.png|alt=Create a checklist instance|center|thumb|650x650px|Create a checklist instance]]

The checklist is now saved in the wiki and can be edited further.
==Send email==
The form can also send an Email after being saved:
[[File:Manual:image.png|alt=Email target|center|thumb|650x650px|Email target]]

*'''Target type:''' Email
*'''Recipient:''' Possible recipients must have been configured on the server for security reasons. Example:
<syntaxhighlight lang="text">
$wgFormsTargetEMailRecipients = [

'Marketing' => "marketing@example.com",

'Administration' => 'WikiSysop'

];
</syntaxhighlight>

* '''Subject:''' Existing form fields can be used as variables here. The value is taken from the form.

* '''Content:''' As in the subject, existing form fields can also be used as variables here. The value is taken from the form.

[[mediawikiwiki:Help:Magic_words#Localisation|Localization messages]] in combination with form fields can also be used as subject or email body:<syntaxhighlight lang="text">
{{int:Mailsubject| {{{name}}}|{{{surname}}} }}
</syntaxhighlight>

==Adjust the styling==

===Common.css===
To style individual elements in the form, go to the styling tab in the options dialog. There, you can enter a css class name. The styling is then defined on the ''MediaWiki:Common.css'' page (admin rights are required).

To style the section heading:

#'''Open''' the styling tab in the options menu of the Event heading field.
#'''Add''' a new CSS class and enter a selector name (''CSS Classes'' field), e.g. ''frm-sectionhd''.[[File:Manual:forms-css-class-en.png|alt=Add a css class|center|thumb|650x650px|Add a css class]]
#'''Paste''' the following style declarations into the ''MediaWiki:Common.css'' page, e.g.:<syntaxhighlight lang="css">
border-bottom: 1px solid #a6a6a7; background:#f1f3f9; padding:6px;margin:30px 0;
</syntaxhighlight>[[File:Manual:forms-css-class-view-en.png|alt=Section label with customized styling|center|thumb|650x650px|Section label with customized styling]]

If you do not have permission to view this page, you can enter style information directly for each element in the form via inline styling.

===Inline styling===
Without access to ''MediaWiki:Common.css'', the style information can be entered directly in the form. However, with many recurring style declarations this is not efficient in contrast to the definition of CSS classes in ''MediaWiki:Common.css''.

As an example, let's apply the previous section heading example directly as inline styling. To do this, open the options menu of the ''ech-event'' form element again. Enter the following statement in the ''Styling'' field and save the change:<syntaxhighlight lang="css">
border-bottom: 1px solid #a6a6a7; background:#f1f3f9; padding:6px;margin:30px 0;
</syntaxhighlight>
[[File:Manual:forms-css-inlinestyling-en.png|alt=Inline styling of a form element|center|thumb|650x650px|Inline styling of a form element]]
{{translation}}

Manual:Extension/FlaggedRevs

2025-06-20T13:44:50Z

Lhuyghe:

{{BSVersion|bsvFrom=|bsvTo=4.2|bsvFeature=FlaggedRevs|text=Starting with BlueSoice 4.3, the extension ContentStabilization is used.}}<bookshelf src="Book:User manual" />
{{DISPLAYTITLE:Page approvals (Acceptance)}}

'''FlaggedRevs''' is a MediaWiki extension that activates an approval mechanism. New versions of a page are initially marked as drafts and remain so until a user with ''review'' rights approves the page.
==Activating the acceptance feature==
Activating the acceptance feature is done on the namespace level. A user with admin permissions activates the feature in ''Global actions > Management > Namespace manager'' for individual namespaces.
The dialog window opens after clicking the edit icon (wrench) in the ''Actions'' column. Select ''Approval'' and click ''Done''. 
[[File:Manual:approval-namespace.png|center|thumb|450x450px|Activate the Approval feature|link=Special:FilePath/Manual:approval-namespace.png]]

===Existing pages===
After activating ''Approvals'' for a namespace, all pages in the namespace are set into ''first draft'' mode.
[[File:Manual:flaggedrevs-firstdraft.png|alt=Frist draft|center|thumb|Frist draft]]

Each page in the namespace now displays the acceptance status in the title area.

The display of the acceptance status can be moved after the page content in the [[Manual:Extension/BlueSpiceConfigManager|Config manager]].

===New pages===
When a new page is created and first saved, it will automatically be visible to all users. Subsequent page edits will be collected in the draft version of the page. If a page is edited and saved multiple times while in draft mode, each edit gets logged in the version history: [[File:Manual:flaggedrevs-revisions.png|center|650x650px|thumb|Draft revisions|link=Special:FilePath/Manual:flaggedrevs-revisions.png]]

The revisions in draft status have a dotted border and are highlighted in orange. In addition, they are marked as ''pending review''. These revisions can be compared before the pending changes of the page are accepted.

==Accepting a page==
Users with ''review'' rights can accept a draft page any time they save a page (''Accept this unreviewed page''): 
[[File:Manual:flaggedrevs-activated-firstsave.png|link=https://en.wiki.bluespice.com/wiki/File:Manual:flaggedrevs-activated-firstsave.png|center|650x650px|thumb|Accepting pending changes]]

If the page is not accepted at this point, it can be accepted independently from the editing process.

A user with ''review'' rights can accept the page quickly with the review feature in the title section of the page. The draft message will display an arrow which includes the ''accept'' function:
 
[[File:Manual:flaggedrevs-acceptdraft.png|center|277x277px|thumb|Accepting a draft from the title section|link=Special:FilePath/Manual:flaggedrevs-acceptdraft.png]]

When accepting the page, the reviewer can leave a comment. This comment will then be shown in the version history of the page.

The page status now shows the page version as accepted.
[[File:Manual:flagged-revs-accepted.png|link=https://bs4-en.wiki.bluespice.com/wiki/File:Manual:flagged-revs-accepted.png|alt=Accepted page|center|thumb|300x300px|Accepted page]]

==Setting read permissions for drafts==
By default, all users can see the drafts of a page, even readers.

To hide drafts from readers, the group ''user'' has to be removed from the configuration. An administrator deletes the group user form "Show unstable pages for the following groups" in ''Global actions > Management > Config manager'':
 
[[File:Manual:flaggedrevs-config.png|center|650x650px|link=Special:FilePath/Manual:flaggedrevs-config.png]]
 {{Messagebox|boxtype=warning|Note text=If the group ''user'' is removed from the ''BlueSpiceFlaggedRevs'' configuration, users in this group will not be able to see draft versions when they are added as reviewers in a review process.}}
When the group user is removed, only ''sysop'' and ''reviewer'' users can access drafts. If you want other groups, for example ''editor'', to see draft versions, you need to add them to the configuration and save it:
 
The two checkboxes ''Automatically set the page to stable...'' (checkbox is available until version 3.1.) and ''Automatically delete the workflow..''. determine what happens at the end of a workflow, if there is an active [[Manual:Extension/Workflows|Review]] for a page. A page can be set to accepted status by a workflow and the workflow can be deleted after the page is marked as stable.
{{Messagebox|boxtype=note|Note text=If no user groups are specified in the configuration field, not even reviewers and sysops users will see a visual status indication of a page. They will have access to drafts through the revision history of a page instead.}}
Anyone with edit permissions will receive a notification that there are pending changes for the page when they access the page in edit mode:
 
[[File:Manual:flaggedrevs-editnotification.png|center|550x550px|thumb|Pending changes notification|link=Special:FilePath/Manual:flaggedrevs-editnotification.png]]

== Changes to embedded templates and files==
If a page uses templates or contains other files such as images and embedded PDFs and these files have been modified since the page was approved, those changes must also be approved. The wiki can be set up in two different ways to achieve this approval:

# '''The embedded resource is located in a namespace without approval feature''' If the embedded resource is in a namespace without its own approval function, the resource version at the time of the page approval is displayed. The draft version of the page shows the most recent version of the embedded resource. To approve the resource change, the page istself must be approved again. The approval has to be done on all pages that have this resource embedded. [[Manual:Extension/FlaggedRevs/Server script|Information about automatic mass approval via server script.]]
# '''The embedded resource is located in a namespace with approval feature:''' The pages that include the changed resource do not give any indication that the resource has been changed. Which version of the included resource is displayed depends on the configuration of the wiki:

{| class="wikitable" style="width:100%;" data-ve-attributes="{"style":"width:100%;"}"
! style="width:220px;" |Setting
!Description
|-
| style="width:220px;" |Stable versions
FR_INCLUDES_STABLE
(default)
|Always shows the approved (stable) version of a resource, even if it was approved after the page that includes the resource was approved (this works only if the resource is located in a namespace with active approval feature).
|-
| style="width:220px;" | Current versions
FR_INCLUDES_CURRENT
| Always shows the latest version of the included resource (as if approvals was not activated in the resource namespace).
|}

=== Ignoring changes to embedded resources ===
If the ''Current versions'' option is selected under "Include handling" in the config manager and the resource namespaces '''do not''' have approvals activated, changes to these resources are ignored on the approved pages. This should be communicated to wiki users and quality managers accordingly.
[[File:FlaggedRevs ignore resources.png|alt=Ignore changes to embedded resources|center|thumb|550x550px|Ignore changes to embedded resources]]

==Effects on Semantic MediaWiki properties==
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:
{| class="wikitable" style="width:950px;"
! 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
! 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
|- style="box-sizing: inherit;"
| style="box-sizing:inherit;padding:0.2em 0.4em;border:1px solid rgb(162, 169, 177);" |First draft
| style="box-sizing:inherit;padding:0.2em 0.4em;border:1px solid rgb(162, 169, 177);" |Current values
|- style="box-sizing: inherit;"
| style="box-sizing:inherit;padding:0.2em 0.4em;border:1px solid rgb(162, 169, 177);" |Approved
| style="box-sizing:inherit;padding:0.2em 0.4em;border:1px solid rgb(162, 169, 177);" |Values of the approved (stable) version
|- style="box-sizing: inherit;"
| style="box-sizing:inherit;padding:0.2em 0.4em;border:1px solid rgb(162, 169, 177);" |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)
|- 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>
| style="box-sizing:inherit;padding:0.2em 0.4em;border:1px solid rgb(162, 169, 177);" |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 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:Manual:qm-overview.png|center|thumb|650x650px|Special page Quality management overview|link=Special:FilePath/Manual:qm-overview.png]]
{{Box Links-en
|Topic1=[[Manual:Quality_management|Quality management tools]]
|Topic2=[[Reference:FlaggedRevs]]
|Topic3=[[Reference:BlueSpiceFlaggedRevsConnector]]|Topic4=[[Manual:Semantic MediaWiki]]}}
{{translation}}
__FORCETOC__

<references />

Manual:Extension/EmbedVideo (fork)

2025-06-20T13:44:30Z

Lhuyghe:

{{DISPLAYTITLE:Embed videos}}
{{BSVersion|bsvFrom=4.4|bsvFeature=EmbedVideo_(fork)|info=It replaces the extension [[Manual:Extension/EmbedVideo|EmbedVideo]]}}
{{Textbox|boxtype=important|header=|icon=no|text=By default, video and audio formats are not configured as allowed file formats.
An administrator must first add the appropriate file formats in the [[Manual:Extension/BlueSpiceConfigManager#System|Config manager]] before users can upload these files.|bgcolor=}}
==Embedding external videos==
===Via Content droplet===
Videos hosted on supported external services can be added via the [[Manual:Extension/ContentDroplets|Content Droplet]] ''Video''.

After choosing the ''Video'' Content Droplet, you can provide the video name, for example of a YouTube video:
[[File:EmbedVideo (fork) options.png|center|thumb|327x327px|Options of the "Video" Content Droplet|alt=Video link to a YouTube video as a thumbnail image with a description.]]
By default, placeholders are displayed for embedded videos until users provide their consent to load the video from the video service. This consent requirement can be disabled [https://www.mediawiki.org/w/index.php?title=Extension:EmbedVideo_(fork)#Configuration via server configuration].[[File:EmbedVideo (fork)-Zustimmung.png|alternativetext=Gray background with video service consent button|center|thumb|Video placeholder]]

===In source-editing mode===
{{Messagebox|boxtype=note|Note text=These instructions are taken and adapted from the [https://www.mediawiki.org/wiki/Extension:EmbedVideo Mediawiki help page] for EmbedVideo.}}

====Syntax====
Individual videos are embedded with the <code>#ev</code> tag. The order of the parameters is fixed when the parameter itself is not explicitely provided. Example:
<syntaxhighlight lang="text">
{{#ev:service|id|dimensions|alignment|description|container|urlargs|autoresize|valignment}}
</syntaxhighlight>Placeholders for unused arguments between two arguments have to remain empty and cannot be removed. Example:
<syntaxhighlight lang="text">
{{#ev:service|id|||description}}
</syntaxhighlight>The shortest option to embed a video is by specifying the service name and the video ID. Example:
<syntaxhighlight lang="text">
{{#ev:youtube|MLIE2642neg}}
</syntaxhighlight>Example with video description. You can include a line break with the <code><nowiki> </nowiki></code> tag:
<syntaxhighlight lang="text">
{{#ev:youtube|MLIE2642neg|||ISS - Life on the space station 1:04:27}}
</syntaxhighlight>
It is simpler to provide the paramter itself. Then the order of the parameters is not relevant. Examplel:<syntaxhighlight lang="text">
{{#ev:youtube|id=MLIE2642neg|description=ISS - Leben auf der Weltraumstation}}
</syntaxhighlight>

=== Displaying a preview image ===
If you embed the video in source editing mode, you can also display a preview image by using the <code>cover</code> parameter. Example:<syntaxhighlight lang="text">
{{#ev:youtube|id=MLIE2642neg|description=How to add tasks to a page|cover=Aufgaben.jpg}}
</syntaxhighlight>
[[File:Manual:embedvideo cover.png|alt=Pen and piece of paper with a fictitious English ‘to-do’ list for the daily routine|centre|thumbnail|300x300px|Video cover|link=https://en.wiki.bluespice.com/wiki/File:Manual:embedvideo_cover.png]]

====Attributes for parser tag #ev====
{| class="contenttable-blue" style="width:100%;" data-sourcepos="123:1-133:266" dir="auto"
|+
! data-sourcepos="123:2-123:46" |attribute
! data-sourcepos="123:48-123:57" |required
! data-sourcepos="123:59-123:67" |default
! data-sourcepos="123:69-123:262" |description
|- data-sourcepos="125:1-125:263"
| data-sourcepos="125:2-125:46" |<code>service="(see supported services below)"</code>
| data-sourcepos="125:48-125:57" |yes
| data-sourcepos="125:59-125:67" |
| data-sourcepos="125:69-125:262" |The video service that is called when the player is created.
|- data-sourcepos="126:1-126:264"
| data-sourcepos="126:2-126:47" |<code><nowiki>id="[id|url]"</nowiki></code>
| data-sourcepos="126:49-126:58" |yes
| data-sourcepos="126:60-126:68" |
| data-sourcepos="126:70-126:263" |The video ID or full URL of the external video.
|- data-sourcepos="127:1-127:596"
| data-sourcepos="127:2-127:48" | <code><nowiki>dimensions="[width|widthxheight|xwidth]"</nowiki></code>
| data-sourcepos="127:50-127:59" |no
| data-sourcepos="127:61-127:69" |640
| data-sourcepos="127:71-127:595" |Dimensions in pixelsto size the container for the player. The default format is width x height. It is possible to omit one of the dimensions. The <code>x</code> always has to be included before the height.
Examples: <code>480</code>, <code>480x320</code>, <code>x320</code>. If the height is not specified, it is calculated using the width and the default ratio of the video service.

Some video services such as ''Gfycat'' don't have a standard height. Therefore, the height setting should be included for each video. With <code>$wgEmbedVideoDefaultWidth</code> the default width can be overwritten in the file <code>LocalSettings.php</code> on the server.
|- data-sourcepos="128:1-128:266"
| data-sourcepos="128:2-128:49" |<code><nowiki>alignment="[left|center|right|inline]"</nowiki></code>
| data-sourcepos="128:51-128:60" |no
| data-sourcepos="128:62-128:70" |none
| data-sourcepos="128:72-128:265" |The video can be placed left, center, right, or inline. Inline allows to add multiple videos in one row. In mobile view, the videos are automatically aligned vertically.
|- data-sourcepos="129:1-129:263"
| data-sourcepos="129:2-129:46" |<code>description="[wiki text]"</code>
| data-sourcepos="129:48-129:57" |no
| data-sourcepos="129:59-129:67" |none
| data-sourcepos="129:69-129:262" |Shows a description below the player container.
|- data-sourcepos="130:1-130:263"
| data-sourcepos="130:2-130:46" |<code>container="[frame]"</code>
| data-sourcepos="130:48-130:57" |no
| data-sourcepos="130:59-130:67" |none
| data-sourcepos="130:69-130:262" |Determines the container type for the player.
<code>frame</code>: Places the video player in a Mediawiki preview box.
|- data-sourcepos="131:1-131:263"
| data-sourcepos="131:2-131:46" |<code>urlargs="modestbranding=1&version=3"</code>
| data-sourcepos="131:48-131:57" |no
| data-sourcepos="131:59-131:67" |none
| data-sourcepos="131:69-131:262" |Allows adding additional URL-arguments to the embedded url. This is useful for settings that are only offered by an individual video service.
|- data-sourcepos="132:1-132:263"
| data-sourcepos="132:2-132:46" |<code>autoresize="false"</code>
| data-sourcepos="132:48-132:57" |no
| data-sourcepos="132:59-132:67" |true
| data-sourcepos="132:69-132:262" |Automatically adjusts the video size if the video would extend beyond the size of the container.
|- data-sourcepos="133:1-133:266"
| data-sourcepos="133:2-133:49" |<code><nowiki>valignment="[top|middle|bottom|baseline]"</nowiki></code>
| data-sourcepos="133:51-133:60" |no
| data-sourcepos="133:62-133:70" |none
| data-sourcepos="133:72-133:265" |Aligns the vertical placement of the video either to the top, middle, bottom, or baseline of the parent element. Using this parameter forces the alignment parameter to be inline.
|-
|<code><nowiki>width</nowiki></code>
|
|
|Width of the video (e.g. <code>300</code>). The height is calculated automatically
|-
|<code><nowiki>height</nowiki></code>
|
|
|Height of the video (e.g. <code>200</code>). The width is calculated automatically.
|-
|<code><nowiki>poster</nowiki></code> / <code><nowiki>cover</nowiki></code>
|
|
|Only considered if consent is required to load the video($wgEmbedVideoRequireConsent=true).
|-
|<code><nowiki>title</nowiki></code>
|
|
| Only considered if consent is required to load the video($wgEmbedVideoRequireConsent=true).
|}

=== No longer supported parameters ===

If you have already integrated videos into your wiki using the previous extension ''EmbedVideo'', it is possible that they are no longer displayed. Example of a previous integration:<syntaxhighlight lang="text">
{{#evt:
service=youtube
|id=fX8ml-XPMdY
|dimensions=280
|alignment=right
|description=Webinar: BlueSpice 4 (12:43)
}}
</syntaxhighlight>The parser function <code>#evt</code> and the parameter name <code>service</code> are no longer supported. Replace the above syntax with the corresponding content droplet or change the syntax in the source code to the following:<syntaxhighlight lang="text">
{{#ev:
youtube
|id=fX8ml-XPMdY
|dimensions=280
|alignment=right
|description=Webinar: BlueSpice 4 (12:43)
}}
</syntaxhighlight>
==Embedding local videos==

===Media dialog===
[[Manual:Extension/VisualEditor/Insert images|Like images]], videos can be inserted directly on a page via the media dialog. The wiki recognizes the file extension and automatically generates the necessary HTML player.

=== BlueSpicePlayer and EmbedVideo===
Videos that have been uploaded to the Wiki can also be embedded in source editing mode. This can also be done using the extension [[Manual:Extension/BlueSpicePlayer|BlueSpicePlayer]]. BlueSpicePlayer has no functions to embed external videos, however.

The two extensions have the following differences when embedding local video files:

{| class="contenttable-blue" style="width:100%;"
|+
! style="width:20%;" | Syntax/Parameter
! style="width:39%;" |EmbedVideo
!BlueSpicePlayer
|-
| style="width:20%;" |Syntax
| style="width:39%;" |corresponds to the syntax of embedding image files:
<code><nowiki>[[File:samplename.mp4]]</nowiki></code>
|<code><nowiki><bs:showtime>samplename.mp4</bs:showtime></nowiki></code>
|-
| style="width:20%;" |Size
| style="width:39%;" |Only the width can be defined. The video fills the entire width of the player container:[[File:300px-video-size-embedvideo-600.PNG|alt=|center]]<code><nowiki>[[File:Manual:300px-video-size-showtime-600.PNG]]</nowiki></code>
 
|Width and height can be defined separately. If the width of the video is smaller than the video container, the canvas is filled in black.
<code><nowiki><bs:showtime width="600"></nowiki></code>..[[File:Manual:300px-video-size-showtime-600.PNG|alt=BlueSpicePlayer with 600px width|center|thumb|BlueSpicePlayer with 600px width]].
|-
| style="width:20%;" |Loop
| style="width:39%;" | - 
|<code><nowiki><bs:showtime repeat="yes"</code></nowiki>
|-
|Autostart
| -
|<code><nowiki><bs:showtime autostart="yes"</code></nowiki>
|-
|Star/End
|<code><nowiki>[[File:samplename.mp4|start=2|end=6]]</nowiki></code>
Time can be added as: ''ss, mm:ss, hh:mm:ss''
| -
|-
| style="width:20%;" |HTML-Output
| style="width:39%;" |embedded as <video> tag
|embedded through nested <nowiki><div> tags</nowiki>
|-
| style="width:20%;" |Adjusts to mobile display
| style="width:39%;" |yes
| no
|-
| colspan="3" class="col-blue-light-bg" | Player controls
|-
| style="width:20%;" |play button
| style="width:39%;" |yes
|yes
|-
| style="width:20%;" |progress bar
| style="width:39%;" |yes
|yes
|-
| style="width:20%;" |volume adjustment
| style="width:39%;" |yes
|yes
|-
| style="width:20%;" |fullscreen mode
| style="width:39%;" |yes
|yes
|-
| style="width:20%;" |picture-in-picture
| style="width:39%;" |yes
|yes
|-
| style="width:20%;" |download
| style="width:39%;" |yes
|no
|-
| style="width:20%;" |speed adjustment
| style="width:39%;" |no
|yes
|}
==Supported video services==
The following video services are supported. In parentheses, you find the service names that are used with the tag <code>#ev</code>:

Archive.org Videos (archiveorg), Bilibili (bilibli), KakaoTV (kakaotv), NaverTIV (navertv), Niconico (niconico), SoundCloud (soundcloud), Spotify Album (spotifyalbum), Spotify Artist (spotifyartist), Spotify Song (spotifytrack), Twitch (twitch), Vimeo (vimeo), YouTube (youtube), YouTube Playlist (youtubeplaylist), YouTube Video List (youtubevideolist).

New services can be requested via[https://github.com/StarCitizenWiki/mediawiki-extensions-EmbedVideo/issues/new?assignees=&labels=enhancement&template=embed-service-request.md&title=Embed+Service+Request%3A+Service+Name GitHub] from the developer.

{{Box Links-en
|Topic1=[https://www.mediawiki.org/wiki/Extension:EmbedVideo Mediawiki help page for the extension EmbedVideo]
|Topic2=[[Manual:Extension/Showtime|Help page for the extension BlueSpicePlayer - only for video files that have been uploaded to the wiki]]
|Topic3=[[Template:Embed video|Template to embed video using the Visual Editor toolbar]]}}

 
{{translation}}

Manual:Extension/BlueSpiceSocialMicroBlog

2025-06-20T13:43:33Z

Lhuyghe:

<bookshelf src="Book:User manual" />
{{translation}}

Manual:Extension/BlueSpicePrivacy

2025-06-20T13:40:30Z

Lhuyghe:

<bookshelf src="Book:User manual" />
{{DISPLAYTITLE:Privacy center}}

'''BlueSpicePrivacy''' is an extension that enables users to control the way their data is collected and used by the wiki. Users interact with this extension through the Privacy center page, which is accessible by clicking ''Privacy center'' in the user menu.

==Accepting the terms of use==
When a user wants to log into the wiki for the first time, the terms and conditions and the privacy policy must be accepted during the login process.

[[File:privacy confirmation links.png|alt="Privacy policy" and "Terms of service" checkboxes on the login page|center|thumb|250x250px|Privacy consent]]

==Cookie consent==

Users are presented with a prompt to accept the cookies that the wiki collects. This prompt appears when a user visits the wiki for the first time or after deleting the browser cookies.
[[File:Manual:PrivacyCookieConsent1a.png|alt=|center|thumb|324x324px|Cookie consent]]

Here, users have the option to accept all cookies or to manage each group of cookies separately. This is done by opening''Cookie consent settings'' and then using the toggle-switches in the prompt. There are different types of cookies, based on the function they perform:

*'''Necessary cookies:''' Cookies that are needed for the user to be able to use the wiki (cookies for keeping session information, user ID data, and so on).
*'''Convenience cookies:''' Cookies that provide a more comfortable wiki experience (saving the state of components of the interface, some user preferences, and more)
*'''Matomo''' (visible only if the [[Reference:BlueSpicePrivacy|necessary plugin]] is installed and activated): Cookies that are used for site analytics.

By default, accepting at least the necessary cookies is mandatory before using the wiki for the first time.

Cookie settings can be changed afterwards at any point by clicking on "Change cookie consent" in the wiki footer links or on the page <code>Special:PrivacyCenter</code>.

==Privacy Center==

The privacy center is the hub for a user's privacy settings. It is located in the profile menu (by clicking on user image in the top right corner) or by navigating directly to the page<code>Special:PrivacyCenter</code>.

[[File:Manual:Extension BlueSpicePrivacy 1743085291590.png|center|thumb|Privacy center]]

This special page consists of a number of "modules". Each module performs a privacy-related function.
===Anonymization===
In this section, users can anonymize their account on the wiki. This means that users can change their username on the wiki. The new username appears wherever the username is used, including comments, page histories and logs. All traces of previous user information including profile information and profile data is removed or renamed.

To anonymize their account, users pick the new username (a random anonymized username is offered by default) and click "Anonymize my account". After confirmation, the process of anonymization starts, and the user receives a notification upon completion.{{Messagebox|boxtype=important|Note text=Changes made in the Privacy center, for example anonymization, can take up to 24 hours to be effective (until the cache expires).}}
===Delete your account===
You can delete all traces of your account from the wiki by clicking the "Delete your account" button. After confirmation, the user account is deleted. In case there is an error in the process, users will be notified of the failed deletion process.

By deleting their account, users will remove all references to their user account anywhere on the wiki. All of the user's contributions are then attributed to "Deleted user", which will appear instead of the original username. The wiki is usually set to require an administrator to delete a user account upon request. The delete-button will show "Request account deletion" accordingly.

=== Transparency / Export your data ===
To view the data the wiki has stored about you in its logs and settings, you can click on the button ''Show all data''. This opens a dialog containing all of the user's data. [[File:Manual:transparency.png|alt=|center|thumb|462x462px|Viewing data wiki collected on the user]]

Users can print out this same information in html or csv formats. The following information is collected:

* '''Personal data:''' Profile image, username, real name, registered on, blocekd, email address, number of edits, experience level, groups, former groups, permissons
* '''Mentions in content:''' signatures, blog entries, comments, links to the user page
* '''Working data:''' search terms, page assignments, pages read, read confirmations, reminders, page approvals and other data that was logged by extensions
* '''Action data:''' administrative actions, changes of settings, file uploads, page actions (move, delete,....)

To export the data, the user selects the groups to export and the export format (HTML or CSV). After clicking ''Export data'', the file is saved to the user's local download location.

===Privacy policy consent===
In this section, users can change their consent to the wiki's privacy policy. Further options may appear based on a specific wiki configuration. Users can also change their cookies consent (as described above).

==Requesting actions==
[[File:Manual:PrivacyNoRequest1.png|alt=|center|thumb|484x484px|active requests]]
The wiki can be configured so that users are not allowed to directly execute certain privacy-related actions. They need to request that operation first.

Requests can be enabled for the wiki by setting <code>$bsgPrivacyEnableRequests = true;</code> in <code>LocalSettings.php</code>

Once enabled, users will be presented with a request form in the affected sections. In this form, users can click ''Request anonymization'' and ''Request account deletion'' respectively. For account deletion, users can enter an optional comment explaining the reason for the request.

All submitted requests are sent to wiki admins for review and can perform or reject the corresponding action via the [[Manual:Extension/BlueSpicePrivacy/Administration|data protection administration]].

After submitting the request, a user sees a R''equest pending'' notice in the Privacy center. If the request is denied, the user is notified with a comment from the wiki administrator. If the user's request is approved, the user also receives a notification.

{{translation}}
[[Category:Personalization]]

Manual:Extension/BlueSpiceInsertFile

2025-06-20T13:39:25Z

Lhuyghe: Changed redirect target from Manual:Extension/VisualEditor/Files to Manual:Extension/VisualEditor/Insert files

#REDIRECT [[Manual:Extension/VisualEditor/Insert_files]]

__STATICREDIRECT__

Manual:Extension/InputBox

2025-06-20T13:31:50Z

Lhuyghe:

The '''InputBox''' extension allows to automatically create a new page via an input field with a specific page name and - optionally - in a specific namespace.

== Creating meeting minutes from an inputbox ==
 
[[File:inputbox-en.png|alt=Inputbox to create a wiki page|center|thumb|450x450px|Inputbox to create a wiki page]]
 A typical example of this is creating meeting minutes that follow a consistent content structure. The following code can be added to the source code of a page:<syntaxhighlight lang="text">
<inputbox>
type=create
default={{CURRENTYEAR}}-{{CURRENTMONTH}}-{{CURRENTDAY2}}
prefix=Meeting:IT/Jour fixe/
preload=Meeting:Standard minutes
buttonlabel=New minutes
break=no
width=30
useve=true
arialabel=New minutes
</inputbox>
</syntaxhighlight>

'''Description of the settings:'''
{| class="wikitable" style=""
|+
!
!Wert
!
|-
|type
|create
|Creates a new page
|-
|default
|
|Suggestion for a name for the new page; here in the example: current edate
|-
|prefix
|''Seitenpfad''
|Path to a namespace or subpage.
|-
|preload
|''Pfad zur Vorlage''
|Loads the default text for the new page from a template, if you are not using a template, this line can be deleted. If the template is not found, a blank page is created.
|-
|buttonlabel
|''Text''
|Text that is shown on the button.
|-
|break
|no
|Places the button behind the text field rather than below.
|-
|width
|30
|Size of the inputbox in characters
|-
|useve
|true
|Opens the new page directly in visual editing mode
|}

===Show latest minutes===
If you want to display links to the last 5 meeting minutes by creation date directly below the input box, you can add the following query in the source code below the input box, specifying the path to the logs in the square brackets in the #ask query (i.e. the prefix-path from the inputbox followed by a *:<syntaxhighlight lang="text">
List of minutes:
<div>
{{#ask:[[~IT/Jour Fixe/*]]
|limit=5
|sort=creation date
|order=desc
|format=ul
|default=There are currently no minutes
|searchlabel= → More IT-Jour Fixe minutes
}}
</div>
</syntaxhighlight>'''Beschreibung der Einstellungen zur Anzeige der letzten Protokolle:'''
{| class="wikitable" style=""
|+
!Name
!Wert
!
|-
|#ask [[ ]]
|create
|The path to the minutes is pecified here. Alternatively, the category if the logs are assigned to a category.
|-
|limit
|Zahl
|Number of results. Below, a more... link will be shown
|-
|sort
|creation date
|Sorting of resulst by creation date
|-
|order
|desc
|Ordered descending
|-
|format
|ul
|Results format is an unordered list
|-
|default
|Text
|Text to show if no results exist
|-
|search label
|Text
|Label for the link to additional results (is shown only if there are more results than the defined ''limit]''
|}{{Box Links-en|Topic1=[https://www.mediawiki.org/wiki/Extension:InputBox/de www.mediawiki.org/wiki/Extension:InputBox]}}
{{translation}}

Manual:Extension/FlexiSkin

2025-06-20T13:30:16Z

Lhuyghe:

<bookshelf src="Book:Admin manual" />
{{DISPLAYTITLE:Customizing the user interface (FlexiSkin)}}

== Access ==

You can access the special page (''Special:FlexiSkin)'' for customizing the skin from the ''Global actions'' menu:

''{{Icon|bi bi-gear-fill|||middle}} (Global actions) > Management > Skin''

The page allows you to customize the logo, favicon, colors and font settings of the wiki. To edit the page, you need ''admin-''rights in the wiki.

[[File:FlexiSkin link.png|alt=Link for customizing the skin|center|thumb|500x500px|Link for customizing the skin]]

 

{{Messagebox|boxtype=important|icon=|Note text=If you don't see the changes in the wiki after saving your settings, you need to clear your browser cache (<code>Ctrl</code>+ <code>F5</code>).|bgcolor=}}

==Logo and Favicon ==

===Logo===
'''To upload your logo:'''

#'''Click''' ''Select a file'' to choose a file from your file explorer '''or drag the file''' into the dotted area of the Logo upload area.[[File:Manual:logo-upload-dialog.png|alt=Upload a logo|center|thumb|140x140px|Upload a logo]]
#'''Click''' the ''Preview'' button on the page and check the placement of the logo.
#'''Click''' ''Save & activate''. The logo is now visible for all users.

To use '''a different logo''', click the "x" symbol in the upload area of the logo and repeat the steps above.

===Favicon===
The favicon is the image that is shown in the browser tabs. Follow the [[Manual:Extension/FlexiSkin#Logo|steps for uploading a logo]], just use the favicon upload area instead.

==Layout colors==
Here you can adjust the colors of the individual layout areas.
[[File:Manual:flexi-main-annotiert-EN.png|alt=Flexiskin layout colors|center|thumb|650x650px|Flexiskin layout colors]]

*'''Header color (3):''' Color settings for the header bar. These colors also apply to the mega menus.[[File:Manual:flexi-headers-EN.png|alt=Mega menu|center|thumb|650x650px|Mega menu]]
*'''Sidebar colors (4):''' Color settings for the main navigation and the page tools.
*'''Footer colors (5):''' Color settings for the footer. 
The following options to enter a color value are available:

*'''Standard color palette:''' A standard color can be selected by clicking on a color preview.[[File:Manual:fs-colorpicker.png|alt=Color picker|center|thumb|192x192px|Color picker]]
*'''Pencil symbol:''' Click on the pencil symbol to select a color from the color mixer.
*'''Manually entering a value:''' To provide a custom value (e.g., your for your CI colors), enter the hex-value for the color.
If you delete a color and FlexiSkin is saved with one or more empty color values, the standard colors of the Discovery skin are saved as values instead.
*

{| class="wikitable" style=""
|+Standardfarben des "Discovery"-Skin
!
!Background
!Foreground
!Highlight
|-
|Header
|#ffffff
|#252525
|#3e5389
|-
|Sidebar
|#f1f3f9
|#252525
|#3e5389
|-
|Footer
|#d3d3d3
| #454545
| -
|}

== Content==
These settings apply to all styles of the content area of a wiki page: 

=== Colors===
Here you can adjust the background, font and link colors. Broken links in the wiki are shown in red by default so that they can be easily identified. You should carefully consider whether you want to deviate from this convention. If you want to color visited links differently than standard links, you can insert the following setting in the Free CSS area:<syntaxhighlight lang="css">
#mw-content-text a:visited,[class^="mw-content-"] a:visited {color: #951b81;}
</syntaxhighlight>

===Font ===
The font settings only apply to the text in the content area. The text in other areas such as B. in the navigation and toolbars or in the menus is not affected.

===Layout===
If you want to change the layout width just test it on many devices to make sure your setting works as intended. Other wiki users work with different display settings and can be negatively affected by this change. Unless you have a specific reason to change the content width, you shouldn't adjust this setting. The standard content width is 61.25 rem.

===Headers===
You can adjust the color, font size and underlining for all heading levels. You can also change the unit for the font settings (e.g. ''px'' instead of ''rem''). If you are not familiar with the differences between these units, just leave the default setting, ''rem''. This is based on the superordinate size setting in the wiki. In contrast, ''em'' sizes are in relation to the enclosing container.
[[File:Manual:fs-headings-EN.png|alt=Heading levels|center|thumb|358x358px|Heading levels]]

==Free CSS==
{{Messagebox|boxtype=note|icon=|Note text=If the same styles are defined in both FlexiSkin or FlexiSkin Free CSS and in MediaWiki:Common.css, the styles from Common.css are applied.|bgcolor=}}
For additional customizations that are not possible with the FlexiSkin settings, you can use the ''Free CSS'' field if you are familiar with CSS. Here are some examples.

===Neutral page tools (right sidebar)===
If you select a color for your left navigation bar, you sometimes don't want the color to be applied to the right sidebar (the page tools). To keep the light-grey background, add the following Free CSS:<syntaxhighlight lang="css">
/*right sidebar*/
#sb-sec-cnt {background-color:#efefef; color:#252525;}
#sb-sec-cnt .card-header.menu-title {color:#747474;}
</syntaxhighlight>
[[File:Manual:flexi-free-CSS.png|alt=Example of Free CSS|center|thumb|650x650px|Example of Free CSS]]

===Neutral top bar backgrounds and hovers===
When you set the header hightlight color, it can happen that the automatically calculated values for the searchbar as well as the button hovers and backgrounds don't fit your needs.
[[File:Manual:flexiskin-highlights-standard.png|alt=Flexiskin highlights standard|center|thumb|650x650px|Flexiskin highlights standard]]

In this case, you can neutralize them to grey.
[[File:Manual:flexiskin-highlights-neutral.png|alt=Neutral highlight colors|center|thumb|650x650px|Neutral highlight colors]]

Add the following Free CSS:
<syntaxhighlight lang="css">
/*top bar neutral search box, button backgrounds and hovers */
#nb-pri form input, #nb-pri form button{border-color:#f1f3f3}
#nb-pri form input, #nb-pri form button,#sb-pri-tgl-btn, #sb-pri-tgl-btn:hover,.mws-dropdown-primary.dropdown-menu a:hover,a.ico-btn:hover, a#sb-sec-tgl-btn, #nb-pri form .bs-extendedsearch-searchbar-clear {background:#f1f3f3}
.mws-button-primary:hover {background-color:#747474; color:#fff}
/*top bar neutral bottom border*/
#nb-pri {box-shadow: 0 0 4px 0 #747474}
.card.mega-menu {box-shadow: inset 0 2px 3px -2px #747474}
/*mega menu neutral bottom overlay*/
@media (min-width: 768px){.dropdown-menu.megamenu .mm-bg {background-color:#747474}}
</syntaxhighlight>
 
[[Category:BlueSpice cloud]]
{{translation}}

Manual:Extension/EmbedVideo

2025-06-20T13:29:41Z

Lhuyghe:

<bookshelf src="Book:User manual" />
{{DISPLAYTITLE:Embed videos}}
{{BSVersion|bsvTo=4.3|bsvFeature=EmbedVideo|info=This extension is replaced by [[Manual:Extension/EmbedVideo_(fork)|a forked version.]]}}
BlueSpice integrates the MediaWiki extension ''EmbedVideo'' to embed video files from external video services such as YouTube or Vimeo. ''EmbedVideo'' supports more than 20 video services. In addition, you can also embed videos that have been uploaded to the wiki itself. 
==Embedding external videos==
[[File:Manual:750px-video-extern-einbetten.PNG|alt=3 |center|thumb|533x533px|Embedded external YouTube videos]]
{{Messagebox|boxtype=note|Note text=These instructions are taken and adapted from the [https://www.mediawiki.org/wiki/Extension:EmbedVideo Mediawiki help page] for EmbedVideo.}}
===Syntax===
Use the following parser tag to embed an external video in source editing mode:

<syntaxhighlight lang="text">
{{#evt:
service=youtube
|id=https://www.youtube.com/watch?v=MLIE2642neg
}}
</syntaxhighlight>
You can add additional optional parameter (see [[#Attributes for parser tag #evt|list of attributes]]):<syntaxhighlight lang="text">
{{#evt:
service=youtube
|id=https://www.youtube.com/watch?v=MLIE2642neg
|dimensions=300
|alignment=inline
|description=ISS - Life on the space station 1:04:27
|container=frame
|urlargs=
|autoresize=
|valignment=
}}
</syntaxhighlight>
A shortened syntax is available with the <code>#ev</code> tag:
<syntaxhighlight lang="text">
{{#ev:service|id|dimensions|alignment|description|container|urlargs|autoresize|valignment}}
</syntaxhighlight>Placeholders for unused arguments between two arguments have to remain empty and cannot be removed::
<syntaxhighlight lang="text">
{{#ev:service|id|||description}}
</syntaxhighlight>The shortest option to embed a video is by specifying the service name and the video ID:
<syntaxhighlight lang="text">
{{#ev:youtube|MLIE2642neg}}
</syntaxhighlight>Example with video description (- you can include a line break with the <code><nowiki> </nowiki></code> tag):
<syntaxhighlight lang="text">
{{#ev:youtube|MLIE2642neg|||ISS - Life on the space station 1:04:27}}
</syntaxhighlight>

===Attributes for parser tag #evt===
{| class="contenttable-blue" style="width:100%;" data-sourcepos="123:1-133:266" dir="auto"
! data-sourcepos="123:2-123:46" |attribute
! data-sourcepos="123:48-123:57" |required
! data-sourcepos="123:59-123:67" |default
! data-sourcepos="123:69-123:262" |description
|- data-sourcepos="125:1-125:263"
| data-sourcepos="125:2-125:46" |<code>service="(see supported services below)"</code>
| data-sourcepos="125:48-125:57" |yes
| data-sourcepos="125:59-125:67" |
| data-sourcepos="125:69-125:262" |The video service that is called when the player is created.
|- data-sourcepos="126:1-126:264"
| data-sourcepos="126:2-126:47" |<code><nowiki>id="[id|url]"</nowiki></code>
| data-sourcepos="126:49-126:58" |yes
| data-sourcepos="126:60-126:68" |
| data-sourcepos="126:70-126:263" |The video ID or full URL of the external video.
|- data-sourcepos="127:1-127:596"
| data-sourcepos="127:2-127:48" |<code><nowiki>dimensions="[width|widthxheight|xwidth]"</nowiki></code>
| data-sourcepos="127:50-127:59" |no
| data-sourcepos="127:61-127:69" |640
| data-sourcepos="127:71-127:595" |Dimensions in pixelsto size the container for the player. The default format is width x height. It is possible to omit one of the dimensions. The <code>x</code> always has to be included before the height.
Examples: <code>480</code>, <code>480x320</code>, <code>x320</code>. If the height is not specified, it is calculated using the width and the default ratio of the video service.

Some video services such as ''Gfycat'' don't have a standard height. Therefore, the height setting should be included for each video. With <code>$wgEmbedVideoDefaultWidth</code> the default width can be overwritten in the file <code>LocalSettings.php</code> on the server.
|- data-sourcepos="128:1-128:266"
| data-sourcepos="128:2-128:49" |<code><nowiki>alignment="[left|center|right|inline]"</nowiki></code>
| data-sourcepos="128:51-128:60" |no
| data-sourcepos="128:62-128:70" |none
| data-sourcepos="128:72-128:265" |The video can be placed left, center, right, or inline. Inline allows to add multiple videos in one row. In mobile view, the videos are automatically aligned vertically.
|- data-sourcepos="129:1-129:263"
| data-sourcepos="129:2-129:46" |<code>description="[wiki text]"</code>
| data-sourcepos="129:48-129:57" |no
| data-sourcepos="129:59-129:67" |none
| data-sourcepos="129:69-129:262" |Shows a description below the player container.
|- data-sourcepos="130:1-130:263"
| data-sourcepos="130:2-130:46" |<code>container="[frame]"</code>
| data-sourcepos="130:48-130:57" |no
| data-sourcepos="130:59-130:67" |none
| data-sourcepos="130:69-130:262" |Determines the container type for the player.
<code>frame</code>: Places the video player in a Mediawiki preview box.
|- data-sourcepos="131:1-131:263"
| data-sourcepos="131:2-131:46" |<code>urlargs="modestbranding=1&version=3"</code>
| data-sourcepos="131:48-131:57" |no
| data-sourcepos="131:59-131:67" |none
| data-sourcepos="131:69-131:262" |Allows adding additional URL-arguments to the embedded url. This is useful for settings that are only offered by an individual video service.
|- data-sourcepos="132:1-132:263"
| data-sourcepos="132:2-132:46" |<code>autoresize="false"</code>
| data-sourcepos="132:48-132:57" |no
| data-sourcepos="132:59-132:67" |true
| data-sourcepos="132:69-132:262" |Automatically adjusts the video size if the video would extend beyond the size of the container.
|- data-sourcepos="133:1-133:266"
| data-sourcepos="133:2-133:49" |<code><nowiki>valignment="[top|middle|bottom|baseline]"</nowiki></code>
| data-sourcepos="133:51-133:60" |no
| data-sourcepos="133:62-133:70" |none
| data-sourcepos="133:72-133:265" |Aligns the vertical placement of the video either to the top, middle, bottom, or baseline of the parent element. Using this parameter forces the alignment parameter to be inline.
|}

==Embedding local videos==

=== Media dialog ===
[[Manual:Extension/VisualEditor/Images|Like images]], videos can be inserted directly on a page via the media dialog. The wiki recognizes the file extension and automatically generates the necessary HTML player.

=== BlueSpicePlayer and EmbedVideo ===
Videos that have been uploaded to the Wiki can also be embedded in source editing mode. This can also be done using the extension [[Manual:Extension/BlueSpicePlayer|BlueSpicePlayer]]. BlueSpicePlayer has no functions to embed external videos, however.

The two extensions have the following differences when embedding local video files:

{| class="contenttable-blue" style="width:100%;"
|+
! style="width:20%;" |Syntax/Parameter
! style="width:39%;" |EmbedVideo
!BlueSpicePlayer
|-
| style="width:20%;" |Syntax
| style="width:39%;" |corresponds to the syntax of embedding image files:
<code><nowiki>[[File:samplename.mp4]]</nowiki></code>
|<code><nowiki><bs:showtime>samplename.mp4</bs:showtime></nowiki></code>
|-
| style="width:20%;" |Size
| style="width:39%;" |Only the width can be defined. The video fills the entire width of the player container:[[File:300px-video-size-embedvideo-600.PNG|alt=|center]]<code><nowiki>[[File:Manual:300px-video-size-showtime-600.PNG]]</nowiki></code>
 
|Width and height can be defined separately. If the width of the video is smaller than the video container, the canvas is filled in black.
<code><nowiki><bs:showtime width="600"></nowiki></code>..[[File:Manual:300px-video-size-showtime-600.PNG|alt=BlueSpicePlayer with 600px width|center|thumb|BlueSpicePlayer with 600px width]].
|-
| style="width:20%;" |Loop
| style="width:39%;" | - 
|<code><nowiki><bs:showtime repeat="yes"</code></nowiki>
|-
|Autostart
| -
|<code><nowiki><bs:showtime autostart="yes"</code></nowiki>
|-
| Star/End
|<code><nowiki>[[File:samplename.mp4|start=2|end=6]]</nowiki></code>
Time can be added as: ''ss, mm:ss, hh:mm:ss''
| -
|-
| style="width:20%;" |HTML-Output
| style="width:39%;" |embedded as <video> tag
|embedded through nested <nowiki><div> tags</nowiki>
|-
| style="width:20%;" |Adjusts to mobile display
| style="width:39%;" |yes
|no
|-
| colspan="3" class="col-blue-light-bg" |Player controls
|-
| style="width:20%;" |play button
| style="width:39%;" | yes
|yes
|-
| style="width:20%;" |progress bar
| style="width:39%;" |yes
|yes
|-
| style="width:20%;" |volume adjustment
| style="width:39%;" |yes
|yes
|-
| style="width:20%;" |fullscreen mode
| style="width:39%;" |yes
|yes
|-
| style="width:20%;" |picture-in-picture
| style="width:39%;" |yes
|yes
|-
| style="width:20%;" |download
| style="width:39%;" |yes
|no
|-
| style="width:20%;" |speed adjustment
| style="width:39%;" |no
|yes
|}

== Video container for multiple videos ==

=== The <nowiki><evlplayer> tag</nowiki> ===
Using the tag <code><nowiki><evlplayer></nowiki></code> and the parser function <code>#evl</code>, you can play multiple videos with one video player.
[[File:Manual:350px-video-extern-videocontainer-hook.PNG|link=https://en.wiki.bluespice.com/wiki/Link=Special:FilePath/Manual:video-extern-videocontainer-hook.PNG|alt=|center|thumb|346x346px|Play multiple videos in one player]]
<syntaxhighlight lang="text">
<evlplayer id="Player ID" w="width" h="height" class="class" style="style">defult content</evlplayer>
</syntaxhighlight>A default video can be loaded using <code>defaultid</code>:<syntaxhighlight lang="text"><evlplayer id="player1" w="480" h="360" service="youtube" defaultid="mCtmECVnrOM" /></syntaxhighlight>

==== Attributes for tag <nowiki><evlplayer> </nowiki>====
{| class="wikitable contenttable-blue" style="width:100%;"
! style="background-color:rgb(234, 236, 240);text-align:center;" |attribute
! style="background-color:rgb(234, 236, 240);text-align:center;" |required
! style="background-color:rgb(234, 236, 240);text-align:center;" |default
! style="background-color:rgb(234, 236, 240);text-align:center;" |description
|-
|id
|no
|default
|An optional unique identifier for this container.
|-
|w
|no
|800
|Width to send to the embedded player when its generated.
|-
|h
|no
|16:9 ratio is achieved by the width setting
|Height to send to the embedded player when its generated.
|-
|class
|no
|
|Additional CSS class to add to the container div style no Additional in-line CSS to apply to the container div.
|-
|style
|no
|
|Additional inline CSS to apply to the container div.
|-
|defaultid
|no
|
|Video ID of default video, if you want a default video.
|-
|service
|no
|
|Service of default video, if you want a default video.
|}

=== Adding video links ===
Use the parser tag <nowiki>{{#evl}}</nowiki> to define the videos that should be passed to the player:<syntaxhighlight lang="text">
{{#evl:<video id>|<Link text>>|<video to play>|service=youtube|player=<player id>}}
</syntaxhighlight>Example:<syntaxhighlight lang="text">
{{#evl:mCtmECVnrOM|Departure to Mars|player=example-player}}
</syntaxhighlight>In addition to the attributes for the tag <code>#evt</code> , there are some additional attributes available for the <code>#evl</code> tag.

==== Attributes for parser tag #evl ====
{| class="wikitable contenttable-blue" style="width:100%;"
! style="background-color:rgb(234, 236, 240);text-align:center;width:100px;" |attribtute
! style="background-color:rgb(234, 236, 240);text-align:center;" |required
! style="background-color:rgb(234, 236, 240);text-align:center;" |default
! style="background-color:rgb(234, 236, 240);text-align:center;" |description
|-
| style="width:100px;" |video id
|yes
|none
|The ID of the video you would like to play.
|-
| style="width:100px;" |link text
|yes
|none
|The text to display inside the link.
|-
| style="width:100px;" |player
|no
|‘default’
|Player container to load video in. ''Note that the ID 'default' will only exist if you've defined a player with no ID.<nowiki/><nowiki/>''
|}

=== Example ===
<syntaxhighlight lang="text">
<evlplayer w="600" id="example-player">
default content
</evlplayer>
{{#evl:OLeWbRdW6rY|Let eet Go|1|player=example-player}}
{{#evl:mCtmECVnrOM|Departure to Mars|2|player=example-player}}
{{#evl:MLIE2642neg|ISS - Life in the space station|3|player=example-player}}
</syntaxhighlight>

==Supported video services==
The following video services are supported by the extension EmbedVideo. In parentheses, you find the service names that are used with the tags <code>#evt</code> and <code>#ev</code>:

Archive.org Videos (archiveorg), Bambuser (bambuser), Bing (bing), Blip.tv (blip), C3TV (mediaccde), CollegeHumor (collegehumor), Dailymotion (dailymotion), Disclose.tv (disclose), Daum TVPot (tvpot), Div Share (divshare), Facebook (facebook), FunnyOrDie (funnyordie), Gfycat (gfycat), Hitbox (hitbox), JW Player (jwplayer), Kickstarter (kickstarter), Metacafe (metacafe), Microsoft Stream (microsoftstream), Mixer (mixer), Nico Nico Video (nico), RuTube (rutube), SoundCloud (soundcloud), Spotify Album (spotifyalbum), Spotify Artist (spotifyartist), Spotify Song (spotifytrack), TeacherTube (teachertube), TED Talks (ted), Tubi TV (tubitv), Tudou (tudou), Twitch (twitch), Videomaten (videomaten), Vimeo (vimeo), Vine (vine), Yahoo Screen (yahoo), YouTube (youtube), YouTube Playlist (youtubeplaylist), YouTube Video List (youtubevideolist), Youku (youku)

{{Box Links-en
|Topic1=[https://www.mediawiki.org/wiki/Extension:EmbedVideo Mediawiki help page for the extension EmbedVideo]
|Topic2=[[Manual:Extension/Showtime|Help page for the extension BlueSpicePlayer - only for video files that have been uploaded to the wiki]]
|Topic3=[[Template:Embed video|Template to embed video using the Visual Editor toolbar]]}}
{{translation}}

Manual:Extension/DynamicPageList3

2025-06-20T13:29:08Z

Lhuyghe:

{{DISPLAYTITLE:Creating page lists with DPL3}}
The extension '''DynamicPageList3''' allows you to display lists of wiki pages on other pages. In addition, individual page sections from one wiki page can be included (=transcluded) in another page.

==Examples==
You can view a documentation of all selection criteria and formatting options at [https://help.gamepedia.com/Extension:DPL3 Gamepedia].

This help page contains some typical examples as well as a [[Manual:Extension/DynamicPageList3#List of common parameters and their values|list of common parameters and their values]].

===Transcluding page sections===
To display a section of one wiki page on another page, provide the page name (title) and the section header (include) as parameters:
<syntaxhighlight lang="text">
{{#dpl:|title=Manual:Semantic_MediaWiki|include=#Defining attributes}}
</syntaxhighlight>

===List of subpages===
The following code shows the subpages of the current page in a 3-column layout:
<syntaxhighlight lang="text">
{{#dpl:
|titlematch={{PAGENAME}}/%
|shownamespace=false
|replaceintitle=/{{PAGENAME}}\//,
|columns=3
|mode=none
|rowcolformat=width=100%
}}
</syntaxhighlight>
Example: Display the subpages of the page ''VisualEditor'' in the namespace ''Manual'' in a 1-column layout:<syntaxhighlight lang="text">
{{#dpl:
|titlematch=VisualEditor/%
|shownamespace=false
|namespace= Manual
|replaceintitle=/VisualEditor\//,
|columns=1
|mode=unordered
|rowcolformat=width=100%
}}
</syntaxhighlight>

 
'''Output:'''

{{#dpl:
|titlematch=VisualEditor/%
|shownamespace=false
|namespace= Manual
|replaceintitle=/VisualEditor\//,
|columns=1
|mode=unordered
|rowcolformat=width=100%
}}

If you want to limit the output to the first level of subpages, you can add:<syntaxhighlight lang="text">
|nottitlematch={{PAGENAME}}/%/%
</syntaxhighlight>

===Selecting pages by namespace===
<syntaxhighlight lang="text">
{{#dpl:
|namespace=Manual
|includesubpages=true
|shownamespace=false
|count=5
|ordermethod=title
}}
</syntaxhighlight>
Output:
{{#dpl:
|namespace=Manual
|includesubpages=true
|shownamespace=false
|count=5
|ordermethod=title

}}

===== Category format =====
<syntaxhighlight lang="text">
<div class="dplcategory">
{{#dpl:
|namespace=Manual
|includesubpages=true
|shownamespace=false
|mode=category
|ordermethod=titlewithoutnamespace
}}
</div>
</syntaxhighlight>

 '''Output:'''

[[File:DynamicPageList3 categoryoutput.png|alt=Category format|1091x1091px]]

If the sorting letters are displayed at the end of a column, the display can be improved by inserting css declarations on the page ''MediaWiki:Common.css'' :<syntaxhighlight lang="css">
/*dpl column layout - avoid header orphans */
.dplcategory {-webkit-column-count:3;column-count:3;}
.dplcategory .mw-category .mw-category-group {display:block}
.dplcategory .mw-category-group {margin:0 2em 2em 2em;}
.dplcategory .mw-category-group h3 {break-after:avoid}
.dplcategory .mw-category-group h3 {margin:0 0 0.3em; border-bottom:1px solid #e2e2e2}
</syntaxhighlight>'''Improved output:'''

[[File:DynamicPageList3 categoryformatwithcss.png|alt=category format with css|1078x1078px]]

==== Category layout ====

===Selecting pages by category===
<syntaxhighlight lang="text">
{{#dpl:
|category=Editing
|addcategories=true
|includesubpages=true
|shownamespace=false
|count=5
|ordermethod=title
|mode=ordered
}}
</syntaxhighlight>
Output:
{{#dpl:
|category=Editing
|addcategories =true
|includesubpages=true
|shownamespace=false
|count=5
|ordermethod=title
|mode=ordered
}}

===Selecting pages with specific naming patterns===
<syntaxhighlight lang="text">
{{#dpl:
|namespace=File
|titlematch=A%
|count=5
}}

</syntaxhighlight>Output:{{#dpl:
|namespace=File
|titlematch=A%
|count=5
}}

 

 
==List of common parameters==

===Criteria for page selection===
{| class="wikitable" style="width:100%;"
!Parameter
!Syntax
! style="width:380px;" |Description
|-
|category
|''<nowiki>|category=QM|Setup...</nowiki>''
| style="width:380px;" |Pages in the category QM OR Setup
|-
|
|''<nowiki>|category=QM&Setup&...</nowiki>''
| style="width:380px;" |Pages in the categories QM AND Setup
|-
|
|''<nowiki>|category=QM|Setup...|category=Admin</nowiki>''
| style="width:380px;" |Pages in the categories QM OR Setup, and pages in the category Admin
|-
|notcategory
|''<nowiki>|notcategory=QM</nowiki>''
| style="width:380px;" |Pages that are not in the category QM
|-
|categoriesminmax
|''<nowiki>|category=QM|categoriesminmax=2</nowiki>''
| style="width:380px;" |Pages that are in the category QM and in at least 2 more categories
|-
|
|''<nowiki>|category=QM|categoriesminmax=,1</nowiki>''
| style="width:380px;" |Pages that are only in the category QM and in no other category
|-
|namespace
|''<nowiki>|namespace=</nowiki>''
| style="width:380px;" |Pages in the namespace (Main)
|-
|
|''<nowiki>|namespace=Help|Manual</nowiki>''
| style="width:380px;" |Pages in the namespace Help OR Manual
|-
|namespacenot
|''<nowiki>|namespacenot=Help</nowiki>''
| style="width:380px;" |Pages that are not in the namespace Help
|-
|
|''<nowiki>|namespacenot={{NAMESPACE}}</nowiki>''
| style="width:380px;" |Pages that are not in the namespace of the current wiki page
|}

===Output-Format===
{| class="wikitable" style="width:100%;" data-ve-attributes="{"style":"width:100%;"}"
!Parameter
!Syntax
! style="width:380px;" data-ve-attributes="{"style":"width:380px;"}" |Description
|-
|mode
|''<nowiki>|mode=ordered</nowiki>''
| style="width:380px;" data-ve-attributes="{"style":"width:380px;"}" |Unordered list
|-
|
|''<nowiki>|mode=unordered</nowiki>''
|Numbered list
|-
|
|<nowiki>|</nowiki>''mode=none''
|Line breaks
|-
|
|<nowiki>|</nowiki>''mode=category''
|Pages are grouped alphabetically with a letter heading (similar to category pages)
|-
|
|''<nowiki>|mode=inline|inlinetext=&nbsp; &bull; &nbsp;</nowiki>''
|Page names are listed on the same line and separated with a bullet point
|}
===Sorting===
{| class="wikitable" style="width:100%;" data-ve-attributes="{"style":"width:100%;"}"
!Parameter
!Syntax
! style="width:380px;" data-ve-attributes="{"style":"width:380px;"}" |Description
|-
|ordermethod
|''<nowiki>|ordermethod=title</nowiki>''
| style="width:380px;" data-ve-attributes="{"style":"width:380px;"}" |Ordered by page (prefix+)title
|-
|
|''<nowiki>|ordermethod=titlewithoutnamespace</nowiki>''
|Ordered by page name independent of namespace
|-
|
|''<nowiki>|ordermethod=counter</nowiki>''
|Ordered by number of page views (popularity)
|-
|
|''<nowiki>|ordermethod=size</nowiki>''
|Ordered by page size
|-
|
|''<nowiki>|ordermethod=firstedit</nowiki>''
|Ordered by creation date
|-
|
|''<nowiki>|ordermethod=lastedit</nowiki>''
|Ordered by last edit date
|-
|
|''<nowiki>|ordermethod=user,firstedit</nowiki>''
|Ordered by author, then by creation date
|-
|
|''<nowiki>|ordermethod=user,lastedit</nowiki>''
|Ordered by last editor, then by last edit date
|-
|order
|''<nowiki>|order=ascending</nowiki>''
|Sorted in ascending order
|-
|
|''<nowiki>|order=descending</nowiki>''
|Sorted in descending order
|}

===Display of meta data===
{| class="wikitable" style="width:100%;" data-ve-attributes="{"style":"width:100%;"}"
!Parameter
!Syntax
! style="width:380px;" data-ve-attributes="{"style":"width:380px;"}" |Description
|-
|addcategories
|''<nowiki>|addcategories=true</nowiki>''
| style="width:380px;" data-ve-attributes="{"style":"width:380px;"}" |Shows all categories of a page after the page name
|-
|addpagecounter
|''<nowiki>|category:QM|ordermethod=counter|order=descending</nowiki>''
''|addpagecounter=true|count=5''
|Shows the 5 most popular pages in the category QM
|-
|adduser
|''<nowiki>|category=QM|ordermethod=lastedit|adduser=true</nowiki>''
|Adds the name of the last editor in front of the page name
|-
|addauthor
|''<nowiki>|category=QM|addauthor=true</nowiki>''
|Adds the name of the original author in front of the page name.
|}

== Disabling automatically generated DPL categories ==
This extension is creating some sometimes unwanted automatic system categories that are then displayed on each wiki page that includes a DPL parser function.

 
To hide these categories, follow these steps:

# '''Go''' to page ''Special:TrackingCategories'' in your wiki
# '''Click''' on ''dpl-parserfunc-tracking-category'' in the column ''Message name''
# '''Replace''' the text ''Pages using DynamicPageList parser function not wanted'' with a dash ("-"). The category will no longer be displayed on your wiki pages.
# '''Save''' the page.
The system category is no longer displayed on your wiki pages.

See also: https://www.mediawiki.org/wiki/Help:Tracking%20categories

 

{{translation}}
[[Category:Organization]]
[[Category:Customization]]

Manual:Extension/BlueSpiceUserManager

2025-06-20T13:27:27Z

Lhuyghe:

<bookshelf src="Book:Admin manual" />
{{DISPLAYTITLE:User manager}}
The extension '''BlueSpiceUserManager''' provides the visual interface for user administration.
==About the User manager==
Administrators can access the User manager in the [[Manual:Extension/BlueSpiceDiscovery#Header bar|Global actions]] menu under ''Administration > Users (''link to page ''Special:UserManager).'' It shows an editable list of all user accounts.
[[File:Manual:Extension BlueSpiceUserManager 1743170306607.png|center|thumb|600x600px|User manager page]]
==Create a user account==
'''To create a user account:'''

#'''Click''' the "+ Add"-button. This opens a dialog.[[File:Manual:Extension BlueSpiceUserManager 1743170419859.png|center|thumb|300x300px|Create a user account]]
#'''Enter''' the user information in the dialog:
#*''Username:'' must be unique and cannot contain special characters
#*''Password and Confirm password:'' The password for the new user.
#*''Real name:'' can be a duplicate of an existing user's real name (optional)
#*''Email:'' The email address of the user (optional)
#*Groups: a user can be assigned to multiple groups. If no group is selected, the user belongs to the default group ''user''.
#Click '''Save''' to create the user account.
{{Messagebox|boxtype=tip|icon=|Note text=If you do not want to provide the new user with a password that is known to you, you can create the user account via the page ''Special:CreateAccount'' instead. It is, however, not possible to assign a user group to the new account during account creation on that page.|bgcolor=}}

=== Invite user ===
A user account can also be created via an invitation. This allows users to choose their own username and password. The accounts are automatically created in the "user" group. User groups can be set for multiple users at the same time by selecting the users and clicking on the "groups" icon above the grid. This resets the groups for the selected users and assigns the newly chosen groups.

==Edit a user account==
[[File:Manual:Extension BlueSpiceUserManager 1743170640214.png|center|thumb|600x600px|Edit a user account]]
By selecting one or more users in the list, two options are available above the list of users:

* ''Edit groups:'' Assign groups to these user account(s)
* ''Block users:'' Disable/enable user accounts. A user account cannot be deleted.

In addition, some functions are available for each individual user on the right on the table:

*''Pen icon:'' Edit real name, email or groups
*''Change password:'' Change the password.
*''Block user:'' Disable/enable user account. A user account cannot be deleted.
{{Messagebox|boxtype=tip|Note text=User groups can be set for multiple users at the same time by selecting the users and clicking on the "groups" icon above the grid. This resets the groups for the selected users and assigns the newly chosen groups.}}

==Inactive users==
[[File:Manual:Extension BlueSpiceUserManager 1743171139789.png|center|thumb|600x600px|View inactive users]]
By default, the list displays users with active user accounts (enabled).

To view inactive users, click on "Show blocked users".

{{Messagebox|boxtype=note|icon=|Note text=User accounts cannot be deleted. They can only be disabled.|bgcolor=}}

== Subscription key ==
The number of users displayed depends on which subscription key is entered in the [[Manual:Extension/BlueSpiceConfigManager|configuration management]] under ‘System’ in the ‘BlueSpiceProDistributionConnector’ area. If the entry is empty, please contact your project manager. Deactivated users are not counted in the number of subscriptions used.
{{translation}}

[[Category:Permissions]]

Manual:Extension/BlueSpiceSocialArticleActions

2025-06-20T13:25:17Z

Lhuyghe:

<bookshelf src="Book:User manual" />
{{translation}}

Archive:Manual:Extension/BlueSpiceSocial

2025-06-20T13:24:51Z

Lhuyghe:

<bookshelf src="Book:User manual" />
{{DISPLAYTITLE:Introduction to BlueSpice Social}}

'''BlueSpiceSocial''' is a set of extensions that add social features around a wiki page. It allows users to quickly communicate on the wiki and to express their opinion on pages.
==Scope==
BlueSpice Social contains the following functionality:
*'''User profile:''' Provides the page ''User:<username>.''
*'''Attachments:''' Connects uploaded files to wiki pages.
*'''Discussions:''' Enables discussions with comments created on wiki pages. Discussion entries can be marked as "closed".
*'''Activities:''' Automatically creates pages in the ''SocialEntity'' namespace to track page edits and creations.
*'''Blog:''' Provides the special page ''Special:Blog''. A blog view can also be embedded into individual wiki pages.
*'''Microblog:''' Similar to blog entries, but without a headline.
*'''Timeline:''' A chronological list of all social entities. The timeline filter can be used for displaying social entities on wiki pages.
<section end="training-slides" /><section end="training-maintainer" />

==User profile==
Every user has a profile that is displayed on the page ''User:<username>''. Users can access their user profile by clicking on ''Profile'' in the user menu (located in the [[Manual:Extension/BlueSpiceDiscovery|header bar]]).

The user profile shows the user's basic information (depending on the wiki setup) and the user's profile image.
Below the user info, the user's wiki activities are listed: Comments the user made, actions on pages, and in general the user's activity on the wiki. It also allows other users to leave comments on the user's profile page.[[File:Profile1a-en.png|thumb|User profile|alt=User profile|center|650x650px]]
==Discussions==
BlueSpiceSocial integrates a discussion section at the bottom of every wiki page. This section allows users to create comments directly on a wiki page. If it is the first entry in a discussion, the discussion page is automatically created at this time if this is configured in the [[Manual:Extension/BlueSpiceConfigManager|Configuration manager]].

The discussion section can be disabled on the page-level by adding the [[Manual:MagicWords|MagicWord]] ''<nowiki></nowiki>'' to the page in source editing mode.

==Timeline==
[[File:Timeline1a-en.png|thumb|alt=Timeline|center|650x650px|Timeline]]
Timeline is a special page that provides an overview of all social conversations on the wiki.

By default, it is listed on the ''Main navigation''. You can also access the page directly at <code>Special:Timeline</code>.
On this page, users can sort and filter existing social entries or create new entries.

===Creating new entries===
To create a new entry, click on the "Plus" icon to add a new timeline entry:

*'''Blog entry''': [[#Blog|Blog]] is used for topics to be shared with other users on the wiki
*'''Microblog''': Like a blog entry, but without titles. It should be used for a short entry, e.g., a quick announcement.
*'''Discussion topic''': Adds a discussion entry to a particular wiki page.

===Interacting with social entities===
Every entry in the timeline is called a social entity. Depending on the type of social entity, the following interaction options exist:

*'''Comments:''' Number of comments related to the entity. Clicking on ''Comments'' opens all current comments and allows users to add a comment (if user has the necessary permissions).
*'''Recommend:''' Number of users that recommended the entity. Uers can add a recommendation by clicking on ''Recommend''.
*'''Linked articles:''' Number of articles linked to this entity Clicking on ''Linked articles'' shows the list of linked articles.
*'''Watch/Unwatched:''' Shows if the user is currently watching the entity (the receives notifications when the entity is changed). Clicking on Watch or Unwatch changes the state of watching.
*'''Resolved/Unresolved''': The status of the entity. Some entities, like discussions on a question can have a status attached to them, so that other users know if the question is answered.
==Blog==
[[Manual:Extension/Blog|Blog]] is a special page showing an overview of all blog entities available on the wiki. By default, it is listed on the ''Main navigation.'' You can also access the page directly at <code>Special:Blog</code>.
Users can sort and filter the list entries by clicking on the icons above the list.

Learn how to [[Manual:Extension/BlueSpiceSocialBlog|include the blog on any wiki page]].

==Permissions==
From BlueSpice version 3.2.7 the following roles have associated "social" permissions. Earlier versions have no option to limit the creation and editing of blog entries by using the role ''commenter.''
 
{| class="contenttable-blue" style=""
!Rechte/Rolle
!commenter
!editor
!admin
!maintenance- 
admin
!Berechtigung
|-
|Create and edit blog entry
|
|x
|x
|x
|social-blog
|-
|Comment on blog entry
|x
|x
|x
|x
|social-blog-comment
|-
|Create and edit microblog entry
|x
|x
|x
|x
|social-microblog
|-
|Comment on microblog entry
|x
|x
|x
|x
|social-microblog-comment
|-
|Create discussion entry
|x
|x
|x
|x
|social-topics
|-
|Comment on discussion entry
|x
|x
|x
|x
|social-topics-comment
|-
|Create and edit attachments
|x
|x
|x
|x
|soical-stash
|}
The comments function for blog, microblog and discussion entries can be deactivated in the LocalSettings-file on the server.

==Deactivating the comments feature==
The comment function for comments on blog, microblog and discussion entries can be deactivated in the LocalSettings file on the server.
$bsgSocialCanHaveChildrenBlacklist = [
'blog', // disable comments on blog
'topic', // diable comments on discussion topics
'microblog' // disable comments on microblogs
];
 {{Box Links-en
|Topic1=[[Manual:Extension/BlueSpiceSocialBlog|Blog]]
|Topic4=[[Reference:BlueSpiceSocial]]
|Topic5=
|Topic2=[[Manual:Extension/BlueSpiceSocialWikiPage|Discussions and Attachments]]
|Topic6=
}}
{{translation}}
[[Category:Social]]

Manual:Extension/BlueSpiceSaferEdit

2025-06-20T13:24:09Z

Lhuyghe:

{{DISPLAYTITLE:Unsaved changes (autosave)}}

The extension '''SaferEdit''' automatically saves a page at predefined intervals. If the page cannot be saved during editing (e.g., due to a browser crash), the unsaved user changes will be preserved for the user until the next page save.

== About autosaved changes ==
 '''Recovery version:''' A recovery version is saved every 10 seconds during editing and is only available to this user. It is not deleted when logging off and available when the user logs on again.

{{Messagebox|boxtype=important|icon=|Note text=If you leave the page (e.g., by closing the browser or the browser tab), then the existing recovery version is automatically deleted and no longer available.

So if you have an issue with saving the page (e.g. lost internet connection) make sure to leave the page open until you can resave the page.

If a page is crashed/stuck, you can safely reload it using the "F5" button. The autosaved changes will be available for you.|bgcolor=}}

== Edit conflicts==
When a user has a page open in edit mode, the page shows a page banner to indicate that changes are being made.
[[File:BlueSpiceSaferEdit banner.png|alt=Screnshot of the banner that shows who is editing the page|center|thumb|650x650px|Banner indicating that a user is working on the page]]

The first person to save the page that was edited by multiple users can save the page without issues. The next person needs to work through a page that will indicate the changes of the first person. They will have to be merged with the changes of the second person.

It is advisable that only one user at a time works on a wiki page.
==User settings==
Users can set in there preferences under the tab ''Editing'' if they want to see a warning message when they leave the page without saving pending changes. This setting is activated by default. 
[[File:SaferEdit-warning.png|alt=Warning when leaving an unsaved page|center|thumb|500x500px|Warning when leaving an unsaved page]] 
==Configuration==
In the [[Manual:Extension/BlueSpiceConfigManager|Config Manager]], administrators can change the following settings:{{#dpl:title=Manual:Extension/BlueSpiceConfigManager|include=#BlueSpiceSaferEdit}}

{{Box Links-en|Topic1=[[Reference:BlueSpiceSaferEdit]]}}
{{translation}}

__FORCETOC__
[[Category:Editing]]

Manual:Extension/BlueSpicePlayer

2025-06-20T13:23:03Z

Lhuyghe:

{{DISPLAYTITLE:Video Player}}

The extension BlueSpice '''Player''' allows you to embed local video files in a page. These files have to be uploaded to your wiki first.

If you want to embed videos from a video sharing service such as Youtube, you can use the installed extension ''EmbedVideo''. EmbedVideo is documented at [https://www.mediawiki.org/wiki/Extension:EmbedVideo www.mediawiki.org/wiki/Extension:EmbedVideo].

==How to use the video player==

Use the tag <code><nowiki><bs:showtime>Video.mp4</bs:showtime></nowiki></code> anywhere in an article to activate the player. Upload the video into your wiki first. You can upload the video just like an image (''Global actions > Upload file'').

The following video formats are supported: '''mp4, ogv, flv, webm'''
<bs:showtime autostart="false">gizmo.mp4</bs:showtime>
 

===Optional arguments===

You can configure the player with the following arguments:

{| class="contenttable-blue"
|-
! style="width:100px;" class="background-color" |Argument
! style="width:300px;" class="background-color" |Description
! style="width:150px;" class="background-color" |Type
! style="width:150px;" class="background-color" |Default
|-
||''width''
||Width of the video
||int
||320
|-
||''height''
||Height of the video
||int
||240
|-
||''autostart''
||Automatically starts the video when the page is loaded
||bool
||false
|-
||''repeat''
||Automatically repeats the video in a loop
||bool
||false
|}

'''Example syntax''': <code><nowiki><bs:showtime width="960" height="760" autostart="true">Testvideo.mp4</bs:showtime></nowiki></code>
===Compatibility matrix===

For technical reasons, not all video formats can be played in all browsers.

{| class="contenttable-blue"
|-
! style="width:150px;" class="background-color" |Format
! style="width:150px;" class="background-color" |Firefox
! style="width:150px;" class="background-color" |Chrome
! style="width:150px;" class="background-color" |Internet Explorer
|-
||mp4
||yes
||yes
||yes
|-
||flv
||yes
||yes
||yes
|-
||ogv
||yes
||yes
| style="" |no
|-
||webm
||yes
||yes
| style="" |no
|}

'''Please note:''' due to VideoJS standards, the player is set back from HTML5 to Flash when playing an flv-file or using Internet Explorer.

==Technical details==
The video player is enabled by the extension BlueSpicePlayer. An administrator has to add the necessary video extensions to the allowed file extensions in the [[Manual:Extension/BlueSpiceConfigManager|Config Manager]].
{{Box Links-en|Topic1=[[Reference:BlueSpicePlayer]] (for embedding videos that are uploaded to the wiki)|Topic2=[[Reference:EmbedVideo]] (for embedding videos form external services such as YouTube)}}
 
{{translation}}

Archive:Manual:Extension/BlueSpiceGroupManager

2025-06-20T13:19:56Z

Lhuyghe:

<bookshelf src="Book:Admin manual" />
{{DISPLAYTITLE:Group manager}}
The interface for the Group manager is provided by the extension '''GroupManager'''. It allows adding, renaming and deleting groups.
==Functionality==
Users with the right ''groupmanager-viewspecialpage'' (in roles: ''admin, maintenanceadmin, accountmanager'') can access the page ''Special:GroupManager'' in the menu ''Global actions > Administration> Groups''.

An administrator can go to ''Global actions > Management > Group manager''. This opens the page ''Special:GroupManager''.
[[File:Manual:groupmanager.png|alt=Group manager|center|thumb|750x750px|Group manager]]
 

.The group manager has the following features:
*'''Viewing groups:''' All existing groups in the wiki are listed.
*'''Creating new groups:''' Clicking on the "plus" button opens a dialog for adding a new group.
*'''Renaming groups:''' A group can be renamed by selecting it and then clicking the wrench icon. System groups and groups declared by other extensions cannot be renamed.
*'''Deleting a group:''' A group can be deleted by selecting it and then clicking the "x" button. System groups cannot be deleted.

 Assigning roles and users to groups

* To assign users to groups, use the [[Manual:Extension/BlueSpiceUserManager|User manager]].
* To assign roles (permissions) to groups, use the [[Manual:Extension/BlueSpicePermissionManager|Permission manager]].

{{Box Links-en
|Topic1=[[Reference:BlueSpiceGroupManager]]
|Topic2=[[Manual:Extension/BlueSpicePermissionManager|Managing permissions]]}}
 
{{translation}}

__FORCETOC__
[[Category:Permissions]]

Manual:Extension/BlueSpiceExtendedStatistics

2025-06-20T13:19:19Z

Lhuyghe:

{{DISPLAYTITLE:Extended statistics}}

The extension '''ExtendedStatistics''' provides an analytic view of many relevant parameters on the wiki, providing wiki administrators better insight into the functioning of the wiki.

==Where to find Extended statistics==

The navigation link ''Extended statistics'' in the tab Global actions loads the page ''Special:ExtendedStatistics''.

 
[[File:Manual:extendedstatistics.png|alt=|center|thumb|441x441px|Extended statistics navigation link]]

==Choosing a data source==

ExtendedStatistics can show data for multiple aspects of the wiki. Available data sources are:

*''Number of users:'' All the users that registered in the period chosen
*''Number of pages:'' All pages created in the period chosen.
*''Number of content pages:'' All articles in content namespaces created in the period chosen
*''Number of edits:'' All edits carried out in the period chosen
*''Edits per user:'' Number of edits per user in the period chosen
*''Search queries:'' All terms users searched for in the period chosen. Only availble if [[Manual:Extension/ExtendedSearch|BlueSpiceExtendedSearch]] is installed.

==Choosing filters==

General filters:

*From - Date from which to display data
*To - Date to which to display data

Some data sources may have additional filters available, like for data sources based on wiki pages, namespace filter is available.

 
[[File:Manual:Mediawiki Extension ExtendedStatistics.png|alt=Selecting a query type|center|thumb|300x300px|Selecting a query type]]
 

==Display settings==

The display of the results is determined by the following settings:

*Interval - grain of the diagram - determines which time unit will be used to group the data.
*Mode - display type:
**Absolute - shows changes in data for the given period
**Aggregate - shows running total for the data source choosen
**List - shows data in tabular view - only avaiable for search statistics
{{Messagebox|boxtype=note|Note text=Depending on the selected time period, the interval has to be set accordingly. For, example if you look for data between 02.06. and 03.06. for the same year, the interval setting "Year" will not return any data. Change the interval to "Week" or "Day" to return results.}}

==Viewing the results==

Once all the filters and options are set, click on the ''Results'' tab to show the resulting data.

 
[[File:Manual:ExtendedStatistics3.png|alt=|center|thumb|335x335px|Result view with export buttons]]
 

==Chart export==
In results view there is an ''Export-''button that allows the user to export and download the currently displayed chart as SVG.

==Data export==

===Maintenance script===
A <code>php</code> maintenance script will be provided on the following location:

<code><mw-root>/extensions/BlueSpiceExtendedStatistics/maintenance/ExportCollection.php</code>

===Usage===
This script must be called on the command line of the server. It takes the path of a configuration file in <code>JSON</code> format.

'''Example'''
php <mw-root>/extensions/BlueSpiceExtendedStatistics/maintenance/ExportCollection.php \
--config=<path-to-file>/myConfig.json \
--exportto=/tmp/myExport.xslx
'''Params'''

*<code>--config</code> - path to config file
*<code>--exportto</code> - path to the file, the data gets exportet to. Note that vaiable file formats are <code>xsl</code>, <code>xslx</code> and <code>csv</code>

===Scirpt configuration===
The script configuration will take the same parameters as the API, which is used on Special:ExtendedStatistics.

'''Params'''

*<code>aggregate</code>
*<code>filter</code>

===Example contents===
The following examples show the content of the JSON file provided to <code>--config</code>.

'''"Page views" aggregated by date over 1 year'''
{
"aggregate": [
{
"property": "timestampcreated",
"type": "daily",
"targets": [
"pagetitle",
"numberhits",
"numberhitsaggregated"
]
}
],
"filter": [
{
"property": "type",
"type": "string",
"value": "hitcounter",
"comparison": "eq"
},
{
"property": "timestampcreated",
"type": "date",
"value": "20200707120000",
"comparison": "gt"
},
{
"property": "timestampcreated",
"type": "date",
"value": "20210707120000",
"comparison": "lt"
}
]
}
'''"Review by namespaces" aggregated by namespace over 1 year''':
{
"aggregate": [
{
"property": "namespacename",
"type": "string",
"targets": [
"ongoingpages",
"expiredpages",
"notrunningpages",
"ongoingpagesaggregated",
"expiredpagesaggregated",
"notrunningpagesaggregated"
]
}
],
"filter": [
{
"property": "type",
"type": "string",
"value": "reviewedpages-ns",
"comparison": "eq"
},
{
"property": "timestampcreated",
"type": "date",
"value": "20200707120000",
"comparison": "gt"
},
{
"property": "timestampcreated",
"type": "date",
"value": "20210707120000",
"comparison": "lt"
}
]
}
 
==Configuration==

In the [[Manual:Extension/BlueSpiceConfigManager|Config manager]], you can change the following settings:

{{#dpl:title=Manual:Extension/BlueSpiceConfigManager|include=#BlueSpiceExtendedStatistics}}

{{Box Links-en|Topic1=[[Reference:BlueSpiceExtendedStatistics]]}}
{{translation}}

__FORCETOC__

[[Category:Administration]]

Manual:Extension/BlueSpiceChecklist

2025-06-20T13:16:40Z

Lhuyghe:

{{DISPLAYTITLE:Checklists}}

'''BlueSpiceChecklist''' allows you to insert a drop-down checklist or a checkbox. Users with edit rights can change the status or value directly in view mode.

{{Textbox|boxtype=note|header=Note:|text=In contrast, checkboxes for tasks are created as a [[Manual:Extension/SimpleTasks| Task list]].|icon=yes}}

==Checklist==
The checklist is inserted as a [[Manual:Extension/ContentDroplets|Content droplet]]. The selected list value can only be changed in the view mode of the page. This creates a new page version.
[[File:Droplet Checklist.png|alt=Dropdown menu with selection of pizzas|center|thumb|223x223px|Droplet "Checklist"]]

===Defining list values===
The list values must be predefined on a page in the template namespace. The elements must be created as an unordered list. In the source code of the page, list items are created with a <code>*</code> at the beginning of the line.

For example, if you want to create a list of pizzas from which a specific pizza can be selected, you can create a Template:Pizza page with the following content:

<pre>
* Choose a pizza ...
* Margherita
* Schinken
* Salami
* Pilze
* Hawaii
* Gamberetti
* Diavolo
* Siziliana
* Quattro Formaggi
</pre>

In addition, a font color (using [[wikipedia:Web_colors#Hex_triplet|HEX-code]] notation) can be specified for each entry:<pre> * Quattro Formaggi | #00FF00 </pre>

===Inserting the list===
The list can now be selected in the control list selection menu.
[[File:Checklist inspector.png|alt=checklist inspector for selecting the template Pizza|center|thumb|300x300px|Choose the list]]

This generates the following tag in the source code:<syntaxhighlight lang="text">
<bs:checklist type="list" list="Template:Pizza" value="Choose a pizza..." />
</syntaxhighlight>Der parameter ''list'' legt die Seite fest, auf der sich die vordefinierte Liste befindet; ''value'' legt den Wert fest, der voreingestellt sein soll.

The parameter ''list'' specifies the page for the list values. The parameter ''value'' specifies the default value.

==Checkboxes (source edit only)==
In addition, it is possible to create individual checkboxes in source edit mode:<pre><bs:checkbox checked="false" /> Margherita
<bs:checkbox checked="true" /> Siziliana
</pre>
===Differences between checkboxes and task lists===
{| class="wikitable"
|+
!Function
!Checkbox
(BlueSpiceChecklist)
!Task list
(Checklists)
|-
!Insert
|in source edit mode
|
*as Content droplet
*via keyboard shortcut <code>[]</code>
*in source edit mode
|-
!Selection
|in view mode
|
*in view mode (tracks status change in version history)
*with the visual editor (no status tracking)
|-
!Status
|checkbox shows a check mark
|
*checkbox shows a check mark
*closed tasks have strike-through formatting
|-
!Overview
|no overview available
|
*filtered overview of all tasks is possible
*stored as page property
|-
!Edit permission
|roles: editor, author, maintenanceadmin, bot
|"edit" permission
|}
<gallery widths="180" heights="120">
File:checkbox example.png|alt=2 checkboxes for selecting Margherita or Siziliana|Checkbox
File:task example.png|alt=Completed task "Order a pizza" and open task "Pick up the pizza"|Tasks
</gallery>

==Compatibility of checkboxes {{Bsvs|bsvFrom=4.3}}==
The Content Droplet ''Checklist'' is available from BlueSpice 4.3. Since this has changed the syntax, checkboxes that were previously created with the <nowiki><bs:checklist /></nowiki> tag must be adjusted accordingly. If there are many checkboes, this can be done using the page [[mediawikiwiki:Extension:Replace_Text/en#Usage|Special:ReplaceText]].

The syntax <<code>bs:checklist value="Salami" type="check" /></code> no longer works as of BlueSpice 4.3.

New integration:<syntaxhighlight lang="text">
<bs:checkbox checked="false" /> Margherita
<bs:checkbox checked="true" /> Siziliana
</syntaxhighlight>
{{Textbox|boxtype=important|header=Important!|text=Checklists and checkboxes cannot be used on a page at the same time.

If you use a checklist on a page, you can, however, create a [[Manual:Extension/SimpleTasks|task list]] as well.|icon=yes}}

==Configuration==

The following configuration can be changed in the [[Manual:Extension/BlueSpiceConfigManager|Config manager]]:

{{#dpl:title=Manual:Extension/BlueSpiceConfigManager|include=#BlueSpiceChecklist}}
[[Category:Content]]

==Permissions==

If a wiki page contains a checklist, any user with the c''hecklistmodify'' right can update the checklist values. This action occurs in view mode of the page. By default, these ar users in the roles ''editor, author, maintenanceadmin'' or ''bot''
==Magic word "checklist" (obsolete) {{Bsvs|bsvTo=4.2}}==

Until BlueSpice 4.2, checklist elements were inserted as magic word. To create a checklist item:
#'''Click''' ''Insert > More > Magic word'' in the visual editor. 
#'''Click''' c''hecklist'' in the dialog window. 
#'''Click''' ''Done''. Another dialog window appears.[[File:Manual:magicword-dialog-EN.png|alt=|center|thumb|Dialog window for checklists]]
#Select the tab to select your checklist type:
#*''Checkbox:'' creates an individual checkbox.
#*''List:'' creates a drop-down menu.

===Creating a checkbox===

#'''Toggle''' the switch in the dialog window on the checkbox tab to create an unselected checkbox. When this toggle is blue, the checkbox is pre-selected.
#'''Select''' ''insert.'' The checkbox is now visible on the page. Write the text for a label or for an instruction next to the checkbox

After the page has been saved, all users can activate and deactivate the checkbox.

===Creating a drop-down list===

# '''Select''' an [[Manual:Extension/BlueSpiceChecklist#Defining list values|existing option list]] in the ''List'' tab.
# Under Selected option, choose the default value.
# '''Click''' Done.

{{translation}}
[[Category:Content]]

Manual:Extension/BlueSpiceAuthors

2025-06-20T13:15:39Z

Lhuyghe:

{{DISPLAYTITLE:Page info: authors}}

'''BlueSpiceAuthors''' displays the profile images of the users who have contributed to a wiki page.
==Page information==
Authors of a page are listed on the ''Page information'' in the [[Manual:Extension/BlueSpiceDiscovery#Page tools|page tools]].
''.''
[[File:Manual:PageInformation.png|link=link=https://en.wiki.bluespice.com/wiki/File:Authors2.jpg|alt=|center|thumb|Page tools]]

==Configuration==

In the [[Manual:Extension/BlueSpiceConfigManager‏‎‏‎|Config manager]] you can change if authors are shown on the Page information or not.
[[File:Manual:300px-configmanager-authors.png|alt=|center|thumb|Config manager]]

===Output===
 
{{#dpl:title=Manual:Extension/BlueSpiceConfigManager|include=#BlueSpiceAuthors}}Authors are listed in their role of original author or subsequent editor. {{Box Links-en|Topic1=[[Reference:BlueSpiceAuthors]]}}

[[Category:Page tools]]
{{translation}}

Manual:Extension/BlueSpicePageTemplates

2025-06-20T13:08:58Z

Lhuyghe:

<bookshelf src="Book:Admin manual" />
{{DISPLAYTITLE:Page templates}}

== Characteristics of a page template ==
A page template applies a predefined content structure and layout to new pages. Page templates are useful for frequently used content formats such as meeting minutes, reference pages or process descriptions, for example.

'''The following characteristics are typical for a page template:'''
*it can only be activated by administrators
*the underlying content itself can be created by any editor in the template namespace
*it can only be used for the initial creation of a page
*it can also contain (standard) templates
*it creates a prefilled page
*it can be restricted to certain namespaces
*it can be grouped ("tagged") with other templates
*it can contain categories
*it can be applied using different page creation mechanisms, such as the New-button, an [[Manual:Extension/InputBox|inputbox]], or a [[mediawikiwiki:Extension:Page_Forms/Linking_to_forms#Preloading_data|page form]].
== Standard page templates ==
{{BSVersion|bsvFrom=4.2|bsvTo=|bsvFeature=}}
Page templates that are installed by default can be deleted (1) from the page [[Manual:Extension/BlueSpicePageTemplates#Creating a page template|template manager]] .
[[File:Manual:Extension BlueSpicePageTemplates 1743087345291.png|center|thumb|500x500px|Page template manager]]

Alternatively, the templates can be adapted directly in the template namespace. To do this, click on the template link in the column ''Template'' (2).

=== List of standard templates ===
{| class="wikitable" style="width:100%;"
! style="" |Page template
! style="" |Edition
! style="" |Description
|-
| style="" |Decision Matrix
| style="" |pro
| style="" |Make an informed decision by comparing your options
|-
| style="" |Event
| style="" |pro
| style="" |Plan an event from beginning to end
|-
| style="" |Guideline
| style="" |pro
| style="" |Create a code of conduct or other guideline
|-
| style="" |How-to Article
| style="" |free, pro
| style="" |Step-by-step instructions for completing a task
|-
| style="" |Management Meeting Minutes
| style="" |pro
| style="" |Create minutes for a regular management meeting
|-
| style="" |Meeting Agenda
| style="" |free
| style="" |Create a generic meeting agenda with minutes
|-
| style="" |Request for Comments
| style="" |pro
| style="" |Ask for feedback about an important decision that needs to be made
|-
| style="" |Status Report
| style="" |pro
| style="" |Stakeholder über den derzeitigen Stand eines Projekts informieren
|-
| style="" |To-do List
| style="" |free, pro
| style="" |Track and update your to-dos
|}

==Creating a page template==
Administrators can create new page templates, as well as edit and remove existing ones in the ''Page templates'' manager, located under ''Global actions''.
[[File:Manual:Extension BlueSpicePageTemplates 1743087498464.png|center|thumb|650x650px|Page template manager]]
[[File:Manual:Extension BlueSpicePageTemplates 1743087570912.png|center|thumb|650x650px|Page templates administration]]
{{Messagebox|boxtype=note|icon=|Note text=Every page template depends on an actual page in the namespace Template. This template must exist before creating a page template.|bgcolor=}}
When a page template is selected, it can be edited by clicking the "wrench" icon or deleted by clicking the "X" icon.

New page templates can be added via the "Plus" button above the templates list.

When creating or editing a page template, '''all fields are required''':

*'''Name''' - the name of the page template
*'''Description''' - a short description of the page template
*'''Tags-''' allows the grouping of similar templates. (If no classification is desired, you can enter ''Untagged'' as a value here, for example).
*'''Namespace''' - a list of the namespace where the template is active. If the template should be available on all pages, select ''(all)'' from the list.
*'''Template''' - page in the ''Template'' namespace from which to pull the content. '''Important!''' The namespace prefix <code>Template:</code> must be explicitly provided in the field.

[[File:Manual:Extension BlueSpicePageTemplates 1743087729166.png|center|thumb|400x400px|Editing a page template]]

== Deleting page templates ==
Page templates can be deleted individually or in groups using the trash can icon.

==Applying a page template==
'''(1) Blank page:''' When creating a new page, the page templates are displayed for selection. A blank page can be created by default. This option can be deactivated in the [[Manual:Extension/BlueSpicePageTemplates#Configuration|configuration manager.]]

'''(2) Filter field:''' The templates can be filtered here. This field is independent of the T''ags/Namespaces'' toggles.

'''(3) Tags/namespaces toggle:''' Here you can switch between tag-based and namespace-based sorting.

'''(4) Sort title:''' The sort titles show the grouping by tags or by namespaces, depending on the toggle setting.

'''(5) Assignment to tag/namespace:''' Depending on the setting of the toggle, the tags (when sorted by namespaces) or namespaces (when sorted by tags) are displayed here as additional possible filter criteria.

[[File:Manual:seitenvorlagenauswahl-en.png|alt=Screenshot of the page templates selection screen|center|thumb|750x750px|Applying a page template]]

== Namespace manager ==
The PageTemplates option for a namespace must be activated in the [[Manual:Extension/BlueSpiceNamespaceManager|Namespace manager]] so that the associated templates are automatically displayed when a new page is created in that namespace (e.g., if the "+" button is used to create the page).

==Configuration==

In the [[Manual:Extension/BlueSpiceConfigManager#BlueSpicePageTemplates|Config manager]], you can change the following settings:
{{#dpl:|title=Manual:Extension/BlueSpiceConfigManager|include=#BlueSpicePageTemplates}}

[[de:Handbuch:Erweiterung/BlueSpicePageTemplates]]

[[Category:Organization]]

Manual:Extension/BlueSpicePrivacy/Administration

2025-06-20T13:03:24Z

Lhuyghe:

==Terms of use==

===Changing the link targets===
The link target of the terms of use and can be changed by administrators on the related page in the MediaWiki-namespace if necessary.
[[File:Manual:Extension BlueSpicePrivacy Administration 1743425022229.png|center|thumb|Terms of service]]
{| class="wikitable" style="width:100%;"
! style="background-color:rgb(234, 236, 240);text-align:center;box-sizing:border-box;border:1px solid rgb(162, 169, 177);padding:0.8em 0.4em;" class="" |'''Link'''
! style="background-color:rgb(234, 236, 240);text-align:center;box-sizing:border-box;border:1px solid rgb(162, 169, 177);padding:0.8em 0.4em;" class="" |Standard link label
(defined in)
! style=""|Standard target page
(defined in)
|-
| style="" |'''Privacy policy'''
| style="" | Privacy policy
(MediaWiki:Privacy)
| style="" | Project:Privacy policy
(MediaWiki:Privacypage)
|-
| style="" |'''Disclaimers'''
| style="" |Disclaimers
(MediaWiki:Disclaimers)
| style="" |Project:General disclaimer
(MediaWiki:Disclaimerspage)
|}

== Account deletion or anonymization ==

=== Request to administrators ===
When a request for anonymization or account deletion is made, users in the sysop group will receive an email notification.

They can then access the ''Privacy'' page located in ''Global actions > Administration'' or by navigating to <code>Special:Privacy_Administration</code>.

This pages lists the submitted requests. Administrators can review and approve or deny them.

* Grant request (click on <code>Approve</code>)
* Reject request (click on <code>Deny</code>)
[[File:Manual:Extension BlueSpicePrivacy Administration 1743425205731.png|center|thumb|600x600px|Review privacy request]]
In addition, administrators can see the status of the''Privacy policy consent'' for every user on the wiki on this page.

=== Direct action by users ===
The wiki can be configured sothat users can perform these actions immediately without approval from an administrator first (not possible in BlueSpice cloud). Requesting actions applies to:

* anonymization
* account deletion

Immediate action can be configured as $<code>bsgPrivacyEnableRequests = false;</code> be activated in ''LocalSettings.php.''

== Configuration settings ==
The following settings can be made in the configuration management:
{{#dpl:title=Manual:Extension/BlueSpiceConfigManager|include=#BlueSpicePrivacy}}

[[de:Handbuch:Erweiterung/BlueSpicePrivacy/Verwaltung]]
[[en:{{FULLPAGENAME}}]]

Manual:Extension/BlueSpicePrivacy/Administration

2025-06-20T13:01:26Z

Lhuyghe:

==Terms of use==

===Changing the link targets===
The link target of the terms of use and can be changed by administrators on the related page in the MediaWiki-namespace if necessary.
[[File:Manual:Extension BlueSpicePrivacy Administration 1743425022229.png|center|thumb|Terms of service]]
{| class="wikitable" style="width:100%;"
! style="background-color:rgb(234, 236, 240);text-align:center;box-sizing:border-box;border:1px solid rgb(162, 169, 177);padding:0.8em 0.4em;" class="" |'''Link'''
! style="background-color:rgb(234, 236, 240);text-align:center;box-sizing:border-box;border:1px solid rgb(162, 169, 177);padding:0.8em 0.4em;" class="" |Standard link label
(defined in)
! style=""|Standard target page
(defined in)
|-
| style="" |'''Privacy policy'''
| style="" | Privacy policy
(MediaWiki:Privacy)
| style="" | Project:Privacy policy
(MediaWiki:Privacypage)
|-
| style="" |'''Disclaimers'''
| style="" |Disclaimers
(MediaWiki:Disclaimers)
| style="" |Project:General disclaimer
(MediaWiki:Disclaimerspage)
|}

== Account deletion or anonymization ==

=== Request to administrators ===
When a request for anonymization or account deletion is made, users in the sysop group will receive an email notification.

They can then access the ''Privacy'' page located in ''Global actions > Administration'' or by navigating to <code>Special:Privacy_Administration</code>.

This pages lists the submitted requests. Administrators can review and approve or deny them.

* Grant request (click on <code>Approve</code>)
* Reject request (click on <code>Deny</code>)
[[File:Manual:Extension BlueSpicePrivacy Administration 1743425205731.png|center|thumb|600x600px|Review privacy request]]
In addition, administrators can see the status of the''Privacy policy consent'' for every user on the wiki on this page.

=== Direct action by users ===
The wiki can be configured sothat users can perform these actions immediately without approval from an administrator first (not possible in BlueSpice cloud). Requesting actions applies to:

* anonymization
* account deletion

Immediate action can be configured as $<code>bsgPrivacyEnableRequests = false;</code> be activated in ''LocalSettings.php.''

[[de:Handbuch:Erweiterung/BlueSpicePrivacy/Verwaltung]]
[[en:{{FULLPAGENAME}}]]

Manual:Extension/BlueSpiceCategoryManager

2025-06-20T12:53:03Z

Lhuyghe:

<bs:bookshelf src="Book:Admin manual" />
{{DISPLAYTITLE:Category manager}}

The category manager makes it easier to create and manage a hierarchical category system in the wiki.

==Where can I find the category manager?==
The menu item ''Global actions > Editing > Categories'' loads the page ''Special:Category manager''.
[[File:Manual:Category manager-link.png|thumb|650x650px|Link to the category manager|alt=Link to the category manager|center]]
==Create a category==

'''To create a category:'''

#'''Click''' <code>+ Create category</code>.
#'''Enter''' the desired category name.
#'''Click''' ''Done.''[[File:Manual:Category manager-create.png|alt=Create a category|center|thumb|650x650px|Create a category]]
==Actions==
The following actions are available for a category:

* '''Edit: The category is also renamed on all pages that contain this category. This creates a new version of the affected pages.'''
* '''View category page:''' The category page opnes in a new browser tab. If this category is a "wanted category" (i.e., a category that is already used on a page but has not yet been created in the wiki), the page can then be created.
* '''Delete :''' The category page is deleted. The category is also deleted from all pages that contain this category. This creates a new version of the affected pages.

[[File:Manual:Category_manager-actions.png|alt=Actions icons for a category|center|thumb|181x181px|Actions]]

==Create a subcategory==

=== Drag-and-drop ===
The subcategory structure can be changed by dragging and dropping categories in the list with the mouse directly on top of another category (rather than between two categories). To move a subcategory outside the parent, wait for a dotted line to appear.

=== Manual links ===
Alternatively, you can go directly to a category page and assign a category to it. For example, if you add the category 1-Wiki to the category Department, the category Department becomes a subcategory of the category 1-Wiki.

== Import category tree ==

=== Create Excel file ===
If you want to create a larger category tree, this can also be imported via a spreadsheet file (xlsx). To do this, you need an Excel spreadsheet containing the columns ‘Title’ and ‘Free text’.

For example, if you want to create a <code>Marketing</code> category with the parent category <code>Department</code>, enter the page name for the new category in column 1: <code>Category:Marketing</code> and the parent category in double brackets in the ‘Free text’ column: (The free text is transferred to the page content of the newly created page).
{| class="wikitable"
|+''Example of a Excel spreadsheet''
! style="" |Titel
! style="" |Free text
|-
| style="" |Category:Marketing
| style="" |<code><nowiki>[[Category:Department]]</nowiki></code>
|-
| style="" |Category:Finance
| style="" |<code><nowiki>[[Category:Department]]</nowiki></code>
|}

=== Import Excel file ===
The Excel file can now be imported into the wiki via the special page ''‘Import spreadsheet’''.

This creates the category pages. The import page shows the following status. Unfortunately, the completion of the import is not displayed. It may take several minutes for the categories to be displayed in the category management.
{{Textbox|boxtype=important|header=Important:|text=If existing category pages are changed, the category page is temporarily blocked for further editing until the database has completed the necessary changes. In this case, check the category hierarchy again after 10 minutes at the latest. The new category structure should then be displayed correctly.|icon=yes}}
{{Box Links-en|Topic1=[[Manual:Extension/BlueSpiceCategoryCheck|Category Check]]}} 

{{Translation}}
[[Category:Organization]]

Manual:Extension/BlueSpiceCategoryManager

2025-06-20T12:52:31Z

Lhuyghe:

<bs:bookshelf src="Book:Admin manual" />
{{DISPLAYTITLE:Category manager}}

The category manager makes it easier to create and manage a hierarchical category system in the wiki.

==Where can I find the category manager?==
The menu item ''Global actions > Editing > Categories'' loads the page ''Special:Category manager''.
[[File:Manual:Category manager-link.png|thumb|650x650px|Link to the category manager|alt=Link to the category manager|center]]
==Create a category==

'''To create a category:'''

#'''Click''' <code>+ Create category</code>.
#'''Enter''' the desired category name.
#'''Click''' ''Done.''[[File:Manual:Category manager-create.png|alt=Create a category|center|thumb|650x650px|Create a category]]
==Actions==
The following actions are available for a category:

* '''Edit: The category is also renamed on all pages that contain this category. This creates a new version of the affected pages.'''
* '''View category page:''' The category page opnes in a new browser tab. If this category is a "wanted category" (i.e., a category that is already used on a page but has not yet been created in the wiki), the page can then be created.
* '''Delete :''' The category page is deleted. The category is also deleted from all pages that contain this category. This creates a new version of the affected pages.

[[File:Manual:Category_manager-actions.png|alt=Actions icons for a category|center|thumb|181x181px|Actions]]

==Create a subcategory==

=== Drag-and-drop ===
The subcategory structure can be changed by dragging and dropping categories in the list with the mouse directly on top of another category (rather than between two categories). To move a subcategory outside the parent, wait for a dotted line to appear.

=== Manual links ===
Alternatively, you can go directly to a category page and assign a category to it. For example, if you add the category 1-Wiki to the category Department, the category Department becomes a subcategory of the category 1-Wiki.

== Import category tree ==

=== Create Excel file ===
If you want to create a larger category tree, this can also be imported via a spreadsheet file (xlsx). To do this, you need an Excel spreadsheet containing the columns ‘Title’ and ‘Free text’.

For example, if you want to create a <code>Marketing</code> category with the parent category <code>Department</code>, enter the page name for the new category in column 1: <code>Category:Marketing</code> and the parent category in double brackets in the ‘Free text’ column: (The free text is transferred to the page content of the newly created page).
{| class="wikitable"
|+''Example of a Excel spreadsheet''
! style="" |Titel
! style="" |Free text
|-
| style="" |Category:Marketing
| style="" |<code><nowiki>[[Category:Department]]</nowiki></code>
|-
| style="" |Category:Finance
| style="" |<code><nowiki>[[Category:Department]]</nowiki></code>
|}

=== Import Excel file ===
The Excel file can now be imported into the wiki via the special page ''‘Import spreadsheet’''.

This creates the category pages. The import page shows the following status. Unfortunately, the completion of the import is not displayed. It may take several minutes for the categories to be displayed in the category management.
{{Textbox|boxtype=important|header=Important:|text=If existing category pages are changed, the category page is temporarily blocked for further editing until the database has completed the necessary changes. In this case, check the category hierarchy again after 10 minutes at the latest. The new category structure should then be displayed correctly.|icon=yes}}
{{Box Links-en|Topic1=[[Manual:Extension/BlueSpiceCategoryCheck|Category Check]]|Topic2=[[Reference:BlueSpiceCategoryCheck]]}} 

{{Translation}}
[[Category:Organization]]

Manual:Extension/BlueSpiceCategoryManager

2025-06-20T12:50:22Z

Lhuyghe:

<bs:bookshelf src="Book:Admin manual" />
{{DISPLAYTITLE:Category manager}}

The category manager makes it easier to create and manage a hierarchical category system in the wiki.

==Where can I find the category manager?==
The menu item ''Global actions > Editing > Categories'' loads the page ''Special:Category manager''.
[[File:Manual:Category manager-link.png|thumb|650x650px|Link to the category manager|alt=Link to the category manager|center]]
==Create a category==

'''To create a category:'''

#'''Click''' <code>+ Create category</code>.
#'''Enter''' the desired category name.
#'''Click''' ''Done.''[[File:Manual:Category manager-create.png|alt=Create a category|center|thumb|650x650px|Create a category]]
==Actions==
The following actions are available for a category:

* '''Edit: The category is also renamed on all pages that contain this category. This creates a new version of the affected pages.'''
* '''View category page:''' The category page opnes in a new browser tab. If this category is a "wanted category" (i.e., a category that is already used on a page but has not yet been created in the wiki), the page can then be created.
* '''Delete :''' The category page is deleted. The category is also deleted from all pages that contain this category. This creates a new version of the affected pages.

[[File:Manual:Category_manager-actions.png|alt=Actions icons for a category|center|thumb|181x181px|Actions]]

==Create a subcategory==

=== Drag-and-drop ===
The subcategory structure can be changed by dragging and dropping categories in the list with the mouse directly on top of another category (rather than between two categories). To move a subcategory outside the parent, wait for a dotted line to appear.

=== Manual links ===
Alternatively, you can go directly to a category page and assign a category to it. For example, if you add the category 1-Wiki to the category Department, the category Department becomes a subcategory of the category 1-Wiki.

== Import category tree ==

=== Create Excel file ===
If you want to create a larger category tree, this can also be imported via a spreadsheet file (xlsx). To do this, you need an Excel spreadsheet containing the columns ‘Title’ and ‘Free text’.

For example, if you want to create a <code>Marketing</code> category with the parent category <code>Department</code>, enter the page name for the new category in column 1: <code>Category:Marketing</code> and the parent category in double brackets in the ‘Free text’ column: (The free text is transferred to the page content of the newly created page).
{| class="wikitable"
|+''Example of a Excel spreadsheet''
! style="" |Titel
! style="" |Free text
|-
| style="" |Category:Marketing
| style="" |<code><nowiki>[[Category:Department]]</nowiki></code>
|-
| style="" |Category:Finance
| style="" |<code><nowiki>[[Category:Department]]</nowiki></code>
|}

=== Import Excel file ===
The Excel file can now be imported into the wiki via the special page ''‘Import spreadsheet’''.

This creates the category pages. The import page shows the following status. Unfortunately, the completion of the import is not displayed. It may take several minutes for the categories to be displayed in the category management.
{{Textbox|boxtype=important|header=Important:|text=If existing category pages are changed, the category page is temporarily blocked for further editing until the database has completed the necessary changes. In this case, check the category hierarchy again after 10 minutes at the latest. The new category structure should then be displayed correctly.|icon=yes}}
{{Box Links-en|Thema1=[[Reference:BlueSpiceCategoryManager]]|Thema2=[[Reference:BlueSpiceCategoryCheck]]}} 

{{Translation}}
[[Category:Organization]]

Manual:Extension/BlueSpiceCategoryManager

2025-06-20T12:40:16Z

Lhuyghe:

File:Manual:Category manager-actions.png

2025-06-20T12:39:13Z

Lhuyghe: (username removed) (log details removed)

File:Manual:Category manager-create.png

2025-06-20T12:35:48Z

Lhuyghe: (username removed) (log details removed)

Category:BlueSpice cloud

2025-06-20T12:34:59Z

Lhuyghe: Changed categories.

[[Category:Edition]]

File:Manual:Category manager-link.png

2025-06-20T12:31:42Z

Lhuyghe: (username removed) (log details removed)