BlueSpice - User contributions [en]

User blog:Mrosengarth

2025-07-09T13:08:33Z

Mrosengarth: Root blog page created

Archive:Setup:Installation Guide/With Installer

2024-05-27T09:36:13Z

Mrosengarth:

== Download installation package ==
{{DISPLAYTITLE:Installation BlueSpice 4 with Installer}}

{{Messagebox|boxtype=neutral|icon=yes|Note text=[https://bluespice.com/download/ Download the installation package] from the bluespice.com website.

Store the installation package in a web root of your choice (see our [[Setup:Installation_Guide/Advanced/Folder_structure_under_Windows|folder structure recommendations]] for Windows installations), where you can access it via your browser.

Make sure that [[Setup:Installation_Guide/Security_Settings/File_System_Permissions|file system permissions]] are set up properly.|bgcolor=}}
==Introduction==
BlueSpice 4 is installed as a complete package with MediaWiki 1.39 and BlueSpice 4.
This installation guide gives you step-by-step instructions to install BlueSpice.

{{Messagebox|boxtype=important|Note text=If you do a fresh install of BlueSpice 4, it might be necessary to run update.php afterwards if you get an error.|bgcolor=|icon=}}This document only describes the steps for installing the web application itself. For the installation of extended functions such as [[Setup:Installation_Guide/Advanced/VisualEditor_Configuration|VisualEditor]] and [[Setup:Installation Guide/Advanced/ExtendedSearch Configuration|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 checked the [[Setup:Installation_Guide#Prerequesites|system requirements]] and your server configuration. You can find more details in our detailed [[Setup:Installation Guide|installation guide]].

Further help on optimizing the operating system can be found in our [[Setup:Installation Guide/Advanced|compendium]].
==Step-by-step installation==

{{Messagebox|boxtype=note|icon=|Note 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!
|bgcolor=}}{{Messagebox|boxtype=note|icon=no|Note text=If Error "Fatal exception of type MWException" shows up, you need to check the rights of your Bluespice Folder and give it reading- and writing permissions. If there is still a error you need to add "$wgShowExceptionDetails = true" to your localsettings.php file and reload your URL to get preciser information of your error.|bgcolor=}}

First use your browser to call up the URL under which the web application can be reached. Then complete the following steps:
{| class="wikitable" style=""
|-
|[[File:Setup:1.png|alt=MediaWiki setup page php error|300x300px]]
||'''Step 1: Start the installation setup'''
First, open the URL of your web application in your browser. Then click on "set up the wiki" to start the installation.

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 the thumbnail to see the full screenshot).

|-
|[[File:Setup:2.png|alt=Select language|300x300px]]
||'''Step 2: Select your language'''
You are now in the language selection.
"Your language" defines the language that guides you through the installer,

"Wiki language" the later language settings of your wiki.
|-
|[[File:Setup:3.png|alt=Installation check|300x300px]]
||'''Step 3: MediaWiki installation check'''
This step takes you to the MediaWiki installation check.
Please read this check carefully, as possible hints may not block the installation itself, but may lead to restrictions of the wiki functionality in practice.
Make the necessary corrections to your system and reload the page in your browser before proceeding with the setup.
|-
|[[File:Setup:4.png|alt=Database connection|300x300px]]
||'''Step 4: Establish the database connection'''
In this step, you configure the database connection.
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.
Or, 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:5.png|alt=Database user|300x300px]]
||'''Step 5: Create the BlueSpice database user'''
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:6.png|alt=Wiki name and admin account|300x300px]]
||'''Step 6: Create your wiki name and administrator account'''
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 extra attention to the correct spelling, because this name can afterwards only be changed with a certain effort and certain risks. Next, enter the username, password and e-mail address of the first wiki administrator. The administrator account is then created by the wiki during setup.
|-
|[[File:Setup:7.png|alt=Email options|center|300x300px]]
||'''Step 7: Options'''
In this step, you specify the e-mail address for notification e-mails.
|-
|[[File:Setup:8.png|alt=|thumb]]
||'''Step 8: Installation'''
This step announces the installation of the wiki. If you don't need to make any changes to the previous steps, click "Next" to start the installation process.
|-
|[[File:Setup:9.png|alt=Installation status|center|300x300px]]
||'''Step 9: Installation status'''
After the successful installation of BlueSpice, you see a confirmation page that you confirm with "Next".
|-
|[[File:Setup:10.png|alt=Download localsettings.php|300x300px]]
||'''Step 10: Download LocalSettings.php'''
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.
|-
|
|'''Step 11: Rename the template folders'''
#Open the folder <code><installpath-bluespice>\extensions\BlueSpiceFoundation</code> and rename the subfolder <code>config.template</code> to <code>config</code> and create the new folder <code>data</code>. These folders should have read and write access, see [[Setup:Installation Guide/Security Settings/File System Permissions|File System Permissions]]. Note: Since BlueSpice 4.3.0, <code>config.template</code> directory no longer exists, so step of renaming it should be skipped
#Run <code>php <installpath-bluespice>\maintenance\update.php</code> from the console.
|-
|[[File:Setup:11.png|alt=BlueSpice start page|300x300px]]
||'''Step 12: Load the BlueSpice welcome page'''
If you now access the URL you specified for BlueSpice, you now see the BlueSpice welcome page. You can start using BlueSpice immediately.
|}

==BlueSpice WikiFarm==
If you are installing '''BlueSpice WikiFarm,''' follow these [[:en:Setup:Installation_Guide/Installation_BlueSpice_WikiFarm|instructions.]] If not, skip to [[:en:Setup:Installation_Guide/Installation_BlueSpice_WikiFarm|Next steps.]]

Now open a command line and change to the folder <code><installpath-bluespice></code>.

Run the following command:

*<code>php maintenance/update.php</code> ''(Linux)''
*<code>php maintenance\update.php</code> ''(Windows)''
==Next steps==
{{Messagebox|boxtype=note|Note text=If the page is not loading, give the group "users" change-permissions for the folder C:\Windows\Temp.}}
For security reasons, it is recommended to prevent access to the path <code>mw-config/</code> after the installation. This can be implemented as follows:

 
=Linux=
In Apache, add the following entry to the file <code>000-bluespice.conf</code>:
<pre>
<Directory /var/www/bluespice/w/mw-config>
Require all denied
</Directory>
</pre>

 
=Windows=
In IIS, create a file <code>web.config</code> in the sub-directory <code>mw-config/</code> with the following content:
<pre>
<?xml version="1.0" encoding="UTF-8"?>
<configuration>
<system.webServer>
<security>
<authentication>
<anonymousAuthentication enabled="false" />
</authentication>
</security>
</system.webServer>
</configuration>
</pre>
<headertabs /><notabtoc/>
Please note that this entry may have to be removed temporarily if the web installer is used to update the application.

