BlueSpice Wiki - User contributions [en]

SocialEntity:6933

2021-12-17T15:23:46Z

Bhofmann:

{
"wikipageid": 11412,
"namespace": 0,
"titletext": "Announcement/Log4Shell",
"description": "",
"parentid": 0,
"id": 6933,
"ownerid": 8,
"type": "wikipage",
"archived": false,
"tags": [
"Announcement/Log4Shell"
],
"resolved": false
}

Announcement/Log4Shell

2021-12-17T15:23:45Z

Bhofmann:

==Event==
Log4j vulnerability

*https://nvd.nist.gov/vuln/detail/CVE-2021-44228

*[https://www.bsi.bund.de/SharedDocs/Cybersicherheitswarnungen/DE/2021/2021-549032-10F2.pdf;jsessionid=95F784B3CFE46DE89B51FC06804C4AEA.internet081 BSI warning from 12/12/2021 (CVE-2021-44228)]

==Current vulnerability assessment in BlueSpice (overview)==

*BlueSpice free, pro, farm:
**[[#Detailed assessment|Current on-premise installations]] => '''not affected'''
**[[#Older versions of BlueSpice 3|Older on-premise installations]] => '''version of Elasticsearch could be vulnerable'''
**[[#Inspected components in the Docker image|The Docker version]] => '''not affected'''
*[[#BlueSpice Cloud|BlueSpice Cloud]] => '''not affected'''

This is true for instances that we have installed. '''Customers have to check their part of the installation''' (i.e., OS, additional packages, etc.)

==Detailed assessment==

===Current version===

*'''Elasticsearch''' => '''not vulnerable''' https://discuss.elastic.co/t/apache-log4j2-remote-code-execution-rce-vulnerability-cve-2021-44228-esa-2021-31/291476
*'''Java-Server'''
**Tomcat => explicit configuration of log4j is necessary. By default, log4j is not activated. We do not change this. => '''not vulnerable'''
**Jetty => explicit configuration of jetty is necessary. By default, log4j is not activated. We do not change this. => '''not vulnerable'''
*'''Java Webservices'''
**xhtmlrenderer => a log4j plugin exists, but is not used by our service => '''not vulnerable'''
**VisualDiff => uses daisydiff + others. Does not use log4j => '''not vulnerable'''
**LaTeX2png => uses the jlatexmath library. Does not use log4j => '''not vulnerable'''
*'''Draw.io''' reports that the appication is not affected: https://twitter.com/drawio/status/1470061320066277382 => '''not vulnerable'''

===Older versions of BlueSpice 3===

*'''Elasticsearch''' => '''not vulnerable''' https://discuss.elastic.co/t/apache-log4j2-remote-code-execution-rce-vulnerability-cve-2021-44228-esa-2021-31/291476
**'''Versions 6.8.9+ ('''released on 13th May 2020) => '''not vulnerable'''
**'''Version 6.4.0 - 6.8.8''': Update of Elasticsearch is recommended. => '''not vulnerable''' '''(updating the version during the next BlueSpice update is recommended)''' => '''vulnerable outside of BlueSpice'''
**'''Versions 6.3.x and below''': Update of Elasticsearch is recommended. => '''not vulnerable''' '''(updating the version during the next BlueSpice update is recommended)''' => '''vulnerable outside of BlueSpice'''

Independently of the Elasticsearch version in use, BlueSpice is not vulnerable due to the setup of Elasticsearch:

*'''No direct access:''' BlueSpice uses Elasticsearch as an internal service. We set up Elasticsearch in such a way that there cannot be any direct access. The only way to access Elasticsearch if you are not working directly on the server is through BlueSpice, which means there is a very controlled set of access vectors. These are search queries and content which is to be indexed.
*'''No logging of data:''' We use log level WARN on Elasticsearch, which means no data can find its way to the logs. So there is no way an attacker can add custom information to the logs.

No pass-through of user data: All communication between BlueSpice and Elasticsearch is done user-agnostic. There is no way Elasticsearch can see which user triggers the communication. The user-agent is restricted to the BlueSpice system user.

This is true even if you are running on an older, vulnerable version of Elasticsearch. So we see no urgent action required. Nonetheless, it is recommended to update your Elasticsearch to a non-vulnerable version with the next update of BlueSpice.

If you have changed the Elasticsearch setup to a different log level or loosened the restrictions on Elasticsearch access, you have to check the setup.

===BlueSpice 2===

*Solr uses log4j => '''vulnerable''' More information on Mitigation is here: https://solr.apache.org/security.html#apache-solr-affected-by-apache-log4j-cve-2021-44228

===Inspected components in the Docker image===
The list of Docker files in the activated packages has been inspected. => '''not vulnerable'''

*https://security-tracker.debian.org/tracker/CVE-2021-44228

===BlueSpice Cloud===

*Swarmpit => '''not affected'''
*Drone => '''not affected'''

 

==Related links==

*https://www.elastic.co/guide/en/elasticsearch/reference/current/deb.html
*https://access.redhat.com/security/vulnerabilities/RHSB-2021-009
*https://www.suse.com/c/suse-statement-on-log4j-log4shell-cve-2021-44228-vulnerability/

 
[[de:Meldung/Log4Shell]]
[[en:{{FULLPAGENAME}}]]

SocialEntity:6932

2021-12-17T15:23:45Z

Bhofmann:

{
"wikipageid": 11412,
"revisionid": 28272,
"namespace": 0,
"titletext": "Announcement/Log4Shell",
"action": "edit",
"summary": "(No summary)",
"parentid": 0,
"id": 6932,
"ownerid": 8,
"type": "articlesave",
"archived": false,
"tags": [],
"resolved": false
}

SocialEntity:6919

2021-12-16T17:18:55Z

Bhofmann:

{
"wikipageid": 4398,
"revisionid": 28252,
"namespace": 3008,
"titletext": "Installation Guide/System Preparation/Windows/Elasticsearch",
"action": "edit",
"summary": "Undo revision 28250 by [[Special:Contributions/Bhofmann|Bhofmann]] ([[User talk:Bhofmann|talk]])",
"parentid": 0,
"id": 6919,
"ownerid": 8,
"type": "articlesave",
"archived": false,
"tags": [],
"resolved": false
}

Setup:Installation Guide/System Preparation/Windows/Elasticsearch

2021-12-16T17:18:54Z

Bhofmann: Undo revision 28250 by Bhofmann (talk)

{{DISPLAYTITLE:Elasticsearch on Windows}}
__TOC__

{{Template:Optional|text=Elasticsearch is a prerequisite for running Advanced Search. The steps listed here are optional and only required if you plan to use them in your BlueSpice installation.}}

{{Template:Hint|text=To run Elasticsearch, OpenJDK is required. If you have not installed it, [[Setup:Installation Guide/System Preparation/Windows/OpenJDK | install it now]].}}
==Download Elasticsearch==
BlueSpice is currently compatible with Elasticsearch 6.8.x as of version 6.8.21. Elasticsearch > 6.8.x is currently '''NOT supported!'''

The latest version can be found at [https://github.com/elastic/elasticsearch/releases this list]. This results in the following direct download link: <nowiki>https://artifacts.elastic.co/downloads/elasticsearch/elasticsearch-<version number>.zip</nowiki>. For example, https://artifacts.elastic.co/downloads/elasticsearch/elasticsearch-6.8.21.zip.

Follow the download instructions of your browser.

{{Template:Hint|text=Please note that the download on your Windows Server with Internet Explorer will only work if you have configured the Internet Explorer Advanced Security Settings in the Server Manager. Please refer to the technical documentation from Microsoft.}}
{{Template:Hint|text=In the following, Elasticsearch version 6.8.21 is used and is only an example of the latest version of the 6.8.x version, which you can download at the time of your installation.}}
==Unpacking Elasticsearch==
Unpack the contents of the ZIP archive (2) just downloaded into the folder "C:\bluespice\bin\elasticsearch-6.8.21" (1):
[[File:Setup:es0.png|center|400x400px|Elasticsearch Installation 01]]

==Installing the plugin ingest-attachment==
Change to the directory "C:\bluespice\bin\elasticsearch-6.8.21\bin" (1) and right-click on a free area of the Explorer window with the Shift key pressed. Then click "Open Windows Powershell Here" (2):
[[File:Setup:es6.png|center|400x400px|Elasticsearch Installation 02]]
Execute the command "elasticsearch-plugin.bat install ingest-attachment" (1) and after downloading the plugin, confirm the installation request with "y" (2):
[[File:Setup:es1.png|center|400x400px|Elasticsearch Installation 03]]
{{Template:Hint|text=If your server does not have an active internet connection, then [https://artifacts.elastic.co/downloads/elasticsearch-plugins/ingest-attachment/ingest-attachment-6.8.21.zip download the plug-in ingest-attachment as zip archive] and install it, as [https://www.elastic.co/guide/en/elasticsearch/plugins/current/plugin-management-custom-url.html documented directly by the manufacturer].}}
==Installing the Elasticsearch service==
Next, run the elasticsearch-service.bat install command and wait for the process to complete:
[[File:Setup:es2.png|center|400x400px|Elasticsearch Installation 07]]

==Configuring and starting the Elasticsearch service==
Press the key combination Windows+R.

In the following dialog box, enter "services.msc" (1) und confirm with "OK" (2):

[[File:Setup:Elastic_Install_04.png|center|400px|Elasticsearch Installation 04]]

Search for the service "Elasticsearch 6.8.21" and open it with a double-click:
[[File:Setup:es3.png|center|400x400px|Elasticsearch Installation 05]]
Select the startup type "Automatic" (1) and start the service (2). After the service is started, close the window with "OK" (3):
[[File:Setup:es4.png|center|459x459px|Elasticsearch Installation 06]]

==Next step==
If you have completed all steps successfully, you can delete the previously downloaded file "elasticsearch-6.8.21.zip" from your hard disk and continue to the next step "[[Setup: Installation Guide/System Preparation/Windows/Git |Git]]".

[[en:{{FULLPAGENAME}}]]
[[de:Setup:Installationsanleitung/Systemvorbereitung/Windows/Elasticsearch]]

SocialEntity:6918

2021-12-16T17:15:26Z

Bhofmann:

{
"wikipageid": 4398,
"revisionid": 28250,
"namespace": 3008,
"titletext": "Installation Guide/System Preparation/Windows/Elasticsearch",
"action": "edit",
"summary": "(No summary)",
"parentid": 0,
"id": 6918,
"ownerid": 8,
"type": "articlesave",
"archived": false,
"tags": [],
"resolved": false
}

Setup:Installation Guide/System Preparation/Windows/Elasticsearch

2021-12-16T17:15:25Z

Bhofmann:

{{DISPLAYTITLE:Elasticsearch on Windows}}
__TOC__

{{Template:Optional|text=Elasticsearch is a prerequisite for running Advanced Search. The steps listed here are optional and only required if you plan to use them in your BlueSpice installation.}}

{{Template:Hint|text=To run Elasticsearch, OpenJDK is required. If you have not installed it, [[Setup:Installation Guide/System Preparation/Windows/OpenJDK | install it now]].}}
==Download Elasticsearch==
BlueSpice is currently compatible with Elasticsearch 6.8.x as of version 6.8.21. Elasticsearch > 6.8.x is currently '''NOT supported!'''

The latest version can be found at [https://github.com/elastic/elasticsearch/releases this list]. This results in the following direct download link: <nowiki>https://artifacts.elastic.co/downloads/elasticsearch/elasticsearch-<version number>.zip</nowiki>. For example, https://artifacts.elastic.co/downloads/elasticsearch/elasticsearch-6.8.21.zip.

Follow the download instructions of your browser.

{{Template:Hint|text=Please note that the download on your Windows Server with Internet Explorer will only work if you have configured the Internet Explorer Advanced Security Settings in the Server Manager. Please refer to the technical documentation from Microsoft.}}
{{Template:Hint|text=In the following, Elasticsearch version 6.8.21 is used and is only an example of the latest version of the 6.8.x version, which you can download at the time of your installation.}}
==Unpacking Elasticsearch==
Unpack the contents of the ZIP archive (2) just downloaded into the folder "C:\bluespice\bin\elasticsearch-6.8.21" (1):
[[Datei:Setup:Elasticsearch (1).png|zentriert|400x400px|Elasticsearch Installation 01]]

==Installing the plugin ingest-attachment==
Change to the directory "C:\bluespice\bin\elasticsearch-6.8.21\bin" (1) and right-click on a free area of the Explorer window with the Shift key pressed. Then click "Open Windows Powershell Here" (2):
[[File:Setup:es6.png|center|400x400px|Elasticsearch Installation 02]]
Execute the command "elasticsearch-plugin.bat install ingest-attachment" (1) and after downloading the plugin, confirm the installation request with "y" (2):
[[File:Setup:es1.png|center|400x400px|Elasticsearch Installation 03]]
{{Template:Hint|text=If your server does not have an active internet connection, then [https://artifacts.elastic.co/downloads/elasticsearch-plugins/ingest-attachment/ingest-attachment-6.8.21.zip download the plug-in ingest-attachment as zip archive] and install it, as [https://www.elastic.co/guide/en/elasticsearch/plugins/current/plugin-management-custom-url.html documented directly by the manufacturer].}}
==Installing the Elasticsearch service==
Next, run the elasticsearch-service.bat install command and wait for the process to complete:
[[File:Setup:es2.png|center|400x400px|Elasticsearch Installation 07]]

==Configuring and starting the Elasticsearch service==
Press the key combination Windows+R.

In the following dialog box, enter "services.msc" (1) und confirm with "OK" (2):

[[File:Setup:Elastic_Install_04.png|center|400px|Elasticsearch Installation 04]]

Search for the service "Elasticsearch 6.8.21" and open it with a double-click:
[[File:Setup:es3.png|center|400x400px|Elasticsearch Installation 05]]
Select the startup type "Automatic" (1) and start the service (2). After the service is started, close the window with "OK" (3):
[[File:Setup:es4.png|center|459x459px|Elasticsearch Installation 06]]

==Next step==
If you have completed all steps successfully, you can delete the previously downloaded file "elasticsearch-6.8.21.zip" from your hard disk and continue to the next step "[[Setup: Installation Guide/System Preparation/Windows/Git |Git]]".

[[en:{{FULLPAGENAME}}]]
[[de:Setup:Installationsanleitung/Systemvorbereitung/Windows/Elasticsearch]]

SocialEntity:6917

2021-12-16T17:10:24Z

Bhofmann:

{
"wikipageid": 4398,
"revisionid": 28248,
"namespace": 3008,
"titletext": "Installation Guide/System Preparation/Windows/Elasticsearch",
"action": "edit",
"summary": "(No summary)",
"parentid": 0,
"id": 6917,
"ownerid": 8,
"type": "articlesave",
"archived": false,
"tags": [],
"resolved": false
}

Setup:Installation Guide/System Preparation/Windows/Elasticsearch

2021-12-16T17:10:23Z

Bhofmann:

Setup:Installation Guide/System Preparation/Windows/Elasticsearch

2021-12-16T17:09:38Z

Bhofmann:

{{DISPLAYTITLE:Elasticsearch on Windows}}
__TOC__

{{Template:Optional|text=Elasticsearch is a prerequisite for running Advanced Search. The steps listed here are optional and only required if you plan to use them in your BlueSpice installation.}}

{{Template:Hint|text=To run Elasticsearch, OpenJDK is required. If you have not installed it, [[Setup:Installation Guide/System Preparation/Windows/OpenJDK | install it now]].}}
==Download Elasticsearch==
BlueSpice is currently compatible with Elasticsearch 6.8.x as of version 6.8.21. Elasticsearch > 6.x is currently '''NOT supported!'''

The latest version can be found at [https://github.com/elastic/elasticsearch/releases this list]. This results in the following direct download link: <nowiki>https://artifacts.elastic.co/downloads/elasticsearch/elasticsearch-<version number>.zip</nowiki>. For example, https://artifacts.elastic.co/downloads/elasticsearch/elasticsearch-6.8.21.zip.

Follow the download instructions of your browser.

{{Template:Hint|text=Please note that the download on your Windows Server with Internet Explorer will only work if you have configured the Internet Explorer Advanced Security Settings in the Server Manager. Please refer to the technical documentation from Microsoft.}}
{{Template:Hint|text=In the following, Elasticsearch version 6.8.21 is used and is only an example of the latest version of the 6.8.x version, which you can download at the time of your installation.}}
==Unpacking Elasticsearch==
Unpack the contents of the ZIP archive (2) just downloaded into the folder "C:\bluespice\bin\elasticsearch-6.8.21" (1):
[[File:Setup:es0.png|center|400x400px|Elasticsearch Installation 01]]

==Installing the plugin ingest-attachment==
Change to the directory "C:\bluespice\bin\elasticsearch-6.8.21\bin" (1) and right-click on a free area of the Explorer window with the Shift key pressed. Then click "Open Windows Powershell Here" (2):
[[File:Setup:es6.png|center|400x400px|Elasticsearch Installation 02]]
Execute the command "elasticsearch-plugin.bat install ingest-attachment" (1) and after downloading the plugin, confirm the installation request with "y" (2):
[[File:Setup:es1.png|center|400x400px|Elasticsearch Installation 03]]
{{Template:Hint|text=If your server does not have an active internet connection, then [https://artifacts.elastic.co/downloads/elasticsearch-plugins/ingest-attachment/ingest-attachment-6.8.21.zip download the plug-in ingest-attachment as zip archive] and install it, as [https://www.elastic.co/guide/en/elasticsearch/plugins/current/plugin-management-custom-url.html documented directly by the manufacturer].}}
==Installing the Elasticsearch service==
Next, run the elasticsearch-service.bat install command and wait for the process to complete:
[[File:Setup:es2.png|center|400x400px|Elasticsearch Installation 07]]

==Configuring and starting the Elasticsearch service==
Press the key combination Windows+R.

In the following dialog box, enter "services.msc" (1) und confirm with "OK" (2):

[[File:Setup:Elastic_Install_04.png|center|400px|Elasticsearch Installation 04]]

Search for the service "Elasticsearch 6.8.21" and open it with a double-click:
[[File:Setup:es3.png|center|400x400px|Elasticsearch Installation 05]]
Select the startup type "Automatic" (1) and start the service (2). After the service is started, close the window with "OK" (3):
[[File:Setup:es4.png|center|459x459px|Elasticsearch Installation 06]]

==Next step==
If you have completed all steps successfully, you can delete the previously downloaded file "elasticsearch-6.8.21.zip" from your hard disk and continue to the next step "[[Setup: Installation Guide/System Preparation/Windows/Git |Git]]".

[[en:{{FULLPAGENAME}}]]
[[de:Setup:Installationsanleitung/Systemvorbereitung/Windows/Elasticsearch]]

SocialEntity:6916

2021-12-16T17:09:38Z

Bhofmann:

{
"wikipageid": 4398,
"revisionid": 28246,
"namespace": 3008,
"titletext": "Installation Guide/System Preparation/Windows/Elasticsearch",
"action": "edit",
"summary": "(No summary)",
"parentid": 0,
"id": 6916,
"ownerid": 8,
"type": "articlesave",
"archived": false,
"tags": [],
"resolved": false
}

Setup:Installation Guide/System Preparation/Windows/Elasticsearch

2021-12-16T17:06:28Z

Bhofmann:

{{DISPLAYTITLE:Elasticsearch on Windows}}
__TOC__

{{Template:Optional|text=Elasticsearch is a prerequisite for running Advanced Search. The steps listed here are optional and only required if you plan to use them in your BlueSpice installation.}}

{{Template:Hint|text=To run Elasticsearch, OpenJDK is required. If you have not installed it, [[Setup:Installation Guide/System Preparation/Windows/OpenJDK | install it now]].}}
==Download Elasticsearch==
BlueSpice is currently compatible with Elasticsearch 6.8.x as of version 6.8.21. Elasticsearch > 6.x is currently '''NOT supported!'''

The latest version can be found at [https://github.com/elastic/elasticsearch/releases this list]. This results in the following direct download link: <nowiki>https://artifacts.elastic.co/downloads/elasticsearch/elasticsearch-<version number>.zip</nowiki>. For example, https://artifacts.elastic.co/downloads/elasticsearch/elasticsearch-6.8.21.zip.

Follow the download instructions of your browser.

{{Template:Hint|text=Please note that the download on your Windows Server with Internet Explorer will only work if you have configured the Internet Explorer Advanced Security Settings in the Server Manager. Please refer to the technical documentation from Microsoft.}}
{{Template:Hint|text=In the following, Elasticsearch version 7.15.0 is used and is only an example of the latest version of the 7.x version, which you can download at the time of your installation.}}
==Unpacking Elasticsearch==
Unpack the contents of the ZIP archive (2) just downloaded into the folder "C:\bluespice\bin\elasticsearch-7.15.0" (1):
[[File:Setup:es0.png|center|400x400px|Elasticsearch Installation 01]]

==Installing the plugin ingest-attachment==
Change to the directory "C:\bluespice\bin\elasticsearch-7.15.0\bin" (1) and right-click on a free area of the Explorer window with the Shift key pressed. Then click "Open Windows Powershell Here" (2):
[[File:Setup:es6.png|center|400x400px|Elasticsearch Installation 02]]
Execute the command "elasticsearch-plugin.bat install ingest-attachment" (1) and after downloading the plugin, confirm the installation request with "y" (2):
[[File:Setup:es1.png|center|400x400px|Elasticsearch Installation 03]]
{{Template:Hint|text=If your server does not have an active internet connection, then [https://artifacts.elastic.co/downloads/elasticsearch-plugins/ingest-attachment/ingest-attachment-6.8.21.zip download the plug-in ingest-attachment as zip archive] and install it, as [https://www.elastic.co/guide/en/elasticsearch/plugins/current/plugin-management-custom-url.html documented directly by the manufacturer].}}
==Installing the Elasticsearch service==
Next, run the elasticsearch-service.bat install command and wait for the process to complete:
[[File:Setup:es2.png|center|400x400px|Elasticsearch Installation 07]]

==Configuring and starting the Elasticsearch service==
Press the key combination Windows+R.

In the following dialog box, enter "services.msc" (1) und confirm with "OK" (2):

[[File:Setup:Elastic_Install_04.png|center|400px|Elasticsearch Installation 04]]

Search for the service "Elasticsearch 6.8.21" and open it with a double-click:
[[File:Setup:es3.png|center|400x400px|Elasticsearch Installation 05]]
Select the startup type "Automatic" (1) and start the service (2). After the service is started, close the window with "OK" (3):
[[File:Setup:es4.png|center|459x459px|Elasticsearch Installation 06]]

==Next step==
If you have completed all steps successfully, you can delete the previously downloaded file "elasticsearch-7.15.0.zip" from your hard disk and continue to the next step "[[Setup: Installation Guide/System Preparation/Windows/Git |Git]]".

[[en:{{FULLPAGENAME}}]]
[[de:Setup:Installationsanleitung/Systemvorbereitung/Windows/Elasticsearch]]

SocialEntity:6915

2021-12-16T17:06:28Z

Bhofmann:

{
"wikipageid": 4398,
"revisionid": 28244,
"namespace": 3008,
"titletext": "Installation Guide/System Preparation/Windows/Elasticsearch",
"action": "edit",
"summary": "(No summary)",
"parentid": 0,
"id": 6915,
"ownerid": 8,
"type": "articlesave",
"archived": false,
"tags": [],
"resolved": false
}

SocialEntity:6914

2021-12-16T17:05:51Z

Bhofmann:

{
"wikipageid": 4398,
"revisionid": 28242,
"namespace": 3008,
"titletext": "Installation Guide/System Preparation/Windows/Elasticsearch",
"action": "edit",
"summary": "(No summary)",
"parentid": 0,
"id": 6914,
"ownerid": 8,
"type": "articlesave",
"archived": false,
"tags": [],
"resolved": false
}

Setup:Installation Guide/System Preparation/Windows/Elasticsearch

2021-12-16T17:05:50Z

Bhofmann:

{{DISPLAYTITLE:Elasticsearch on Windows}}
__TOC__

{{Template:Optional|text=Elasticsearch is a prerequisite for running Advanced Search. The steps listed here are optional and only required if you plan to use them in your BlueSpice installation.}}

{{Template:Hint|text=To run Elasticsearch, OpenJDK is required. If you have not installed it, [[Setup:Installation Guide/System Preparation/Windows/OpenJDK | install it now]].}}
==Download Elasticsearch==
BlueSpice is currently compatible with Elasticsearch 6.x as of version 6.8.21. Elasticsearch > 6.x is currently '''NOT supported!'''

The latest version can be found at [https://github.com/elastic/elasticsearch/releases this list]. This results in the following direct download link: <nowiki>https://artifacts.elastic.co/downloads/elasticsearch/elasticsearch-<version number>.zip</nowiki>. For example, https://artifacts.elastic.co/downloads/elasticsearch/elasticsearch-6.8.21.zip.

Follow the download instructions of your browser.

{{Template:Hint|text=Please note that the download on your Windows Server with Internet Explorer will only work if you have configured the Internet Explorer Advanced Security Settings in the Server Manager. Please refer to the technical documentation from Microsoft.}}
{{Template:Hint|text=In the following, Elasticsearch version 7.15.0 is used and is only an example of the latest version of the 7.x version, which you can download at the time of your installation.}}
==Unpacking Elasticsearch==
Unpack the contents of the ZIP archive (2) just downloaded into the folder "C:\bluespice\bin\elasticsearch-7.15.0" (1):
[[File:Setup:es0.png|center|400x400px|Elasticsearch Installation 01]]

==Installing the plugin ingest-attachment==
Change to the directory "C:\bluespice\bin\elasticsearch-7.15.0\bin" (1) and right-click on a free area of the Explorer window with the Shift key pressed. Then click "Open Windows Powershell Here" (2):
[[File:Setup:es6.png|center|400x400px|Elasticsearch Installation 02]]
Execute the command "elasticsearch-plugin.bat install ingest-attachment" (1) and after downloading the plugin, confirm the installation request with "y" (2):
[[File:Setup:es1.png|center|400x400px|Elasticsearch Installation 03]]
{{Template:Hint|text=If your server does not have an active internet connection, then [https://artifacts.elastic.co/downloads/elasticsearch-plugins/ingest-attachment/ingest-attachment-6.8.21.zip download the plug-in ingest-attachment as zip archive] and install it, as [https://www.elastic.co/guide/en/elasticsearch/plugins/current/plugin-management-custom-url.html documented directly by the manufacturer].}}
==Installing the Elasticsearch service==
Next, run the elasticsearch-service.bat install command and wait for the process to complete:
[[File:Setup:es2.png|center|400x400px|Elasticsearch Installation 07]]

==Configuring and starting the Elasticsearch service==
Press the key combination Windows+R.

In the following dialog box, enter "services.msc" (1) und confirm with "OK" (2):

[[File:Setup:Elastic_Install_04.png|center|400px|Elasticsearch Installation 04]]

Search for the service "Elasticsearch 6.8.21" and open it with a double-click:
[[File:Setup:es3.png|center|400x400px|Elasticsearch Installation 05]]
Select the startup type "Automatic" (1) and start the service (2). After the service is started, close the window with "OK" (3):
[[File:Setup:es4.png|center|459x459px|Elasticsearch Installation 06]]

==Next step==
If you have completed all steps successfully, you can delete the previously downloaded file "elasticsearch-7.15.0.zip" from your hard disk and continue to the next step "[[Setup: Installation Guide/System Preparation/Windows/Git |Git]]".

[[en:{{FULLPAGENAME}}]]
[[de:Setup:Installationsanleitung/Systemvorbereitung/Windows/Elasticsearch]]

Setup:Installation Guide/System Preparation/Linux/Memcached

2021-09-28T08:46:06Z

Bhofmann:

{{DISPLAYTITLE:Memcached on Linux}}
__TOC__

{{Template:Optional|text=Memcached is a cache server to improve the performance of your BlueSpice installation. It is not required for the actual operation of BlueSpice. The steps listed here are therefore optional.}}
==Installation==
Install Memcached with Aptitude:

<pre>apt-get update; \
apt-get -y install memcached; \
apt-get clean</pre>

==Configuration==
Open the file containing the memcached configuration (for example, /etc/memcached.conf on Debian / Ubuntu). Find the '' '-m' '' argument there and increase the available memory according to your server's capabilities:

<pre>-m 512</pre>
Save and close the file and restart memcached with <code>service memcached restart</code>.

==Next step==
If you have completed all steps successfully and want to install BlueSpice pro, proceed to the next step "[[Setup:Installation Guide/System Preparation/Linux/Texvc | Texvc]]". If you want to install BlueSpice free, you can now continue with [[Setup:Installation_Guide/BlueSpice_Installation| Installing BlueSpice]].

[[en:{{FULLPAGENAME}}]]
[[de:Setup:Installationsanleitung/Systemvorbereitung/Linux/Memcached]]

SocialEntity:6721

2021-09-28T08:46:06Z

Bhofmann:

{
"wikipageid": 4509,
"revisionid": 27799,
"namespace": 3008,
"titletext": "Installation Guide/System Preparation/Linux/Memcached",
"action": "edit",
"summary": "(No summary)",
"parentid": 0,
"id": 6721,
"ownerid": 8,
"type": "articlesave",
"archived": false,
"tags": [],
"resolved": false
}

SocialEntity:5703

2021-03-24T10:05:42Z

Bhofmann:

{
"wikipageid": 745,
"revisionid": 24980,
"namespace": 3008,
"titletext": "Installation Guide/Security Settings/File System Permissions",
"action": "edit",
"summary": "(No summary)",
"parentid": 0,
"id": 5703,
"ownerid": 8,
"type": "articlesave",
"archived": false,
"tags": [],
"resolved": false
}

Setup:Installation Guide/Security Settings/File System Permissions

2021-03-24T10:05:41Z

Bhofmann:

{{DISPLAYTITLE:File System Permissions}}
__TOC__

For trouble-free usage of your BlueSpice installation, the web server requires write permissions to several folders of the file system. However, it is recommended to keep the rights for all other files and folders to a minimum. This document shows you the relevant folders and the correct permissions setting.

==Tips for this Document==
* Please, read this manual completely and work through the single installation steps one after another.
* For editing the configuration files with a text editor, the files must be saved in UTF-8 coding without BOM (Byte Order Mark).
* The placeholder <code></code> stands for the path to your BlueSpice installation, e.g <code>C:\inetpub\wwwroot\bluespice</code> (Windows) or <code>/var/www/bluespice</code> (Linux).

==Affected Folders==
The folders, which require write permissions, are:

* <code><installpath-bluespice></code>/cache
* <code><installpath-bluespice></code>/images
* <code><installpath-bluespice></code>/extensions/BlueSpiceFoundation/config
* <code><installpath-bluespice></code>/extensions/BlueSpiceFoundation/data
* <code><installpath-bluespice></code>/extensions/Widgets/compiled_templates '''(only BlueSpice pro)'''

==Assignment of Permissions with Windows==
Assign "change" rights for this folder for the local user "Everyone". 

[[File:Setup:Setup_windows_permissions.jpg|center]]

==Assignment of Permissions with Linux==
Here you can assign rights much more strictly, which is also recommended. Transfer the directory <code><installpath-bluespice></code> recursively to the user root (CHMOD for Files 644, CHMOD for Directories 755) and after this, transfer the mentioned directory recursively to the user and the group, under which the Apache Web Server runs (Debian/Ubuntu e.g. "www-data").

In the following, we provide a bash script, which works through this tasks for you with only one command.

To do so, create the file /usr/local/bin/setWikiPerm and copy the following code into this file:

<pre>#!/bin/bash

WWW_USER="www-data"
WWW_GROUP="www-data"

WWW_HOME=`eval echo ~$WWW_USER`
WWW_CFG=$WWW_HOME/.config

if [ $# -eq 0 ]; then
echo "You must enter the path of your MediaWiki installation."
exit
elif [ ! -d $1 ]; then
echo "$1 does not exist or is no path."
exit
fi

if [ ! -f $1/LocalSettings.php ]; then
echo "$1 contains no Localsettings.php"
exit
fi

PATH=`echo "$1" | sed -e 's#/$##'`

/usr/bin/find $PATH -type d -exec /bin/chmod 755 {} \;
/usr/bin/find $PATH -type f -exec /bin/chmod 644 {} \;

/bin/chown -R root:root $PATH

pathes=(
"$PATH/cache" \
"$PATH/images" \
"$PATH/_sf_archive" \
"$PATH/_sf_instances" \
"$PATH/extensions/BlueSpiceFoundation/data" \
"$PATH/extensions/BlueSpiceFoundation/config" \
"$PATH/extensions/Widgets/compiled_templates" \
)

for i in "${pathes[@]}"; do
if [ -d $i ]; then
/bin/chown -R $WWW_USER:$WWW_GROUP $i
fi
done

if [ ! -d $WWW_CFG ]; then
/bin/mkdir $WWW_CFG
fi

/bin/chown -R $WWW_USER:$WWW_GROUP $WWW_CFG

/usr/bin/find $PATH/extensions -iname 'create_pygmentize_bundle' -exec /bin/chmod +x {} \;
/usr/bin/find $PATH/extensions -iname 'pygmentize' -exec /bin/chmod +x {} \;
/usr/bin/find $PATH/extensions -name 'lua' -type f -exec /bin/chmod 755 {} \;

</pre>

If needed, replace the content of the variables

WWW_USER="www-data"
WWW_GROUP="www-data"

with the approprate user and group of your distribution.

After this, assign CHMOD 755 to this file. Now you can run the script and let it do the complete permission setting automatically with the following command:

setWikiPerm <code><installpath-bluespice></code>

{{Hint
|text=Note that when the update.php is executed on the console, the rights can be partially discarded. For this reason, set the rights to "update.php" again.
}}

[[en:{{FULLPAGENAME}}]][[de:Setup:Installationsanleitung/Sicherheitseinstellungen/Dateisystemrechte]]

User:Bhofmann

2021-03-24T10:05:10Z

Bhofmann: create user page

Setup:Installation Guide/Advanced/Configuration Folder settings.d

2020-09-03T08:37:09Z

Bhofmann:

{{DISPLAYTITLE:For Advanced Users: Configuration Folder settings.d}}
__TOC__

==Tip for theDocument==

*Please, read this manual completely and work through the single installation steps one after another.
*For editing the configuration files with a text editor, the files must be saved in UTF-8 coding without BOM (Byte Order Mark).
*The placeholder <code><installpath-bluespice></code> stands for the path to your BlueSpice installation, e.g <code>C:\inetpub\wwwroot\bluespice</code> (Windows) or <code>/var/www/bluespice</code> (Linux).

[[File:Hint.jpg|left]] '''This document provides background information for advanced users. We recommend not to make any changes on BlueSpice, if you are not familiar with the following information. '''

==Explanation For the Folder settings.d==
Starting with BlueSpice version 2.27.1, all default settings as well as the modules of BlueSpice are outsourced. All configurations can now be found in separate files in the /settings.d folder.

The files in this folder integrate the standard MediaWiki extensions required for BlueSpice, perform recommended default configurations, and also integrate all BlueSpice-related extensions (free or pro).

The files in the /settings.d folder are automatically integrated in alphabetical order and are therefore prefixed with numbers. If you want to add additional configurations yourself, you can save your own files here. For this, it is recommended to use the prefix 001-. 

Additional configurations, which are not packed per default but can be used, can be found at [https://github.com/hallowelt/bluespice-tools/tree/master/default-configs/settings.d auf github.com].

==Update-safe changing of default configuration files==

If you want to change the files delivered by default in the settings.d folder, we strongly recommend that you choose the following method so as not to lose this configuration after an update:

*Create a copy of the respective configuration file with the extension <code>.local.php</code> - e.g. ''020-VisualEditor.local.php''
*Only edit this file

Files with this file extension are generally preferred in the loading process.

[[en:{{FULLPAGENAME}}]]
[[de:Setup:Installationsanleitung/Kompendium/Konfigurationsordner_settings.d]]

SocialEntity:4770

2020-09-03T08:37:09Z

Bhofmann:

{
"wikipageid": 771,
"revisionid": 22696,
"namespace": 3008,
"titletext": "Installation Guide/Advanced/Configuration Folder settings.d",
"action": "edit",
"summary": "\u29fcbs-socialactionsmw-autoeditsummaray\u29fd",
"parentid": 0,
"id": 4770,
"ownerid": 8,
"type": "articlesave",
"archived": false,
"tags": [],
"resolved": false
}

SocialEntity:4769

2020-09-03T08:35:29Z

Bhofmann:

{
"wikipageid": 771,
"namespace": 0,
"titletext": "Setup:Installation Guide/Advanced/Configuration Folder settings.d",
"description": "",
"parentid": 0,
"id": 4769,
"ownerid": 8,
"type": "wikipage",
"archived": false,
"tags": [
"Setup:Installation Guide/Advanced/Configuration Folder settings.d"
],
"resolved": false
}

Setup:Installation Guide/Advanced/Configuration Folder settings.d

2020-09-03T08:35:28Z

Bhofmann:

SocialEntity:4768

2020-09-03T08:35:28Z

Bhofmann:

{
"wikipageid": 771,
"revisionid": 22693,
"namespace": 3008,
"titletext": "Installation Guide/Advanced/Configuration Folder settings.d",
"action": "edit",
"summary": "\u29fcbs-socialactionsmw-autoeditsummaray\u29fd",
"parentid": 0,
"id": 4768,
"ownerid": 8,
"type": "articlesave",
"archived": false,
"tags": [],
"resolved": false
}

Setup:Installation Guide/Advanced/Performance Optimization/MySQL

2020-07-21T09:19:49Z

Bhofmann:

{{DISPLAYTITLE:Performance Optimization: MySQL (MariaDB)}}
Match MySQL or MariaDB directly to your memory and CPU cores. To do this, apply the following configuration in your my.ini:
<pre>[mysqld]

; with 16GB RAM
innodb_buffer_pool_size=4096M
tmp-table-size=1024M
max-heap-table-size=1024M
query_cache_size=1024M

; with 12 CPU cores
innodb-buffer-pool-instances=12
max_connections=12000

; Only use "127.0.0.1", not "localhost" when accessing MySQL
; Remember to also make these changes in the $wgDBserver variable in LocalSettings.php.
skip-name-resolve</pre>

[[en:{{FULLPAGENAME}}]][[de:Setup:Installationsanleitung/Kompendium/Performance-Optimierungen/MySQL]]

SocialEntity:4449

2020-07-21T09:19:49Z

Bhofmann:

{
"wikipageid": 4519,
"revisionid": 21859,
"namespace": 3008,
"titletext": "Installation Guide/Advanced/Performance Optimization/MySQL",
"action": "edit",
"summary": "\u29fcbs-socialactionsmw-autoeditsummaray\u29fd",
"parentid": 0,
"id": 4449,
"ownerid": 8,
"type": "articlesave",
"archived": false,
"tags": [],
"resolved": false
}

SocialEntity:3733

2020-01-31T08:56:19Z

Bhofmann:

{
"social-profile-title": null,
"social-profile-name": null,
"social-profile-email": null,
"social-profile-department": "",
"social-profile-function": "",
"social-profile-location": "",
"social-profile-phone": "",
"description": "",
"parentid": 0,
"id": 3733,
"ownerid": 42,
"type": "profile",
"archived": false,
"tags": [
"User:Mkartmann"
],
"resolved": false
}

Setup:Installation Guide/System Preparation/Linux/Parsoid

2019-12-09T12:33:07Z

Bhofmann:

{{DISPLAYTITLE:Installing Parsoid}}
__TOC__

{{Template:Optional|text=Parsoid is the rendering service for the Visual Editor. The steps listed here are optional and only required if you plan to use them in your BlueSpice installation.}}
== Installation ==
The installation from package sources of the distribution will be omitted. Parsoid is installed under /opt. Go there with the following command:

<pre>cd /opt</pre>

To download Parsoid, the software "git" must be installed(<code>apt install git</code>).
Start the download with:

<pre>git clone --depth 1 --branch v0.10.0 https://gerrit.wikimedia.org/r/p/mediawiki/services/parsoid parsoid</pre>

Install Parsoid with the following commands:

<pre>cd parsoid; \
npm install</pre>

==Create the configuration file==
In the BlueSpice codebase, you can find two files in the folder <code>extensions/BlueSpiceVisualEditorConnector/docs/parsoid</code>:
* config.yaml
* localsettings.js

Copy them to the folder <code>/opt/parsoid</code>.

Parsoid is already fully configured and should work in standard setup without further changes.

==Installing Parsoid and checking the configuration ==
To test the installation and the configuration, run the command <code>node bin/server.js </code> in the <code>/opt/parsoid </code> folder.

Parsoid should now start without an error message.

Quit Parsoid by pressing "Ctrl+C". Keep the command prompt open and go to the next step.

== Installing Parsoid as a service ==
To run Parsoid in the background in the future, you must additionally install pm2 via Node.js:

<pre>npm install -g pm2</pre>

Then start Parsoid via pm2:

<pre>pm2 start /opt/parsoid/bin/server.js</pre>

Now save the pm2 process list — this adds parsoid to the pm2 services:

<pre>pm2 save</pre>

Finally, add pm2 to the system startup:

<pre># Render startup-script for a specific platform, the [platform] could be one of:
# ubuntu|centos|redhat|gentoo|systemd|darwin|amazon
pm2 startup [platform]</pre>

==Next Step==
If you have completed all steps successfully, you can proceed to the next step "[[Setup: Installation Guide/System Preparation/Linux/Python | Python]]".

[[en:{{FULLPAGENAME}}]][[de:etup:Installationsanleitung/Systemvorbereitung/Linux/Parsoid]]

SocialEntity:3269

2019-12-09T12:33:07Z

Bhofmann:

{
"wikipageid": 4504,
"revisionid": 18810,
"namespace": 3008,
"titletext": "Installation Guide/System Preparation/Linux/Parsoid",
"action": "edit",
"summary": "\u29fcbs-socialactionsmw-autoeditsummaray\u29fd",
"parentid": 0,
"id": 3269,
"ownerid": 8,
"type": "articlesave",
"archived": false,
"tags": [],
"resolved": false
}

Setup:Installation Guide/System Preparation/Linux/Parsoid

2019-11-04T14:11:15Z

Bhofmann:

{{DISPLAYTITLE:Installing Parsoid}}
__TOC__

{{Template:Optional|text=Parsoid is the rendering service for the Visual Editor. The steps listed here are optional and only required if you plan to use them in your BlueSpice installation.}}
== Installation ==
The installation from package sources of the distribution will be omitted. Parsoid is installed under /opt. Go there with the following command:

<pre>cd /opt</pre>

To download Parsoid, the software "git" must be installed(<code>apt install git</code>).
Start the download with:

<pre>git clone --depth 1 --branch v0.10.0 https://gerrit.wikimedia.org/r/p/mediawiki/services/parsoid parsoid</pre>

Install Parsoid with the following commands:

<pre>cd parsoid; \
npm install</pre>

==Create the configuration file==
In the BlueSpice codebase, you can find two files in the folder <code>extensions/BlueSpiceVisualEditorConnector/docs/parsoid</code>:
* config.yaml
* localsettings.js

Copy them to the folder <code>/opt/parsoid</code>.

Parsoid is already fully configured and should work in standard setup without further changes.

==Installing Parsoid and checking the configuration ==
To test the installation and the configuration, run the command <code>node bin\server.js </code> in the <code>/opt/parsoid </code> folder.

Parsoid should now start without an error message.

Quit Parsoid by pressing "Ctrl+C". Keep the command prompt open and go to the next step.

== Installing Parsoid as a service ==
To run Parsoid in the background in the future, you must additionally install pm2 via Node.js:

<pre>npm install -g pm2</pre>

Then start Parsoid via pm2:

<pre>pm2 start /opt/parsoid/bin/server.js</pre>

Now save the pm2 process list — this adds parsoid to the pm2 services:

<pre>pm2 save</pre>

Finally, add pm2 to the system startup:

<pre># Render startup-script for a specific platform, the [platform] could be one of:
# ubuntu|centos|redhat|gentoo|systemd|darwin|amazon
pm2 startup [platform]</pre>

==Next Step==
If you have completed all steps successfully, you can proceed to the next step "[[Setup: Installation Guide/System Preparation/Linux/Python | Python]]".

[[en:{{PAGENAME}}]][[de:etup:Installationsanleitung/Systemvorbereitung/Linux/Parsoid]]

SocialEntity:2556

2019-11-04T14:11:15Z

Bhofmann:

{
"wikipageid": 4504,
"revisionid": 16229,
"namespace": 3008,
"titletext": "Installation Guide/System Preparation/Linux/Parsoid",
"action": "edit",
"summary": "\u29fcbs-socialactionsmw-autoeditsummaray\u29fd",
"parentid": 0,
"id": 2556,
"ownerid": 8,
"type": "articlesave",
"archived": false,
"tags": [],
"resolved": false
}

User:Bhofmann/Testseite

2019-01-18T16:07:55Z

Bhofmann:

Teeeeeeeeeest

<math>2 = \left(
\frac{\left(3-x\right) \times 2}{3-x}
\right)</math>

User:Bhofmann/Testseite

2019-01-18T16:07:29Z

Bhofmann: Created page with "Teeeeeeeeeest"

Teeeeeeeeeest

Setup:Installation Guide/Security Settings/File System Permissions

2019-01-17T09:03:54Z

Bhofmann:

{{DISPLAYTITLE:File System Permissions}}
__TOC__

For trouble-free usage of your BlueSpice installation, the web server requires write permissions to several folders of the file system. However, it is recommended to keep the rights for all other files and folders to a minimum. This document shows you the relevant folders and the correct permissions setting.

==Tips for this Document==
* Please, read this manual completely and work through the single installation steps one after another.
* For editing the configuration files with a text editor, the files must be saved in UTF-8 coding without BOM (Byte Order Mark).
* The placeholder <code></code> stands for the path to your BlueSpice installation, e.g <code>C:\inetpub\wwwroot\bluespice</code> (Windows) or <code>/var/www/bluespice</code> (Linux).

==Affected Folders==
The folders, which require write permissions, are:

* <code><installpath-bluespice></code>/cache
* <code><installpath-bluespice></code>/images
* <code><installpath-bluespice></code>/extensions/BlueSpiceFoundation/config
* <code><installpath-bluespice></code>/extensions/BlueSpiceFoundation/data
* <code><installpath-bluespice></code>/extensions/Widgets/compiled_templates '''(only BlueSpice pro)'''

==Assignment of Permissions with Windows==
Assign "change" rights for this folder for the local user "Everyone". 

[[File:Setup:Setup_windows_permissions.jpg|center]]

==Assignment of Permissions with Linux==
Here you can assign rights much more strictly, which is also recommended. Transfer the directory <code><installpath-bluespice></code> recursively to the user root (CHMOD for Files 644, CHMOD for Directories 755) and after this, transfer the mentioned directory recursively to the user and the group, under which the Apache Web Server runs (Debian/Ubuntu e.g. "www-data").

In the following, we provide a bash script, which works through this tasks for you with only one command.

To do so, create the file /usr/local/bin/setWikiPerm and copy the following code into this file:

<pre>#!/bin/bash

WWW_USER="www-data"
WWW_GROUP="www-data"

WWW_HOME=`eval echo ~$WWW_USER`
WWW_CFG=$WWW_HOME/.config

if [ $# -eq 0 ]; then
echo "You must enter the path of your MediaWiki installation."
exit
elif [ ! -d $1 ]; then
echo "$1 does not exist or is no path."
exit
fi

PATH=`echo "$1" | sed -e 's#/$##'`

/usr/bin/find $PATH -type d -exec /bin/chmod 755 {} \;
/usr/bin/find $PATH -type f -exec /bin/chmod 644 {} \;

/bin/chown -R root:root $PATH

pathes=(
"$PATH/cache" \
"$PATH/images" \
"$PATH/_sf_archive" \
"$PATH/_sf_instances" \
"$PATH/extensions/BlueSpiceFoundation/data" \
"$PATH/extensions/BlueSpiceFoundation/config" \
"$PATH/extensions/Widgets/compiled_templates" \
)

for i in "${pathes[@]}"; do
if [ -d $i ]; then
/bin/chown -R $WWW_USER:$WWW_GROUP $i
fi
done

if [ ! -d $WWW_CFG ]; then
/bin/mkdir $WWW_CFG
fi

/bin/chown -R $WWW_USER:$WWW_GROUP $WWW_CFG

/usr/bin/find $PATH/extensions -iname 'create_pygmentize_bundle' -exec /bin/chmod +x {} \;
/usr/bin/find $PATH/extensions -iname 'pygmentize' -exec /bin/chmod +x {} \;
/usr/bin/find $PATH/extensions -name 'lua' -type f -exec /bin/chmod 755 {} \;

</pre>

If needed, replace the content of the variables

WWW_USER="www-data"
WWW_GROUP="www-data"

with the approprate user and group of your distribution.

After this, assign CHMOD 755 to this file. Now you can run the script and let it do the complete permission setting automatically with the following command:

setWikiPerm <code><installpath-bluespice></code>

{{Hint
|text=Note that when the update.php is executed on the console, the rights can be partially discarded. For this reason, set the rights to "update.php" again.
}}

[[en:{{FULLPAGENAME}}]][[de:Setup:Installationsanleitung/Sicherheitseinstellungen/Dateisystemrechte]]

MediaWiki:Common.css

2019-01-11T07:06:54Z

Bhofmann: Created page with "/* CSS placed here will be applied to all skins */ h2 { border-bottom: 1px solid rgb(51, 51, 51); padding-bottom: 2px; } #toc h2 { border-bottom: 0; }"

/* CSS placed here will be applied to all skins */

h2 {
border-bottom: 1px solid rgb(51, 51, 51);
padding-bottom: 2px;
}

#toc h2 {
border-bottom: 0;
}

Setup:Installation Guide/With Installer

2018-12-21T13:43:55Z

Bhofmann:

{{DISPLAYTITLE:Installation Manual BlueSpice 3 With Installer}}
__TOC__

==Preface==
With BlueSpice 3, we offer the installation as a complete package with MediaWiki and BlueSpice.
This installation manual give you step-by-step instructions to install BlueSpice.

==Notes==
This document only describes the steps for installing the web application. For the installation of extended functions such as VisualEditor and ExtendedSearch, please refer to the corresponding documentation.

We will not go into details about your operating system installation here, but assume that you have already configured your system and stored the installation package in a Webroot of your choice, where you can access it via your browser. You can find more details in our detailed [[Setup:Installation Manual|installation manual]].

Further help on the operating system setup can be found in our [[Setup:Installation Manual/Advanced|compendium]].

==Installation step-by-step==

{{Hint
|text=If you also install the paid extension "BlueSpiceWikiFarm", make sure that the codebase is not located directly in the DocumentRoot of your web server or VirtualHost - it must be located in the /w subfolder!
}}

First use call the URL in your browser at which the web application can be accessed. Then perform the following steps:
{| class="wikitable"
|-
|[[File:bs3-install-01.png|300px|BlueSpice 3 Installation Step 1]]
||If you don't meet all necessary requirements for PHP yet, you won't be able to view this setup page yet. Please make the necessary corrections to your PHP installation first. Otherwise you are now on the page shown in the screenshot. Click on "set up the wiki" to start the installation.
|-
|[[File:Setup:bs3-install-02.png|300px|BlueSpice 3 Installation Step 2]]
||You are now in the language selection. "Your language" defines the language you will be guided through the installer, "Wiki language" the later language of your wiki.
|-
|[[File:Setup:bs3-install-03.png|300px|BlueSpice 3 Installation Step 3]]
||The next step will take you to the MediaWiki installation check. Please read this check carefully, as possible hints may not block the installation, but may lead to restrictions of the wiki functionality in practice. Make desired corrections to your system and reload the page in your browser before proceeding with the setup.
|-
|[[File:bs3-install-04.png|300px|BlueSpice 3 Installation Step 4]]
||The connection to the database is then configured.

Here you can either specify the root user of your MySQL server and in the following step have the installer create an additional user who only has access to the BlueSpice database. The database will also be created automatically if it does not yet exist. Alternatively, you can create a user and a database in advance and directly enter this information here. You can find information on the manual creation of users and databases in the [[mediawikiwiki:Manual:Installing_MediaWiki#MariaDB/MySQL|official Mediawiki documentation]].
|-
|[[File:Setup:bs3-install-05.png|300px|BlueSpice 3 Installation Step 5]]
||Depending on the procedure you followed in the previous step, you can now define an exclusive user for your BlueSpice database. If you have already created the user explicitly for the database in advance, leave the check mark at "Use the same database account as during the installation process".
|-
|[[File:Setup:bs3-install-06.png|300px|BlueSpice 3 Installation Step 6]]
||Enter the name for your wiki. This name is displayed in the title bar of your browser and in various other places such as in notification mails. Pay attention to the correct spelling, because this name can only be changed afterwards with certain effort and certain risks.

You can also enter the username, password and e-mail address of the first administrative user to be created by the wiki during setup.
|-
|[[File:Setup:bs3-install-07.png|300px|BlueSpice 3 Installation Step 7]]
||In this step, you specify the e-mail address to be used as the sender address for notification e-mails.
|-
|[[File:Setup:bs3-install-08.png|300px|BlueSpice 3 Installation Step 8]]
||You can skip this step directly with "Next".
|-
|[[File:Setup:bs3-install-09.png|300px|BlueSpice 3 Installation Step 9]]
||After the successful installation of BlueSpice you will receive this confirmation page, which you confirm with "Next".
|-
|[[File:Setup:bs3-install-10.png|300px|BlueSpice 3 Installation Step 10]]
||In the last step of the installation you will be asked to download the configuration file "LocalSettings.php" of your installation. Download it and place it in the root directory of your BlueSpice codebase.
|-
|[[File:Setup:bs3-install-11.png|300px|BlueSpice 3 Installation Step 11]]
||If you now access the BlueSpice URL you have chose, you will receive the completed installation and can now start using BlueSpice directly.
|}

[[en:{{FULLPAGENAME}}]]
[[de:Setup:Installationsanleitung/Installation_mit_Installer]]

Setup:Installation Guide/With Installer

2018-12-21T13:43:36Z

Bhofmann:

{{DISPLAYTITLE:Installation Manual BlueSpice 3 With Installer}}
__TOC__

==Preface==
With BlueSpice 3, we offer the installation as a complete package with MediaWiki and BlueSpice.
This installation manual give you step-by-step instructions to install BlueSpice.

==Notes==
This document only describes the steps for installing the web application. For the installation of extended functions such as VisualEditor and ExtendedSearch, please refer to the corresponding documentation.

We will not go into details about your operating system installation here, but assume that you have already configured your system and stored the installation package in a Webroot of your choice, where you can access it via your browser. You can find more details in our detailed [[Setup:Installation Manual|installation manual]].

Further help on the operating system setup can be found in our [[Setup:Installation Manual/Advanced|compendium]].

==Installation step-by-step==

{{Hint
|text=If you also install the paid extension "BlueSpiceWikiFarm", make sure that the codesbase is not located directly in the DocumentRoot of your web server or VirtualHost - it must be located in the /w subfolder!
}}

First use call the URL in your browser at which the web application can be accessed. Then perform the following steps:
{| class="wikitable"
|-
|[[File:bs3-install-01.png|300px|BlueSpice 3 Installation Step 1]]
||If you don't meet all necessary requirements for PHP yet, you won't be able to view this setup page yet. Please make the necessary corrections to your PHP installation first. Otherwise you are now on the page shown in the screenshot. Click on "set up the wiki" to start the installation.
|-
|[[File:Setup:bs3-install-02.png|300px|BlueSpice 3 Installation Step 2]]
||You are now in the language selection. "Your language" defines the language you will be guided through the installer, "Wiki language" the later language of your wiki.
|-
|[[File:Setup:bs3-install-03.png|300px|BlueSpice 3 Installation Step 3]]
||The next step will take you to the MediaWiki installation check. Please read this check carefully, as possible hints may not block the installation, but may lead to restrictions of the wiki functionality in practice. Make desired corrections to your system and reload the page in your browser before proceeding with the setup.
|-
|[[File:bs3-install-04.png|300px|BlueSpice 3 Installation Step 4]]
||The connection to the database is then configured.

Here you can either specify the root user of your MySQL server and in the following step have the installer create an additional user who only has access to the BlueSpice database. The database will also be created automatically if it does not yet exist. Alternatively, you can create a user and a database in advance and directly enter this information here. You can find information on the manual creation of users and databases in the [[mediawikiwiki:Manual:Installing_MediaWiki#MariaDB/MySQL|official Mediawiki documentation]].
|-
|[[File:Setup:bs3-install-05.png|300px|BlueSpice 3 Installation Step 5]]
||Depending on the procedure you followed in the previous step, you can now define an exclusive user for your BlueSpice database. If you have already created the user explicitly for the database in advance, leave the check mark at "Use the same database account as during the installation process".
|-
|[[File:Setup:bs3-install-06.png|300px|BlueSpice 3 Installation Step 6]]
||Enter the name for your wiki. This name is displayed in the title bar of your browser and in various other places such as in notification mails. Pay attention to the correct spelling, because this name can only be changed afterwards with certain effort and certain risks.

You can also enter the username, password and e-mail address of the first administrative user to be created by the wiki during setup.
|-
|[[File:Setup:bs3-install-07.png|300px|BlueSpice 3 Installation Step 7]]
||In this step, you specify the e-mail address to be used as the sender address for notification e-mails.
|-
|[[File:Setup:bs3-install-08.png|300px|BlueSpice 3 Installation Step 8]]
||You can skip this step directly with "Next".
|-
|[[File:Setup:bs3-install-09.png|300px|BlueSpice 3 Installation Step 9]]
||After the successful installation of BlueSpice you will receive this confirmation page, which you confirm with "Next".
|-
|[[File:Setup:bs3-install-10.png|300px|BlueSpice 3 Installation Step 10]]
||In the last step of the installation you will be asked to download the configuration file "LocalSettings.php" of your installation. Download it and place it in the root directory of your BlueSpice codebase.
|-
|[[File:Setup:bs3-install-11.png|300px|BlueSpice 3 Installation Step 11]]
||If you now access the BlueSpice URL you have chose, you will receive the completed installation and can now start using BlueSpice directly.
|}

[[en:{{FULLPAGENAME}}]]
[[de:Setup:Installationsanleitung/Installation_mit_Installer]]

Setup:Installation Guide/Security Settings/File System Permissions

2018-11-08T12:28:28Z

Bhofmann:

{{DISPLAYTITLE:File System Permissions}}
__TOC__

For trouble-free usage of your BlueSpice installation, the web server requires write permissions to several folders of the file system. However, it is recommended to keep the rights for all other files and folders to a minimum. This document shows you the relevant folders and the correct permissions setting.

==Tips for this Document==
* Please, read this manual completely and work through the single installation steps one after another.
* For editing the configuration files with a text editor, the files must be saved in UTF-8 coding without BOM (Byte Order Mark).
* The placeholder <code></code> stands for the path to your BlueSpice installation, e.g <code>C:\inetpub\wwwroot\bluespice</code> (Windows) or <code>/var/www/bluespice</code> (Linux).

==Affected Folders==
The folders, which require write permissions, are:

* <code><installpath-bluespice></code>/cache
* <code><installpath-bluespice></code>/images
* <code><installpath-bluespice></code>/extensions/BlueSpiceFoundation/config
* <code><installpath-bluespice></code>/extensions/BlueSpiceFoundation/data
* <code><installpath-bluespice></code>/extensions/Widgets/compiled_templates '''(only BlueSpice pro)'''

==Assignment of Permissions with Windows==
Assign "change" rights for this folder for the local user "Everyone". 

[[File:Setup:Setup_windows_permissions.jpg|center]]

==Assignment of Permissions with Linux==
Here you can assign rights much more strictly, which is also recommended. Transfer the directory <code><installpath-bluespice></code> recursively to the user root (CHMOD for Files 644, CHMOD for Directories 755) and after this, transfer the mentioned directory recursively to the user and the group, under which the Apache Web Server runs (Debian/Ubuntu e.g. "www-data").

In the following, we provide a bash script, which works through this tasks for you with only one command.

To do so, create the file /usr/local/bin/setWikiPerm and copy the following code into this file:

<pre>#!/bin/bash

WWW_USER="www-data"
WWW_GROUP="www-data"

WWW_HOME=`eval echo ~$WWW_USER`
WWW_CFG=$WWW_HOME/.config

if [ $# -eq 0 ]; then
echo "You must enter the path of your MediaWiki installation."
exit
elif [ ! -d $1 ]; then
echo "$1 does not exist or is no path."
exit
fi

PATH=`echo "$1" | sed -e 's#/$##'`

/usr/bin/find $PATH -type d -exec /bin/chmod 755 {} \;
/usr/bin/find $PATH -type f -exec /bin/chmod 644 {} \;

/bin/chown -R root:root $PATH

pathes=(
"$PATH/cache" \
"$PATH/images" \
"$PATH/_sf_instances" \
"$PATH/extensions/BlueSpiceFoundation/data" \
"$PATH/extensions/BlueSpiceFoundation/config" \
"$PATH/extensions/Widgets/compiled_templates" \
)

for i in "${pathes[@]}"; do
if [ -d $i ]; then
/bin/chown -R $WWW_USER:$WWW_GROUP $i
fi
done

if [ ! -d $WWW_CFG ]; then
/bin/mkdir $WWW_CFG
fi

/bin/chown -R $WWW_USER:$WWW_GROUP $WWW_CFG

/usr/bin/find $PATH/extensions -iname 'create_pygmentize_bundle' -exec /bin/chmod +x {} \;
/usr/bin/find $PATH/extensions -iname 'pygmentize' -exec /bin/chmod +x {} \;
/usr/bin/find $PATH/extensions -name 'lua' -type f -exec /bin/chmod 755 {} \;

</pre>

If needed, replace the content of the variables

WWW_USER="www-data"
WWW_GROUP="www-data"

with the approprate user and group of your distribution.

After this, assign CHMOD 755 to this file. Now you can run the script and let it do the complete permission setting automatically with the following command:

setWikiPerm <code><installpath-bluespice></code>

{{Hint
|text=Note that when the update.php is executed on the console, the rights can be partially discarded. For this reason, set the rights to "update.php" again.
}}

[[en:{{FULLPAGENAME}}]][[de:Setup:Installationsanleitung/Sicherheitseinstellungen/Dateisystemrechte]]

Archive:FormattingHelp

2018-08-06T14:00:06Z

Bhofmann: Text replacement - "help.bluespice.com" to "wiki.bluespice.com"

{{BSExtensionInfobox
|desc=description of the most important Wiki codes for beginners.
|status=stable
|developer=HalloWelt
|type=BlueSpice
|edition=BlueSpice free, BlueSpice pro
|active=Yes
|compatible=BlueSpice
|category=Editor
|docu=https://www.mediawiki.org/wiki/Extension:FormattingHelp
}}

__TOC__

==Description==

'''FormattingHelp''' gives the most important information on formatting as you type. It is, however, significantly shorter than the wiki quick reference. FormattingHelp is a MediaWiki extension.

==Usage / Features==

FormattingHelp shows a help area with the most important formatting rules for the wiki code in the [https://en.wiki.bluespice.com/wiki/VisualEditor BlueSpice VisualEditor.]

==Technical information==

===Configuration===
This extension offers no configurations.

===Rights (permissions)===
This extension does not require any special rights.

===Requirements===

FormatingHelp requires [[BlueSpiceFoundation]].

==User manual==

For detailed description and usage please visit our [[Manual:Extension/FormattingHelp|user manual]].

==Try free our BluseSpice==

[https://en.demo.bluespice.com/wiki/Main_Page BlueSpice Demo.]

[[de:Formatierungshilfen]][[en:{{FULLPAGENAME}}]][[Category:Extension]]

Legal:Terms of use

2018-08-06T14:00:06Z

Bhofmann: Text replacement - "help.bluespice.com" to "wiki.bluespice.com"

==Principles and definitions==
# The Hallo Welt! GmbH, P.O. Box 11 02 09, 93015 Regensburg, Germany, hereinafter referred to as "Hallo Welt", provides a helpdesk for the BlueSpice software on the Internet at http://wiki.bluespice.com These Terms of Use apply to every user of the platform.
# The Hallo Welt! GmbH ("Hallo Welt!") has initiated the helpdesk and will be moderating the platform until further notice.
# Anyone who creates or changes content for the helpdesk as an author and/or text editor is an "active user". Anyone who only reads such content or wishes to use it for other purposes is a "passive user" within the meaning of these Terms of Use. Active and passive users are hereinafter collectively referred to as "users".
# If you want to become an active user, you have to log in with a user name, a password and an e-mail address. The further requirements for registration are regulated further down in these terms of use.
# This website contains links to third-party websites ("external links"). According to the regulations of the TMG (Telemediengesetzes) these websites are subject to the area of responsibility of the respective responsible persons of the websites in the sense of §§ 7 ff TMG. Hallo Welt! has checked the external contents for possible legal violations when linking the external links for the first time. Hallo Welt! has not completely checked the information contained in the links for their correctness. Hallo Welt! has no influence on the current and future design and content of the linked pages. The setting of external links does not mean that Hallo Welt! adopts the contents behind the reference or link as its own and/or guarantees the correctness of the respective contents. A permanent control of the external links is not reasonable for Hallo Welt! without concrete indications of legal violations or content errors and is also not provided by law. However, if we become aware of any legal infringements, such external links will be deleted immediately. Hallo Welt! will also delete links immediately if it becomes known that links to pages with obviously incorrect information refer.
# Hallo Welt! reserves the right to change these terms of use at any time. The user will be informed of the currently valid version of the terms of use before each login. However, the user will not be informed individually. Every user is responsible for reading the terms of use before each use of the Helpdesk and for checking that they are up to date. Further use of the platform by logging in after a change to the terms of use is deemed to be the user's declaration of consent to the changed terms of use.

==Information and obligations for active users (authors and text editors)==
# Any user who creates or modifies content must allow all other users free use of such content as long as the original authors are named (with the first and last name of the author(s) and either the reproduction of a hyperlink or the URL to any website that is used) and the right to free use of such content is passed on.
# The user therefore agrees to place any content to which the user is the author under the "Creative Commons Attribution/Share-Alike License 3.0 (unported)" license.
# Commercial use of the contents by active users is permitted as long as these terms of use are observed.
# The user declares that he is either the author of the contents used by him, in particular the texts, or that he has duly acquired the rights to use them.
# In this respect, the user is responsible for the contents and contributions used by him and published in the helpdesk. Hallo Welt! is not obliged to check the legality of contents before publication or to regularly check its Internet pages for possible illegal contents. Illegal contents are those which offend against morality or general ethical sentiment or infringe intellectual, industrial and other property rights of third parties, in particular copyrights and trademark rights as well as general personal rights.
# After becoming aware of a concrete content and its illegality, Hallo Welt! is entitled to remove this content or to block access to it. Furthermore, Hallo Welt! is entitled to temporarily or permanently exclude the user who has posted the illegal content from using the platform. Claims of the user for the removal of a content or the blocking of access to the content and/or for the temporary or permanent blocking of the user himself are excluded.
# The user indemnifies Hallo Welt! from all claims of third parties due to the violation of their rights by illegal content posted by the user. The user has hello world! in particular all damages to compensate the hello world! arising from the fact that third take hello world! because of the violation of their rights.

==Information and obligations for passive users==
# Use of the contents by passive users is permitted as long as these terms of use are observed.
# For the further use of the contents of the helpdesk the following conditions must be observed:
#* the authors (with their first and last names and either a hyperlink or the URL to each website used), and
#* a distribution of these terms of use, preferably with reference to a hyperlink to wiki.bluespice.com
#* Indication of changes and/or extensions to the existing work in an appropriate manner.

==Rights and duties of Hallo Welt!==
# Hallo Welt! makes the Helpdesk available to the general public free of charge.
# The user has no legal claim to permanent use of the platform. In particular, Hallo Welt! is not obliged to ensure the availability or accessibility of its services at all times. Hallo Welt! strives, however, to keep the platform up and running as smoothly as possible and to develop it further in accordance with the needs of the users. Hallo Welt! does not guarantee the availability and flawlessness of the platform.
# Hallo Welt! expressly reserves the right to change, restrict or completely discontinue the use of the platform at any time. The platform may be temporarily unavailable, in particular due to maintenance work, without the user having any claims against Hallo Welt! as a result.
# If the user violates these terms of use, Hallo Welt! is entitled to make use of his virtual domiciliary rights. This means that Hallo Welt! is entitled to exclude the user concerned from the platform or parts of the platform with the help of a block and to delete the contents used by him completely. Exclusion shall be at equitable discretion when assessing the individual case and in particular taking into account the seriousness of the infringement.
# The users of the platform are expressly informed that the distribution of inadmissible content may be subject to prosecution. Hallo Welt! is in these cases entitled and under certain circumstances obliged, if it becomes aware of illegal or unlawful contents or if it becomes aware of contents that offend common decency, to remove them immediately and to secure the respective contents for evidence purposes. In these cases Hallo Welt! is entitled to exclude the respective user from a future use of the platform.

==Other provisions==
# If any provision of these terms of use proves invalid, this shall not affect the validity of the remaining provisions. In place of the invalid provision, the parties shall agree on the validity of an appropriate provision which comes closest to what the parties to the contract have wanted but is permissible; the same shall apply to loopholes in the contract.
# Exclusive place of jurisdiction for all legal disputes arising from this contract is Regensburg, provided that the user is a merchant, a legal person under public law or a special fund under public law or provided that the user has no place of jurisdiction in the Federal Republic of Germany.
# Applicable law for all disputes arising from this user relationship is German law. Insofar as this refers to other legal regulations, this reference is excluded.
# In the event of inconsistencies between the English version and a translation into another language, the German version shall apply.

Regensburg, 22 May 2018

[[en:{{FULLPAGENAME}}]][[de:Legal:Nutzungsbedingungen]]

MediaWiki:Sidebar

2018-08-06T14:00:05Z

Bhofmann: Text replacement - "help.bluespice.com" to "wiki.bluespice.com"

* NAVIGATION
** mainpage|mainpage-description
** Special:AllPages|All articles
** recentchanges-url|recentchanges
* SETUP
** Setup:Portal|Setup Portal
* HOW TO...
** Search and find content|Search and find
** Create and structure content|Create and structure
** Manage and analyze content|Manage and analyze
** Quality assurance|Assure quality
** Communication and feedback|Communicate and give feedback
** Administration and safety|Administer and secure your wiki
** Personalization|Personalize
* PARTICIPATE
** Community|BlueSpice Community
** Special:WantedPages|Wanted pages

* ARCHIVE
** https://en.wiki.bluespice.com/index.php/Special:AllPages?from=&to=&namespace=3002 | Archived pages

Installation Manual/2.23.3/Update Manual/de

2018-08-06T14:00:05Z

Bhofmann: Text replacement - "help.bluespice.com" to "wiki.bluespice.com"

[https://de.wiki.bluespice.com/wiki/Archive:Update_Anleitung_2.23.3 Update_Anleitung_2.23.3]

Manual:Extension/Blog

2018-08-06T14:00:05Z

Bhofmann: Text replacement - "help.bluespice.com" to "wiki.bluespice.com"

<bs:bookshelf src="Book:User manual" />

__TOC__

==What is Blog?==

''' Blog''' extension allows creating news feeds on the wiki. These news feeds can be shown on any page, and users can be allowed to add their own news.

==Blog by default==

By default, there is a link to the Blog page in the TopMenuBar, which then opens the blog, a page containing a form for writing a new blog entry and a list of previous entries.

::: [[File:Blg1.jpg|500x304px]]

===Display Blog on any wiki page===

This blog news feed can be displayed on any wiki page by adding the blog tag to the page.

::: [[File:Blg2.jpg|500x309px]]

::: [[File:Blg3.jpg|500x308px]]

::: [[File:Blg4.jpg|500x309px]]

::: [[File:Blg5.jpg|500x306px]]

This also displays a "Create new blog entry"-form on the page, unless it is disabled to use blog tag [[Extensions/Blog#Blog tags|attributes]].

A blog entry consists of a title, revision information (date and author of first revision), the entry itself and possibly links for comments and a permalink. If a blog entry is too long, the link "continue reading" is displayed.

==Blog tags==

Blog extension offers several tags. These tags can be added to a page using InsertMagic functionality, or writing tag syntax directly to wiki code editor.

{| class="contenttable" border="0" cellspacing="0" cellpadding="0"
|-
!|'''Wiki tag'''
!|'''Description'''
|-
||<nowiki><bs:blog /></nowiki>
||Displays blog news feed on the page. It can be extended with multiple attributes. For more on attubutes read section "Blog tag attibutes" below.
|-
||<nowiki><bs:blog:more /></nowiki>
||This tag should be placed inside the content of a blog entry (pages in Blog namespace) to define at which point in text "continue reading" link should be placed. This will override default cut-off length of an entry.
|-
||<nowiki><bs:blog:time time="YYYYMMDDHHmm" /></nowiki>
||
This tag also should be placed inside the content of a blog entry. It allows manually defining timestamp for that particular blog entry. Timestamp is used in sorting and displaying blog entries.

|}

===Write an entry or create a new entry===

New blog entries can be created through the form on the page containing a blog tag, on Blog special page (Special:Blog), or by directly creating new pages in the Blog namespace.

===Creating a second blog===

As described the default blog feed consists of "normal" wiki pages stored in the Blog namespace. Other blog feeds can exist in addition to this feed, and they can be defined by category. For example, the category "Company news" can be designated for a second blog. In that case all pages in this category will be considered entries of this blog and will be displayed on page as blog entries. By adding <nowiki><bs:blog /></nowiki> tag to the page, attribute "cat" must be set to "Company news" like <nowiki><bs:blog cat="Company news" /></nowiki>

Another option is to designate a namespace for this purpose. Using example from above, namespace "Company news" must be created and all pages inside this namespace (Company news:News1, Company news:News2) will be considered blog entries. The syntax that should be used for the blog tag in this case is: <nowiki><bs:blog ns="Company news" /></nowiki> Keep in mind that when blog tags with "cat" or "ns" are used, all pages from that category/namespace will be shown, so those categories/namespaces should be used for that purpose only.

===<nowiki><bs:blog /></nowiki> attributes===

The following tag arguments can be used with the tag <nowiki><bs:blog /></nowiki>:

{| class="contenttable" style="width: 784px; height: 297px;" border="0"
|-
!|'''Attribute'''
!|'''Description'''
!|Value
|-
||count
||Number of blog entries to be displayed.
||number
|-
||cat
||Category from which to show pages as blog entries
||category name
|-
||ns
||Namespace from which to show pages as blog entries
||namespace name or ID
|-
||newentryfield
||Should "Create new blog entry" be shown?
||0 or 1
|-
||newentryfieldposition
||Position of the "Create new blog entry" form.
||"bottom" or "top"
|-
||renderimages
||Should images be displayed
||0 or 1
|-
||maxchars
||Number of characters that should be shown before the "Continue reading" link is shown.
||number
|}

Default values for these attributes for the whole wiki can be set in the global BlueSpice preferences. See [https://en.wiki.bluespice.com/wiki/Blog Reference page.]

==Tips for working with blogs==

Put a link to the blog in the left hand navigation menu. Then your colleagues will be able to find the blog whenever they want.

==See also==
Our [[Blog|reference page.]]

Talk:PageTemplates

2018-08-06T14:00:04Z

Bhofmann: Text replacement - "help.bluespice.com" to "wiki.bluespice.com"

'''Error:'''
Bluespice 2.23.3 MW 1.23.15 LTS
I have been trying to create page templates, and I can, but the templates that are presented during page creation, are red letter templates, and the template is empty at the page creation stage.
I think what may be the problem is I am unable to choose "Template namespace" during template creation as shown at https://wiki.bluespice.com/index.php/PageTemplates
Here is what I see during template creation at the attached file. As you can see the "Template namespace" dialogue is missing. Any help is greatly appreciated.

'''Splution:'''
This is a known bug in 2.23.3 [1]. You will need to update BlueSpiceExtensions to latest REL1_23 branch state (not released as tarball yet). You can find the download here:
https://extdist.wmflabs.org/dist/extensions/BlueSpiceExtensions-REL1_23-d78d922.tar.gz
You will have to recreate the page templates as the error already got written to the DB. Alternatively you can try to fix the DB entries in bs_pagetemplate.pt_template_title (Remove namespace prefix).
[1] https://gerrit.wikimedia.org/r/#/c/295888/

Manual:Create a new article

2018-08-06T14:00:04Z

Bhofmann: Text replacement - "help.bluespice.com" to "wiki.bluespice.com"

<bs:bookshelf src="Book:User manual" />
__HIDETITLE__

==How to create a new article==
__TOC__

===General hints before you begin...===
* Before creating a new article, take the time to''' find out if a similar article already exists'''. Search for the term and possible synonyms, and see if there are any alternate ways of spelling. If you can't find anything: go ahead and create!
* To create an '''article in a different namespace''', you have to add the namespace in front of the article name. Example: <nowiki>[[Desired_namespace:Name_of_the_article]]</nowiki>
* '''Do not use''' the following symbols when choosing a name for an article:

<div style="text-align: center;"><code>{ } & ? < > \ / ,</code></div>

===Three ways to create a new article===
====Method 1: Via the search function====
If your search for an article returned no results, you can use the search box to directly create this article. Simply click on ''Create page'', and you will be forwarded to the page to be created.

[[File:BlueSpice_Create_from_Search_en.png|thumb|center|450x225px|How to create a new page from the search box]]

====Method 2: Via the URL====
Go to your browser's address bar. You will see something like '''<nowiki>http://wiki.bluespice.com/index.php</nowiki>'''.
Add a slash and the name of the page to be created, and press enter. You will be automatically forwarded to the new page.
Example:

<div style="text-align: center;">
<pre>http://wiki.bluespice.com/index.php/New_article</pre></div>

====Method 3: Via a "Red link" in an article====
A classic way to create new articles in MediaWiki is by using so-called "red links". These are links in the text of an existing article that link to articles that don't exist yet, and are therefore colored red (as opposed to already active links which are colored blue).

By the way: you can view a list of all red links in your wiki on the special page <code>Special:WantedPages</code>.

{| style="border: 1px solid #98A7C4; background-color: #ffffff; border-left: 20px solid #98A7C4; margin-bottom: 0.4em; margin-left: auto; margin-right: auto; width: 100%;" border="0" cellspacing="2" cellpadding="5"
|-
||
To learn more about how to set links in an article, click [[InsertLink|here]].

|}

===Using page templates===
Whenever you create a new page in your wiki (regardless of the method used), you will always be forwarded to an overview page where you can choose from different page templates (provided that they have been installed by your administrator). If you don't want to use an existing template, click on ''Empty page'' or directly on ''Create''. You will then be able to add content to the page.

[[File:BlueSpice_Page_templates.png|thumb|center|450x161px|A typical example for an existing page template in the wiki]]

{| style="border: 1px solid #98A7C4; background-color: #ffffff; border-left: 20px solid #98A7C4; margin-bottom: 0.4em; margin-left: auto; margin-right: auto; width: 100%;" border="0" cellspacing="2" cellpadding="5"
|-
||
[[PageTemplates|Here]] you can find out more about page templates.

|}

===A special type of entry: writing a blog post===
BlueSpice also offers a function that allows users to publish news in a blog post. This can e.g. be very useful if you implement the blog feature on your main page, and use it to keep your employees informed on latest developments.

{| style="border: 1px solid #98A7C4; background-color: #ffffff; border-left: 20px solid #98A7C4; margin-bottom: 0.4em; margin-left: auto; margin-right: auto; width: 100%;" border="0" cellspacing="2" cellpadding="5"
|-
||
Click [[Blog|here]] to learn more about the blog functionality.

|}

===More tipps on creating pages===
* Avoid using the '''back button''' of your browser. Many browsers use the page cache to lower loading times, so you may be given an older version of the page. The worst case scenario is that the browser resends data from the edit form to the edit view, overwriting newer changes.
* Do you think that an article will often be searched by using a '''synonym'''? Add an article with this name and use a [[Redirects|redirect]]!
* The choice of a '''suitable page title''' is extremely important. Especially in large wikis it is quite common that authors link existing pages that look like important additional content in their articles without knowing exactly about the content of these pages. You should therefore take great care in choosing a title that is as precise and descriptive as possible. Individual words are often very helpful, but short sentences like "Why wikis work" can also be useful. Besides, descriptive page titles also help readers to navigate and search for entries more easily.
* When linking to an already existing page, take care to spell the title correctly. If e.g. you write <nowiki>[[hello world]]</nowiki> instead of <nowiki>[[HelloWorld]]</nowiki>, the link will create a new article because the name is spelled differently. So make sure that you take capitalization, spaces and the correct spelling into account!

===Video tutorial: "How do I create a new page?"===
{{#ev:youtube|l0z1zMHy4xM|450}}

[[Category:Manual]]

Main Page

2018-08-06T14:00:04Z

Bhofmann: Text replacement - "help.bluespice.com" to "wiki.bluespice.com"

__NOSTATEBAR__''' Welcome to the BlueSpice Helpdesk!'''

This helpdesk provides you with feature descriptions, support and tips and tricks on how to use your BlueSpice wiki.

<div style="text-align: center; target=blank;">[[File:De.png|none|link=http://de.wiki.bluespice.com/index.php/Hauptseite]]
[http://de.wiki.bluespice.com/index.php/Hauptseite Go to the german version].</div>
Do you want some interesting '''entry points'''?

{| class="cuscosky" style="width: 700px; height: 300px; text-align: center; vertical-align: middle; margin-left: auto; margin-right: auto;"
|-
| style="width: 200px; height: 100px;"|
[[File:Helpdesk-editieren.png|center]]

[[Manual:Wiki_basics_-_Introduction|User manual]]

| style="width: 500px; height: 100px; text-align: left;"|In the [[Manual:Wiki_basics_-_Introduction|user manual]], we will guide you step-by-step through BlueSpice. You will get an overview of the wiki, learn how to create articles, and how to enhance them by including pictures, links and files. Furthermore, we will show you ways to structure and personalize your BlueSpice wiki.
|-
| style="width: 200px; height: 100px;"|
[[File:Helpdesk-admin.png|center]]

[[WikiAdmin|Admin manual]]

| style="width: 500px; height: 100px; text-align: left;"|The [[WikiAdmin|admin manual]] compiles topics concerning the administration of a wiki: user, group and permission management, global settings in BlueSpice, as well as working with templates.
|-
| style="width: 200px; height: 100px;"|
[[File:Helpdesk-erweiteurngen.png|center]]

The right BlueSpice for everyone

| style="width: 500px; height: 100px; text-align: left;"|You either have the free version of BlueSpice, a subscription of BlueSpice pro, or manually installed additional packages. No matter what, here you will find detailed descriptions of your installation:
:* [[BlueSpice free]] - all extensions included in the free version
:* [[BlueSpice pro]] - extended functions of the subscription
:* [[:Category:Extension|All extensions]] - List of all available BlueSpice extensions

|-
| style="width: 200px; height: 100px;"|
[[File:Helpdesk-installieren.png|center]]

News

| style="width: 500px; height: 100px; text-align: left;"|
Here you will find an up-to-date list showing you the most recent changes on the helpdesk. Take a peek!

<bs:smartlist/>

|}

<div style="text-align: center;">... or just take a look at our '''How to''' portals. You can find links in the navigation menu on the right.</div>

<div style="text-align: center;">'''Have fun!'''</div>
[[en:{{FULLPAGENAME}}]][[de:Hauptseite]]

Archive:PageTemplates

2018-08-06T14:00:04Z

Bhofmann: Text replacement - "help.bluespice.com" to "wiki.bluespice.com"

Reference:BlueSpiceArticleInfo

2018-08-06T14:00:03Z

Bhofmann: Text replacement - "help.bluespice.com" to "wiki.bluespice.com"

{{BSExtensionInfobox
|desc=displays additional information about an article like the last edit, page assignments or categories.
|status=stable
|developer=HalloWelt
|type=BlueSpice
|edition=BlueSpice free, BlueSpice pro
|active=Yes
|compatible=BlueSpice
|category=Data Analysis
|docu=https://www.mediawiki.org/wiki/Extension:ArticleInfo
}}
__TOC__[[de:{{FULLPAGENAME}}]][[en:{{FULLPAGENAME}}]]

==Description==
'''ArticleInfo''' displays additional information about an article. You can find it at the top of the page in the [https://en.wiki.bluespice.com/wiki/StateBar StateBar].

==Usage/Features==
ArticleInfo offers information about:

* time of recent change,
* author of recent change (link to user page of the author),
* categories of this page (link to categorie pages),
* subpages of this page (opens the state bar there you will find links to the subpages),
* used templates and
* similar pages.

==Technical information==

===Configuration===
This extension has no configuration options.

===Rights (permissions)===
This extension requires no special rights, all users with "read" permission for the page, will also be able to see information provided by ArticleInfo.

===Requierements===
This extension requires [[BlueSpiceFoundation]] and [[StateBar]].

==User manual==
For detailed description and usage please visit our [[Manual:Extension/ArticleInfo|user manual.]]

==Try free our BlueSpice==
[https://en.demo.bluespice.com/wiki/Main_Page Demo] BlueSpice

[[en:{{FULLPAGENAME}}]][[de:{{FULLPAGENAME}}]]

[[Category:Extension]]

Reference Talk:FlexiSkin

2018-08-06T14:00:03Z

Bhofmann: Text replacement - "help.bluespice.com" to "wiki.bluespice.com"

'''Error:'''
Marketing would like us to modify the wiki background and replace the background image with an image that is one of ours.
As the admin, I opened the active skin, highlighted it and the skin preview appeared. I uploaded a new background image and saved. The first time I did it, a message appeared to save a file called "api.json". It saved in my downloads folder. I'm not sure what this is and where I should put it.
Could you please tell me how to modify the background image for my "NewSkin" so that it pulls the new graphic?

'''Solution:'''
You can modify your background image with Flexiskin (https://wiki.bluespice.com/index.php/FlexiSkin) just upload the image there, save and activate your new created skin.
(IE-Problem - work with Chrome and Firefox)

'''Error:'''
I've tried multiple fresh installs of mediawiki and bluespice but have not been able to get flexskin to work at all. What i'm doing is simply trying to add a background. The images directory has correct permissions as suggested in the installation procedure. I got no error messages but what happens is I click browse to upload an image(png) and then click upload to upload it. Nothing appears to happen. The background doesnt change and the Background image field is empty.

'''Solution:'''
Please try the current sources from - https://git.wikimedia.org/zip/?r=mediawiki/extensions/BlueSpiceFoundation.git&h=refs/heads/REL1_23&format=zip - https://git.wikimedia.org/zip/?r=mediawiki/extensions/BlueSpiceExtensions.git&h=refs/heads/REL1_23&format=zip - https://git.wikimedia.org/zip/?r=mediawiki/skins/BlueSpiceSkin.git&h=refs/heads/REL1_23&format=zip