{{Messagebox|boxtype=important|Note text=As next step, you can configure [[Setup:Installation Guide/Advanced/VisualEditor Configuration|VisualEditor]] and [[Setup:Installation Guide/Advanced/ExtendedSearch Configuration|Extendedsearch]].}}
[[en:{{FULLPAGENAME}}]]
[[de:Setup:Installationsanleitung/Installation von BlueSpice]]

Archive:Setup:Installation Guide/With Installer

2024-05-27T09:27:36Z

Mrosengarth:

== Download installation package ==
{{DISPLAYTITLE:Installation BlueSpice 4 with Installer}}

{{Messagebox|boxtype=neutral|icon=yes|Note text=[https://bluespice.com/download/ Download the installation package] from the bluespice.com website.

Store the installation package in a web root of your choice (see our [[Setup:Installation_Guide/Advanced/Folder_structure_under_Windows|folder structure recommendations]] for Windows installations), where you can access it via your browser.

Make sure that [[Setup:Installation_Guide/Security_Settings/File_System_Permissions|file system permissions]] are set up properly.|bgcolor=}}
==Introduction==
BlueSpice 4 is installed as a complete package with MediaWiki 1.39 and BlueSpice 4.
This installation guide gives you step-by-step instructions to install BlueSpice.

{{Messagebox|boxtype=important|Note text=If you do a fresh install of BlueSpice 4, it might be necessary to run update.php afterwards if you get an error.|bgcolor=|icon=}}This document only describes the steps for installing the web application itself. For the installation of extended functions such as [[Setup:Installation_Guide/Advanced/VisualEditor_Configuration|VisualEditor]] and [[Setup:Installation Guide/Advanced/ExtendedSearch Configuration|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 checked the [[Setup:Installation_Guide#Prerequesites|system requirements]] and your server configuration. You can find more details in our detailed [[Setup:Installation Guide|installation guide]].

Further help on optimizing the operating system can be found in our [[Setup:Installation Guide/Advanced|compendium]].
==Step-by-step installation==

{{Messagebox|boxtype=note|icon=|Note 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!
|bgcolor=}}{{Messagebox|boxtype=note|icon=no|Note text=If Error "Fatal exception of type MWException" shows up, you need to check the rights of your Bluespice Folder and give it reading- and writing permissions. If there is still a error you need to add "$wgShowExceptionDetails = true" to your localsettings.php file and reload your URL to get preciser information of your error.|bgcolor=}}

First use your browser to call up the URL under which the web application can be reached. Then complete the following steps:
{| class="wikitable" style=""
|-
|[[File:Setup:1.png|alt=MediaWiki setup page php error|300x300px]]
||'''Step 1: Start the installation setup'''
First, open the URL of your web application in your browser. Then click on "set up the wiki" to start the installation.

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 the thumbnail to see the full screenshot).

|-
|[[File:Setup:2.png|alt=Select language|300x300px]]
||'''Step 2: Select your language'''
You are now in the language selection.
"Your language" defines the language that guides you through the installer,

"Wiki language" the later language settings of your wiki.
|-
|[[File:Setup:3.png|alt=Installation check|300x300px]]
||'''Step 3: MediaWiki installation check'''
This step takes you to the MediaWiki installation check.
Please read this check carefully, as possible hints may not block the installation itself, but may lead to restrictions of the wiki functionality in practice.
Make the necessary corrections to your system and reload the page in your browser before proceeding with the setup.
|-
|[[File:Setup:4.png|alt=Database connection|300x300px]]
||'''Step 4: Establish the database connection'''
In this step, you configure the database connection.
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.
Or, 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:5.png|alt=Database user|300x300px]]
||'''Step 5: Create the BlueSpice database user'''
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:6.png|alt=Wiki name and admin account|300x300px]]
||'''Step 6: Create your wiki name and administrator account'''
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 extra attention to the correct spelling, because this name can afterwards only be changed with a certain effort and certain risks. Next, enter the username, password and e-mail address of the first wiki administrator. The administrator account is then created by the wiki during setup.
|-
|[[File:Setup:7.png|alt=Email options|center|300x300px]]
||'''Step 7: Options'''
In this step, you specify the e-mail address for notification e-mails.
|-
|[[File:Setup:8.png|alt=|thumb]]
||'''Step 8: Installation'''
This step announces the installation of the wiki. If you don't need to make any changes to the previous steps, click "Next" to start the installation process.
|-
|[[File:Setup:9.png|alt=Installation status|center|300x300px]]
||'''Step 9: Installation status'''
After the successful installation of BlueSpice, you see a confirmation page that you confirm with "Next".
|-
|[[File:Setup:10.png|alt=Download localsettings.php|300x300px]]
||'''Step 10: Download LocalSettings.php'''
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.
|-
|
|'''Step 11: Rename the template folders'''
#Open the folder <code><installpath-bluespice>\extensions\BlueSpiceFoundation</code> and rename the subfolder <code>config.template</code> to <code>config</code> and create the new folder <code>data</code>. These folders should have read and write access, see [[Setup:Installation Guide/Security Settings/File System Permissions|File System Permissions]]. Note: Since BlueSpice 4.3.0, <code>config.template</code> directory no longer exists, so step of renaming it should be skipped
#Run <code>php <installpath-bluespic</code><code>e></code><code>\maintenance\update.php</code> from the console.
|-
|[[File:Setup:11.png|alt=BlueSpice start page|300x300px]]
||'''Step 12: Load the BlueSpice welcome page'''
If you now access the URL you specified for BlueSpice, you now see the BlueSpice welcome page. You can start using BlueSpice immediately.
|}

==BlueSpice WikiFarm==
If you are installing '''BlueSpice WikiFarm,''' follow these [[:en:Setup:Installation_Guide/Installation_BlueSpice_WikiFarm|instructions.]] If not, skip to [[:en:Setup:Installation_Guide/Installation_BlueSpice_WikiFarm|Next steps.]]

Now open a command line and change to the folder <code><installpath-bluespice></code>.

Run the following command:

*<code>php maintenance/update.php</code> ''(Linux)''
*<code>php maintenance\update.php</code> ''(Windows)''
==Next steps==
{{Messagebox|boxtype=note|Note text=If the page is not loading, give the group "users" change-permissions for the folder C:\Windows\Temp.}}
For security reasons, it is recommended to prevent access to the path <code>mw-config/</code> after the installation. This can be implemented as follows:

 
=Linux=
In Apache, add the following entry to the file <code>000-bluespice.conf</code>:
<pre>
<Directory /var/www/bluespice/w/mw-config>
Require all denied
</Directory>
</pre>

 
=Windows=
In IIS, create a file <code>web.config</code> in the sub-directory <code>mw-config/</code> with the following content:
<pre>
<?xml version="1.0" encoding="UTF-8"?>
<configuration>
<system.webServer>
<security>
<authentication>
<anonymousAuthentication enabled="false" />
</authentication>
</security>
</system.webServer>
</configuration>
</pre>
<headertabs /><notabtoc/>
Please note that this entry may have to be removed temporarily if the web installer is used to update the application.

{{Messagebox|boxtype=important|Note text=As next step, you can configure [[Setup:Installation Guide/Advanced/VisualEditor Configuration|VisualEditor]] and [[Setup:Installation Guide/Advanced/ExtendedSearch Configuration|Extendedsearch]].}}
[[en:{{FULLPAGENAME}}]]
[[de:Setup:Installationsanleitung/Installation von BlueSpice]]

Ghostscript-CVE-2023-36664 - How to fix

2023-07-28T07:49:41Z

Mrosengarth:

{{Featurepage|featured=true|featuredesc=Ghostscript-CVE-2023-36664 - How to fix|featurestart=07/28/2023}}
==Overview==
This page is related to the [[Security:Security Advisories/BSSA-2023-01|BSSA-2023-01 Security Advisory]].

Older versions of Ghostscript open a way for script infusion.

Because of bugs in the Ghostscript binary out of the BlueSpice package manager, Hallo Welt! mostly installed manually on Linux systems. These bugs no longer seem to be a problem.
==How to update - Linux==

# '''Check '''the system for manual installation and delete it:<syntaxhighlight lang="bash">ls -al /usr/local/bin</syntaxhighlight>If there is a binary called<syntaxhighlight lang="bash">gs</syntaxhighlight>delete it:<syntaxhighlight lang="bash">
rm -fr /usr/local/bin/gs</syntaxhighlight>
#'''Check''' the system for an installation out of the package manager (Ghostscript comes as a dependency of ImageMagik):<syntaxhighlight lang="bash">
dpkg -l ghostscript
</syntaxhighlight>for Debian 11 this should look like:<syntaxhighlight lang="bash">
root@XXXXXXXXXXXX:~# dpkg -l ghostscript
Gewünscht=Unbekannt/Installieren/R=Entfernen/P=Vollständig Löschen/Halten
| Status=Nicht/Installiert/Config/U=Entpackt/halb konFiguriert/
Halb installiert/Trigger erWartet/Trigger anhängig
|/ Fehler?=(kein)/R=Neuinstallation notwendig (Status, Fehler: GROSS=schlecht)
||/ Name Version Architektur Beschreibung
+++-==============-=====================-============-===================================================
ii ghostscript 9.53.3~dfsg-7+deb11u5 amd64 interpreter for the PostScript language and for PDF

</syntaxhighlight>For Debian 12 the Version is "10.0.0~dfsg-11+deb12u1" For Ubuntu 22 the Version is "9.50~dfsg-5ubuntu4.8" If it does not match the needed Version please do an:<syntaxhighlight lang="bash">
apt update
apt upgrade -y
</syntaxhighlight>and recheck.
#'''Change''' the settings in the codebase. Go to the directory where the codebase is saved (check your ApacheConfiguration for''DocumentRoot'' if you are not sure). Normally it should look like this:<syntaxhighlight lang="bash">
root@XXXXX:/var/www/bluespice/w/settings.d# grep -rin PdfProcessor
005-PdfHandler.php:5:$wgPdfProcessor = '/usr/local/bin/gs';

</syntaxhighlight>It could be <code>005-PdfHandler.php</code> or some other configuration file.
#'''Find''' '''and change''' the variable to the correct path, for example with this command:<syntaxhighlight lang="bash">
sed -i 's/local\///g' 005-PdfHandler.php

</syntaxhighlight>Double-check:<syntaxhighlight lang="bash">
root@XXXXXXXXXXX:/var/www/bluespice/w/settings.d# grep -rin PdfProcessor
005-PdfHandler.php:5:$wgPdfProcessor = '/usr/bin/gs';

</syntaxhighlight>

Your system is now patched.

==How to update - Windows==

#'''Deinstall''' the package ''GPL Ghostscript''.
#'''Download''' the package ''Ghostscript AGPL Release'' from https://www.ghostscript.com/releases/gsdnld.html .
#'''Install''' the new package.

Your system is now patched.

__FORCETOC__

Archive:Setup:Installation Guide/Upgrade

2023-02-13T09:44:50Z

Mrosengarth:

{{DISPLAYTITLE:Upgrade from BlueSpice 3 to 4}}

==System requirements==
===Browser===
{{#dpl:title=Setup:System requirements|include=#Browser}}
===Server environment===
{{#dpl:title=Setup:System requirements|include=#Server Environment}}
{{Messagebox|boxtype=note|icon=|Note text=You might need to add external repos to get the correct php on your server! Please check your package manager for the available php versions on your system.|bgcolor=}}
==Back up the old wiki==
In BlueSpice 3, create a temporary migration folder and copy all necessary data:<syntaxhighlight lang="bash">
mkdir /tmp/migration
cd /tmp/migration
wikifolder=/path/to/wikifolder
cp -r $wikifolder/images .
cp -r $wikifolder/extensions/BlueSpiceFoundation/config .
cp -r $wikifolder/LocalSettings.* .
#check for for locals in settings.d
find $wikifolder/settings.d/ -iname '*.local.php' -exec cp --parent {} /tmp/migration \;

</syntaxhighlight>Also search for specialized php files in <code>settings.d</code> (normally <code>090-</code> or <code>099-</code> ).
==Upgrade step 1==
This step has to be completed before the ''Upgrade step 2'' further below.{{Messagebox|boxtype=warning|icon=|Note text=BlueSpice 4.x cannot process wiki pages and files that were uploaded and edited by '''deleted users'''. To prevent data loss, don't skip any upgrade steps!|bgcolor=}}
===Create a "substitute user" for deleted users===
In BlueSpice 3.x, create a user with a random password:
php maintenance/createAndPromote.php --force DeletedUser someR4ndomPass
{{Messagebox|boxtype=note|icon=|Note text=You may need to temporarily disable authentication plugins like LDAP-Stack, SAML or OpenIDConnect extensions.|bgcolor=}}
Get the <code>user_id</code> of the substitute user by running the following command in the database:
SELECT user_id FROM user WHERE user_name = "DeletedUser";
==Sql dump==
Create the backup of your data:<syntaxhighlight lang="bash">
mysqldump -u root -p bluespice > migrationdump.sql
</syntaxhighlight>
==Optional files for migration==
If any of the following features apply to your installation, check if migration steps are necessary. In that case, add everything to your ''tar'' file and send it to the new server.

Examples of files that you might have to consider:

* ssl-certs
* apache.conf
* ldapprovider.json
* kerberos files (krb5.conf/keyfile)

==Migrate to the new wiki==
''Grep'' <code>LocalSettings.php</code> for <code>wgDB</code><syntaxhighlight lang="bash">
grep wgDB LocalSettings.*
LocalSettings.local.php:$wgDBserver = "Your-IP";
LocalSettings.local.php:$wgDBname = "Your-datbase-name";
LocalSettings.local.php:$wgDBuser = "Your-database-user";
LocalSettings.local.php:$wgDBpassword = "Your-password";

</syntaxhighlight>and create the '''database''' and '''DBuser''' with the '''DBpassword'''. Grant <code>all</code> on database to the '''DBuser''' in mysql.

Migrate the data:<syntaxhighlight lang="bash">
mysql -u root -p bluespice < migration.sql
cp -r images $wikifolder
cp -r extensions $wikifolder
cp -r LocalSettings.php $wikifolder
setWikiPerm $wikifolder

</syntaxhighlight>
====Modify LocalSettings.php====
Replace:<syntaxhighlight lang="php">
$wgLogo = "$wgResourceBasePath/resources/assets/wiki.png";
</syntaxhighlight>with:<syntaxhighlight lang="php">
$wgLogos = [ '1x' => "$wgResourceBasePath/resources/assets/wiki.png" ];

</syntaxhighlight>
*Check other <code>LocalSettings.*</code> for individual configurations from the old BlueSpice installation.
*Compare the <code>migrated settings.d/*.local.php</code> with the new <code>settings.d/*.php</code> and check for individual (probably deprecated) configurations. Do the same with <code>09*-xx.php</code>.
*Copy to <code>$wikifolder/settings.d/</code> what is needed.
==Upgrade step 2==
Assign all pages and files without a valid editor user to your newly created substitute user:<syntaxhighlight lang="bash">
cd $wikifolder
php extensions/BlueSpiceFoundation/maintenance/PrepareActorMigration.php --unknownUserId=<user-id-from-step I. > --unknownUserName=DeletedUser
</syntaxhighlight>
==Optional==
*Copy the following files (if applicable in your case):<code>apache.conf</code>, <code>krb5.conf,</code> <code>Kerberos-key</code>, <code>ldapprovider.json</code>
*Add to VirtualHost in <code>Apache.conf</code> after rewrite rules:
AllowEncodedSlashes NoDecode
==Last steps==
Run the following maintenance scripts:<syntaxhighlight lang="bash">
cd $wikifolder
php maintenance/update.php --quick
php extensions/BlueSpiceExtendedSearch/maintenance/initBackends.php --quick
php extensions/BlueSpiceExtendedSearch/maintenance/rebuildIndex.php --quick

screen
while [ "$(php maintenance/showJobs.php)" != "0" ]; do php maintenance/runJobs.php --maxjobs 100; done

</syntaxhighlight>The last step will take a while.
==Known possible issues after the update==
===Problems with VisualEditor===
<div>
Add in <code>includes/libs/http/MultiHttpClient.php</code> after line 327:
curl_setopt( $ch, CURLOPT_SSL_VERIFYHOST, 0 );
curl_setopt( $ch, CURLOPT_SSL_VERIFYPEER, 0 );
</div>

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

MediaWiki:Common.js

2022-12-08T11:18:47Z

Mrosengarth: Created page with "/* Any JavaScript here will be loaded for all users on every page load. */ if ( mw.config.get( 'wgCanonicalSpecialPageName' ) === 'Watchlist' ) { document.body.classList...."

/* Any JavaScript here will be loaded for all users on every page load. */

if ( mw.config.get( 'wgCanonicalSpecialPageName' ) === 'Watchlist' ) {
document.body.classList.add( 'mw-rcfilters-ui-initialized' );
}

Archive:Manual:Extension/BlueSpiceUniversalExport

2022-11-21T13:26:53Z

Mrosengarth:

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

'''BlueSpiceUniversalExport''' allows exporting wiki pages to various formats. It incorporates various modules, each serving as exporter for a particular export type.

==The export menu==
Every content page on the wiki can be exported. Export fuctions are located in the general [[Manual:Extension/BlueSpiceDiscovery#Page_tools|page tools]] under the menu item ''Export''. The available export options depend on your wiki configuration. Clicking one of the links downloads the page content in the selected format.

 
[[File:Manual:pageexport.png|alt=export options menu in the page tools|center|thumb|348x348px|Export options]]

==Configuration==

Configuration of UniversalExport (and its modules) can be done in the [[Manual:Extension/BlueSpiceConfigManager|Config manager]] in the ''Export'' section. Available settings include:

*'''Table of contents:''' only applies to exporting books. Select how the ToC should be constructed (as a ToC for the entire book or for each page individually).
*'''Hide namespace prefix in HTML:''' removes namespace prefixes when displaying page titles in HTML exports.
*'''Hide namespace prefix in PDF:''' removes namespace prefixes when displaying page titles in PDF exports.
*'''Metadata (standard, JSON)''' : additional data to be passed to the rendering template in JSON format. This data will be avalible for usage in the template (advanced users).
*'''Metadata (override, JSON)''': offers overriding standard data sent to the rendering template. Values that are set by default can be overriden by using this option (JSON format) (advanced users). 
[[File:Manual:UniversalExport2a.png|link=link=link=https://en.wiki.bluespice.com/wiki/File:UniversalExport2a.png|alt=|center|thumb|372x372px|Configuration options]]
 

==Tags==
If the following tags are included in a page, they are usually applied both to the PDF book export and to the PDF single page export unless otherwise noted.

===Manual page breaks===
You can insert the following tag on a wiki page anywhere you want to force a manual page break in the PDF:<syntaxhighlight lang="text">
<bs:uepagebreak />
</syntaxhighlight>In visual editing mode, a marker is displayed where the page breaks have been inserted.
 
[[File:pdf-pagebreak-marker.png|center|thumb|750x750px|Marker for page breaks in visual editing mode|link=Special:FilePath/pdf-pagebreak-marker.png]]
 
=== Landscape printing ===
To print a PDF page in landscape format, the following tag can be inserted in the wiki page in source editing mode at any position:
<nowiki><bs:ueparams template="BlueSpice_Landscape" /></nowiki>
To make it easier for the user to add this tag with the visual editor, this tag can be added to a wikitext-template, for example, <code><nowiki>{{LandscapeFormatExport}}</nowiki></code>. The element can be inserted anywhere on the page.{{Messagebox|boxtype=note|Note text=This tag only works for the PDF single page export.}}Within a wiki page, individual areas can be marked separately (e.g. wide tables). This way, the output in the export can be landscape or extra-wide. This is possible using the following css classes:

*"bs-rotated" -> landscape format
*"bs-narrow" -> 0,33 x A4 portrait
*"bs-ultrawide" -> 2 x A4 landscape

These classes can also be combined. Example:
<nowiki><div class="bs-rotated bs-ultrawide">...</div></nowiki>
The start and end div tags can also be added to templates (e.g., <code><nowiki>{{LandscapeStart}}</nowiki></code> and <code><nowiki>{{LandscapeEnd}}</nowiki></code>) to allow users to insert the tags using the visual editor.{{Messagebox|boxtype=note|Note text=Display of header and footer areas could be problematic when using these tags.}}These css classes also work for the book export.

===PDF-specific styling===
{{Messagebox|boxtype=important|Note text=The tag is only taken applied in the single page export (including linked pages and subpages). The tag from individual pages is ignored in the book export. The tag can, however, be inserted on the corresponding book page in the ''Book:'' namespace and is then applied to all pages in the book.}}
To style classes or IDs only in the PDF output, you can include the following tag at the beginning of a page:<syntaxhighlight lang="text">
<bs:uemeta body-class=class-name-here/>
</syntaxhighlight>

 
Example''': Changing background, header, and footer settings'''

#Insert the tag <code><nowiki><bs:uemeta body-class=bg-grey bg-yellow no-header-image no-footer-text/></nowiki></code> at the top of your wiki page.
#To define the page background, add the following CSS to <code>MediaWiki:Common.css</code> ein (admin rights needed):<syntaxhighlight lang="css">
/*PDF output*/
.bg-grey { background-color:#EDEDED !important;} /*sets the page background. There will be a white margin around it.*/
.bg-yellow .bs-page-content { background-color:#F7F0C6; padding:10px;} /*sets the background color for the content and adds padding*/
.no-header-image #bs-runningheaderfix { background:none;} /*removes the PDF header*/
.no-footer-text #bs-runningfooterleft, .no-footer-text #bs-runningfootercenter, .no-footer-text #bs-runningfooterright { display:none;} /*removes the text from the PDF footer*/
</syntaxhighlight>Compare the page before inserting the tag and after inserting the tag: 
<gallery widths="250" heights="400">
File:Manual:250px-pdf-class-output-vorher.png
File:Manual:250px-pdf-class-output-nachher.png
</gallery>

===Exclude content from PDF export===
To exclude the content of a page from the PDF export, it can be inserted via the visual editor under ''Insert> No PDF''. The text is then marked accordingly in the source text:
<nowiki><bs:uenoexport>Dieser Text wird nicht ins PDF exportiert.</bs:uenoexport></nowiki>

==Show content in PDF only==
If content should only be displayed in the PDF, but not on the wiki page, this content can be marked manually via the source text. First, a wiki administrator needs to add the following code to the page ''MediaWiki: Common.css'':<syntaxhighlight lang="css">
.bs-page-content .no-pdf {
display: none;
}
.bs-page-content div.only-pdf {
display:block;
}
.bs-page-content span.only-pdf {
display:inline;
}

.only-pdf {
display: none;
}
</syntaxhighlight>

 
A block element or an inline element can now be created for the PDF export. This content is not rendered on the wiki page in display mode. Source code examples:
<div class="only-pdf">This block is only shown in the PDF.</div>
The adjective <span class="no-pdf">beautiful</span><span class="only-pdf">small</span> is shown differently on the page and in the PDF.
 
==Display of email addresses==
If an email link has an additional label on a wiki page, the email address will be listed separately in the PDF after the link label.
 
[[File:Manual:750px-pdf-email-wikipage-EN.png|link=link=Special:FilePath/pdf-email-wikipage-EN.png|alt=|center|thumb|479x479px|Email link on wiki page]]
 
[[File:Manual:750px-pdf-email-output-EN.png|link=link=Special:FilePath/pdf-email-output-EN.png|alt=|center|thumb|478x478px|PDF link in PDF output]]
 
==Printing==
MediaWiki, by default, provides a print view for the pages. This command is also available in the ''Export'' menu (option ''Print'').

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

== Modules ==
The extension ''BlueSpiceUniversalExport'' contains several modules:

* '''BlueSpiceUEModulePDF:''' module for exporting pages in PDF (.pdf) format. It downloads the current page (PDF single page), the current page including all its subpages (PDF page with subpages), or the current page and the pages that are linked from that page (PDF page with linked pages).
* '''BlueSpiceUEModuleHTML:''' module for exporting pages as an html zip-archive (option HTML single page).
* '''BlueSpiceUEModuleBookPDF:''' module for exporting books.
{{Box Links-en|Topic1=[[Reference:BlueSpiceUniversalExport]]
|Topic2=[[Reference:BlueSpiceUEModulePDF]]
|Topic3=[[Reference:BlueSpiceUEModuleBookPDF]]
|Topic4=[[Reference:BlueSpiceUEModuleHTML]]
|Topic5=[[Manual:Extension/BlueSpiceBookshelf|Creating books]]
}}

{{Translation}}

[[Category:Page tools]]

Archive:Manual:Extension/BlueSpiceUniversalExport

2022-11-21T13:26:05Z

Mrosengarth:

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

'''BlueSpiceUniversalExport''' allows exporting wiki pages to various formats. It incorporates various modules, each serving as exporter for a particular export type.

==The export menu==
Every content page on the wiki can be exported. Export fuctions are located in the general [[Manual:Extension/BlueSpiceDiscovery#Page_tools|page tools]] under the menu item ''Export''. The available export options depend on your wiki configuration. Clicking one of the links downloads the page content in the selected format.

 
[[File:Manual:pageexport.png|alt=export options menu in the page tools|center|thumb|348x348px|Export options]]

==Configuration==

Configuration of UniversalExport (and its modules) can be done in the [[Manual:Extension/BlueSpiceConfigManager|Config manager]] in the ''Export'' section. Available settings include:

*'''Table of contents:''' only applies to exporting books. Select how the ToC should be constructed (as a ToC for the entire book or for each page individually).
*'''Hide namespace prefix in HTML:''' removes namespace prefixes when displaying page titles in HTML exports.
*'''Hide namespace prefix in PDF:''' removes namespace prefixes when displaying page titles in PDF exports.
*'''Metadata (standard, JSON)''' : additional data to be passed to the rendering template in JSON format. This data will be avalible for usage in the template (advanced users).
*'''Metadata (override, JSON)''': offers overriding standard data sent to the rendering template. Values that are set by default can be overriden by using this option (JSON format) (advanced users). 
[[File:Manual:UniversalExport2a.png|link=link=link=https://en.wiki.bluespice.com/wiki/File:UniversalExport2a.png|alt=|center|thumb|372x372px|Configuration options]]
 

==Tags==
If the following tags are included in a page, they are usually applied both to the PDF book export and to the PDF single page export unless otherwise noted.

===Manual page breaks===
You can insert the following tag on a wiki page anywhere you want to force a manual page break in the PDF:<syntaxhighlight lang="text">
<bs:uepagebreak >
</syntaxhighlight>In visual editing mode, a marker is displayed where the page breaks have been inserted.
 
[[File:pdf-pagebreak-marker.png|center|thumb|750x750px|Marker for page breaks in visual editing mode|link=Special:FilePath/pdf-pagebreak-marker.png]]
 
=== Landscape printing ===
To print a PDF page in landscape format, the following tag can be inserted in the wiki page in source editing mode at any position:
<nowiki><bs:ueparams template="BlueSpice_Landscape" /></nowiki>
To make it easier for the user to add this tag with the visual editor, this tag can be added to a wikitext-template, for example, <code><nowiki>{{LandscapeFormatExport}}</nowiki></code>. The element can be inserted anywhere on the page.{{Messagebox|boxtype=note|Note text=This tag only works for the PDF single page export.}}Within a wiki page, individual areas can be marked separately (e.g. wide tables). This way, the output in the export can be landscape or extra-wide. This is possible using the following css classes:

*"bs-rotated" -> landscape format
*"bs-narrow" -> 0,33 x A4 portrait
*"bs-ultrawide" -> 2 x A4 landscape

These classes can also be combined. Example:
<nowiki><div class="bs-rotated bs-ultrawide">...</div></nowiki>
The start and end div tags can also be added to templates (e.g., <code><nowiki>{{LandscapeStart}}</nowiki></code> and <code><nowiki>{{LandscapeEnd}}</nowiki></code>) to allow users to insert the tags using the visual editor.{{Messagebox|boxtype=note|Note text=Display of header and footer areas could be problematic when using these tags.}}These css classes also work for the book export.

===PDF-specific styling===
{{Messagebox|boxtype=important|Note text=The tag is only taken applied in the single page export (including linked pages and subpages). The tag from individual pages is ignored in the book export. The tag can, however, be inserted on the corresponding book page in the ''Book:'' namespace and is then applied to all pages in the book.}}
To style classes or IDs only in the PDF output, you can include the following tag at the beginning of a page:<syntaxhighlight lang="text">
<bs:uemeta body-class=class-name-here/>
</syntaxhighlight>

 
Example''': Changing background, header, and footer settings'''

#Insert the tag <code><nowiki><bs:uemeta body-class=bg-grey bg-yellow no-header-image no-footer-text/></nowiki></code> at the top of your wiki page.
#To define the page background, add the following CSS to <code>MediaWiki:Common.css</code> ein (admin rights needed):<syntaxhighlight lang="css">
/*PDF output*/
.bg-grey { background-color:#EDEDED !important;} /*sets the page background. There will be a white margin around it.*/
.bg-yellow .bs-page-content { background-color:#F7F0C6; padding:10px;} /*sets the background color for the content and adds padding*/
.no-header-image #bs-runningheaderfix { background:none;} /*removes the PDF header*/
.no-footer-text #bs-runningfooterleft, .no-footer-text #bs-runningfootercenter, .no-footer-text #bs-runningfooterright { display:none;} /*removes the text from the PDF footer*/
</syntaxhighlight>Compare the page before inserting the tag and after inserting the tag: 
<gallery widths="250" heights="400">
File:Manual:250px-pdf-class-output-vorher.png
File:Manual:250px-pdf-class-output-nachher.png
</gallery>

===Exclude content from PDF export===
To exclude the content of a page from the PDF export, it can be inserted via the visual editor under ''Insert> No PDF''. The text is then marked accordingly in the source text:
<nowiki><bs:uenoexport>Dieser Text wird nicht ins PDF exportiert.</bs:uenoexport></nowiki>

==Show content in PDF only==
If content should only be displayed in the PDF, but not on the wiki page, this content can be marked manually via the source text. First, a wiki administrator needs to add the following code to the page ''MediaWiki: Common.css'':<syntaxhighlight lang="css">
.bs-page-content .no-pdf {
display: none;
}
.bs-page-content div.only-pdf {
display:block;
}
.bs-page-content span.only-pdf {
display:inline;
}

.only-pdf {
display: none;
}
</syntaxhighlight>

 
A block element or an inline element can now be created for the PDF export. This content is not rendered on the wiki page in display mode. Source code examples:
<div class="only-pdf">This block is only shown in the PDF.</div>
The adjective <span class="no-pdf">beautiful</span><span class="only-pdf">small</span> is shown differently on the page and in the PDF.
 
==Display of email addresses==
If an email link has an additional label on a wiki page, the email address will be listed separately in the PDF after the link label.
 
[[File:Manual:750px-pdf-email-wikipage-EN.png|link=link=Special:FilePath/pdf-email-wikipage-EN.png|alt=|center|thumb|479x479px|Email link on wiki page]]
 
[[File:Manual:750px-pdf-email-output-EN.png|link=link=Special:FilePath/pdf-email-output-EN.png|alt=|center|thumb|478x478px|PDF link in PDF output]]
 
==Printing==
MediaWiki, by default, provides a print view for the pages. This command is also available in the ''Export'' menu (option ''Print'').

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

== Modules ==
The extension ''BlueSpiceUniversalExport'' contains several modules:

* '''BlueSpiceUEModulePDF:''' module for exporting pages in PDF (.pdf) format. It downloads the current page (PDF single page), the current page including all its subpages (PDF page with subpages), or the current page and the pages that are linked from that page (PDF page with linked pages).
* '''BlueSpiceUEModuleHTML:''' module for exporting pages as an html zip-archive (option HTML single page).
* '''BlueSpiceUEModuleBookPDF:''' module for exporting books.
{{Box Links-en|Topic1=[[Reference:BlueSpiceUniversalExport]]
|Topic2=[[Reference:BlueSpiceUEModulePDF]]
|Topic3=[[Reference:BlueSpiceUEModuleBookPDF]]
|Topic4=[[Reference:BlueSpiceUEModuleHTML]]
|Topic5=[[Manual:Extension/BlueSpiceBookshelf|Creating books]]
}}

{{Translation}}

[[Category:Page tools]]

BlueSpice 4.1

2022-04-26T11:53:09Z

Mrosengarth:

BlueSpice 4.1 is a Minor Release.
==Point Releases==
{{#ask: [[Release::4.1]]
|?Releasepatch = Release
|?Releasedate#LOCL = Releasedate
|mainlabel= -
|headers = plain
|sort=Releasedate
|order=desc
}}

==Important new features in BlueSpice 4.1 pro==
{| class="wikitable" style="width:100%;"
!Function
!Description
!Screenshot
|-
|'''[[Manual:Extension/BlueSpiceDiscovery|New standard skin "Discovery"]]'''
|Modern, light-weight skin. We focused on a neutral design and thought a lot about usability. As an alternative, you can still activate the previous "Calumma" skin.
|[[File:discovery-skin-EN.png|alt=Skin "Discovery"|center|thumb|400x400px|Skin "Discovery"]]
|-
|'''[[Manual:Extension/FlexiSkin|FlexiSkin]]'''
|With the FlexiSkin editor, you can change the logo, colors, and fonts within minutes directly in the wiki.
|[[File:flexi-main-EN.png|alt=FlexiSkin|center|thumb|400x400px|FlexiSkin]]
|-
|'''[[Manual:Extension/Workflows|Workflows]]'''
|The workflow function has been completely revised. Workflows are now based on BPMN. This makes it easier to adapt them to special requirements. Four review workflows are already included.
|[[File:workflow-select.png|alt=Selecting a workflow|center|thumb|400x400px|Selecting a workflow]]
|-
|'''[[Reference:UnifiedTaskOverview|My tasks]]'''
|The new “My Tasks” overview page enables users to view and process all pending workflow tasks or read confirmations.
|[[File:my tasks.png|alt=My tasks|center|thumb|400x400px|My tasks]]
|-
|'''[[Reference:CognitiveProcessDesigner|BPMN diagrams]]'''
|You can now create business processes in BPMN format. The diagrams can be exported as XML files or in SVG format.
|[[File:bpmn-employee-relocation1.png|alt=BPMN diagram|center|thumb|400x400px|BPMN diagram]]
|-
|[[Reference:WebAuthn|'''Two-factor authentication''']]
|Logins to the wiki can now also be configured to require an additional one-time password or a physical security key (Fido stick).
|
|}
==Additional added Extensions==
{| class="wikitable" style="width:100%;"
|+Developer: MW=MediaWiki Extension HW: Hallo Welt! Extension
!'''Extension'''
!'''Developer'''
!'''Description'''
|-
|[[Reference:Data Transfer|DataTransfer]]
|MW
|Allows for importing and exporting the contents of a wiki's pages in XML and CSV form, using template calls to define the fields
|-
|[[Reference:EventBus|EventBus]]
|MW
|Propagates state changes (edit, move, delete, revision visibility, etc) to a RESTful event service, providing consumers of the service with the means of tracking changes to MediaWiki content.
|-
|[[Reference:Forms|Forms]]
|HW
|A new all-purpose forms framework for MediaWiki.
|-
|[[Reference:Loops|Loops]]
|MW
|Parser functions for performing loops.
|-
|[[Reference:OATHAuth|OATHAuth]]
|MW
|Provides authentication support using HMAC based one-time passwords. Now by default activated in BlueSpice pro.
|-
|[[Reference:PageCheckout|PageCheckout]]
|HW
|Grants a user exclusive rights on a page. Works in conjunction with the Worfklows extension.
|-
|[[Reference:PageHeader|PageHeader]]
|HW
|Provides an additional user interface before the page content
|-
|[[Reference:RevisionSlider|RevisionSlider]]
|MW
|Shows a slider allowing selecting and comparing of revisions on a diff page.
|-
|[[Reference:SecureLinkFixer|SecureLinkFixer]]
|MW
|Rewrites URLs to HTTPS if domain always requires HTTPS.
|-
|[[Reference:StandardDialogs|StandardDialogs]]
|MW
|Provides dialog user interfaces for common page actions.
|-
|[[Reference:WebAuthn|WebAuthn]]
|MW
|Provides authentication support using WebAuthn protocol.
|}

*

==Extensions that are no longer included==

*'''BlueSpiceBookshelfUI''': Removed since BlueSpice 3.2.
*'''BlueSpiceEditNotifyConnector''': Removed since BlueSpice 3.2.
*'''BlueSpiceReview''' and '''BlueSpiceReviewExtended''': Replaced by '''Workflows'''.
*'''BlueSpiceSocialArticleActions'''
*'''BlueSpiceTagSearch''': Removed since BlueSpice 3.2.
*'''BlueSpiceUserMergeConnector'''
*'''BluespiceVisualDiff'''
*'''CookieWarning:''' Functionality has been integrated in BlueSpicePrivacy.
*'''Duplicator''' (Copying a page): Replaced by StandardDialogs.
*'''EditNotify''': Removed since BlueSpice 3.2.
*'''Quiz'''
*'''Page Schemas'''
* '''Semantic Internal Objects'''

==Additional changes in BlueSpice free==

*Removal of the LDAP stack: LDAP extensions are now only bundled with BlueSpice pro.
*BlueSpicePermissionManager: Custom settings are only available in BlueSpice pro.

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

BlueSpice 4.1

2022-04-26T11:52:21Z

Mrosengarth:

Two-BlueSpice 4.1 is a Minor Release.
==Point Releases==
{{#ask: [[Release::4.1]]
|?Releasepatch = Release
|?Releasedate#LOCL = Releasedate
|mainlabel= -
|headers = plain
|sort=Releasedate
|order=desc
}}

==Important new features in BlueSpice 4.1 pro==
{| class="wikitable" style="width:100%;"
!Function
!Description
!Screenshot
|-
|'''[[Manual:Extension/BlueSpiceDiscovery|New standard skin "Discovery"]]'''
|Modern, light-weight skin. We focused on a neutral design and thought a lot about usability. As an alternative, you can still activate the previous "Calumma" skin.
|[[File:discovery-skin-EN.png|alt=Skin "Discovery"|center|thumb|400x400px|Skin "Discovery"]]
|-
|'''[[Manual:Extension/FlexiSkin|FlexiSkin]]'''
|With the FlexiSkin editor, you can change the logo, colors, and fonts within minutes directly in the wiki.
|[[File:flexi-main-EN.png|alt=FlexiSkin|center|thumb|400x400px|FlexiSkin]]
|-
|'''[[Manual:Extension/Workflows|Workflows]]'''
|The workflow function has been completely revised. Workflows are now based on BPMN. This makes it easier to adapt them to special requirements. Four review workflows are already included.
|[[File:workflow-select.png|alt=Selecting a workflow|center|thumb|400x400px|Selecting a workflow]]
|-
|'''[[Reference:UnifiedTaskOverview|My tasks]]'''
|The new “My Tasks” overview page enables users to view and process all pending workflow tasks or read confirmations.
|[[File:my tasks.png|alt=My tasks|center|thumb|400x400px|My tasks]]
|-
|'''[[Reference:CognitiveProcessDesigner|BPMN diagrams]]'''
|You can now create business processes in BPMN format. The diagrams can be exported as XML files or in SVG format.
|[[File:bpmn-employee-relocation1.png|alt=BPMN diagram|center|thumb|400x400px|BPMN diagram]]
|-
|[[Reference:WebAuthn|'''Two-factor authentication''']]
|Logins to the wiki can now also be configured to require an additional one-time password or a physical security key (Fido stick).
|
|}
==Additional added Extensions==
{| class="wikitable" style="width:100%;"
|+Developer: MW=MediaWiki Extension HW: Hallo Welt! Extension
!'''Extension'''
!'''Developer'''
!'''Description'''
|-
|[[Reference:Data Transfer|DataTransfer]]
|MW
|Allows for importing and exporting the contents of a wiki's pages in XML and CSV form, using template calls to define the fields
|-
|[[Reference:EventBus|EventBus]]
|MW
|Propagates state changes (edit, move, delete, revision visibility, etc) to a RESTful event service, providing consumers of the service with the means of tracking changes to MediaWiki content.
|-
|[[Reference:Forms|Forms]]
|HW
|A new all-purpose forms framework for MediaWiki.
|-
|[[Reference:Loops|Loops]]
|MW
|Parser functions for performing loops.
|-
|[[Reference:OATHAuth|OATHAuth]]
|MW
|Provides authentication support using HMAC based one-time passwords. Now by default activated in BlueSpice pro.
|-
|[[Reference:PageCheckout|PageCheckout]]
|HW
|Grants a user exclusive rights on a page. Works in conjunction with the Worfklows extension.
|-
|[[Reference:PageHeader|PageHeader]]
|HW
|Provides an additional user interface before the page content
|-
|[[Reference:RevisionSlider|RevisionSlider]]
|MW
|Shows a slider allowing selecting and comparing of revisions on a diff page.
|-
|[[Reference:SecureLinkFixer|SecureLinkFixer]]
|MW
|Rewrites URLs to HTTPS if domain always requires HTTPS.
|-
|[[Reference:StandardDialogs|StandardDialogs]]
|MW
|Provides dialog user interfaces for common page actions.
|-
|[[Reference:WebAuthn|WebAuthn]]
|MW
|Provides authentication support using WebAuthn protocol.
|}

*

==Extensions that are no longer included==

*'''BlueSpiceBookshelfUI''': Removed since BlueSpice 3.2.
*'''BlueSpiceEditNotifyConnector''': Removed since BlueSpice 3.2.
*'''BlueSpiceReview''' and '''BlueSpiceReviewExtended''': Replaced by '''Workflows'''.
*'''BlueSpiceSocialArticleActions'''
*'''BlueSpiceTagSearch''': Removed since BlueSpice 3.2.
*'''BlueSpiceUserMergeConnector'''
*'''BluespiceVisualDiff'''
*'''CookieWarning:''' Functionality has been integrated in BlueSpicePrivacy.
*'''Duplicator''' (Copying a page): Replaced by StandardDialogs.
*'''EditNotify''': Removed since BlueSpice 3.2.
*'''Quiz'''
*'''Page Schemas'''
* '''Semantic Internal Objects'''

==Additional changes in BlueSpice free==

*Removal of the LDAP stack: LDAP extensions are now only bundled with BlueSpice pro.
*BlueSpicePermissionManager: Custom settings are only available in BlueSpice pro.

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

Archive:Setup:Installation Guide/System Preparation/Windows/Python

2022-03-15T14:16:08Z

Mrosengarth:

__TOC__

{{Hint|file=icon_optional.png|text=Python with the Pygmentize extension is required for rendering the MediaWiki extension [https://www.mediawiki.org/wiki/Extension:SyntaxHighlight SyntaxHighlight], which is part of BlueSpice. If you do not need the functionality, the installation of Python is not relevant for the installation and operation of BlueSpice.}}
==Download==
{{Hint|file=hint.png|text=The content of this section refers to external sources and is current at the time of writing this documentation. We cannot guarantee how long these sources will remain unchanged. Please let us know if you notice any discrepancies to the information provided here.}}

Download Python directly at [https://www.python.org python.org].

[[File:Setup:systempreparation_python_01.png|border|center|600px|Python 01]]

{{Hint|file=hint.png|text=In the following, Python in version 3.10.2 is used and only serves as an example for the most current version that you can download at the time of your installation.}}
==Installation==
'''Open''' the file that you have just downloaded.

'''Select''' both checkboxes (1).

'''Click''' "Customize installation" (2):

[[File:Setup:systempreparation_python_02.png|border|center|600px|Python 02]]

'''Click''' "Next" in the Optional Features window.

[[File:Setup:systempreparation_python_03.png|border|center|600px|Python 03]]

Make sure to install Python for all users (1) . Choose an appropriate path, if possible without spaces and special characters (2)

'''Click''' "Install" to start the installation (3).

[[File:Setup:systempreparation_python_04.png|border|center|600px|Python 04]]

{{Hint|file=hint.png|text=This documentation assumes the [[Setup:Installation_Guide/Advanced/Windows_Folder_Structure| folder structure recommended by us]]. For this reason, Python is unpacked at this point in the folder C:\bluespice\bin\python-3.10.2. If you have individual wishes, adjust these paths according to your own understanding.}}

'''Deactivate''' the limitation of the path length to 260 characters after the installation:

[[File:Setup:systempreparation_python_05.png|border|center|600px|Python 05]]

'''Click''' "Close" to finish the installation.

[[File:Setup:systempreparation_python_06.png|border|center|600px|Python 06]]

=Installing Pygmentize=
'''Open''' the PowerShell (the command prompt in older Windows versions). To do this, '''right-click''' "Start" (1) and select "Command Prompt (Administrator)" (2):

[[File:Setup:systempreparation_python_07.png|border|center|Python 07]]

Geben Sie den Befehl "pip install pygments" ein und warten Sie, bis der folgende Prozess

[[File:Setup:systempreparation_python_08.png|border|center|600px]]

==Completion==
Your Windows server is now fully prepared for the actual installation of BlueSpice.

User:Mrosengarth

2022-03-15T14:13:45Z

Mrosengarth: create user page