https://en.wiki.bluespice.com/w/api.php?action=feedcontributions&user=WikiSysop&feedformat=atomBlueSpice Wiki - User contributions [en]2024-03-28T19:49:17ZUser contributionsMediaWiki 1.39.6https://en.wiki.bluespice.com/w/index.php?title=Setup:Installation_Guide/With_Installer&diff=8462Setup:Installation Guide/With Installer2024-03-21T08:32:02Z<p>WikiSysop: </p>
<hr />
<div>== Download installation package ==<br />
{{DISPLAYTITLE:Installation BlueSpice 4 with Installer}}<br />
<br />
{{Messagebox|boxtype=neutral|icon=yes|Note text=[https://bluespice.com/download/ Download the installation package] from the bluespice.com website.<br />
<br />
<br />
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.<br />
<br />
<br />
Make sure that [[Setup:Installation_Guide/Security_Settings/File_System_Permissions|file system permissions]] are set up properly.|bgcolor=}}<br />
==Introduction==<br />
BlueSpice 4 is installed as a complete package with MediaWiki 1.39 and BlueSpice 4.<br />
This installation guide gives you step-by-step instructions to install BlueSpice.<br />
<br />
{{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.<br />
<br />
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]].<br />
<br />
Further help on optimizing the operating system can be found in our [[Setup:Installation Guide/Advanced|compendium]].<br />
==Step-by-step installation==<br />
<br />
{{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!<br />
|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=}}<br />
<br />
First use your browser to call up the URL under which the web application can be reached. Then complete the following steps: <br />
{| class="wikitable" style=""<br />
|-<br />
|[[File:Setup:1.png|alt=MediaWiki setup page php error|300x300px]]<br />
||'''Step 1: Start the installation setup'''<br />
First, open the URL of your web application in your browser. Then click on "set up the wiki" to start the installation. <br />
<br />
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).<br />
<br />
|-<br />
|[[File:Setup:2.png|alt=Select language|300x300px]]<br />
||'''Step 2: Select your language'''<br />
You are now in the language selection.<br />
"Your language" defines the language that guides you through the installer,<br />
<br />
"Wiki language" the later language settings of your wiki.<br />
|-<br />
|[[File:Setup:3.png|alt=Installation check|300x300px]]<br />
||'''Step 3: MediaWiki installation check'''<br />
This step takes you to the MediaWiki installation check. <br />
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.<br />
Make the necessary corrections to your system and reload the page in your browser before proceeding with the setup.<br />
|-<br />
|[[File:Setup:4.png|alt=Database connection|300x300px]]<br />
||'''Step 4: Establish the database connection'''<br />
In this step, you configure the database connection. <br />
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. <br />
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]].<br />
|-<br />
|[[File:Setup:5.png|alt=Database user|300x300px]]<br />
||'''Step 5: Create the BlueSpice database user'''<br />
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".<br />
|-<br />
|[[File:Setup:6.png|alt=Wiki name and admin account|300x300px]]<br />
||'''Step 6: Create your wiki name and administrator account'''<br />
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.<br />
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.<br />
|-<br />
|[[File:Setup:7.png|alt=Email options|center|300x300px]]<br />
||'''Step 7: Options'''<br />
In this step, you specify the e-mail address for notification e-mails.<br />
|-<br />
|[[File:Setup:8.png|alt=|thumb]]<br />
||'''Step 8: Installation'''<br />
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.<br />
|-<br />
|[[File:Setup:9.png|alt=Installation status|center|300x300px]]<br />
||'''Step 9: Installation status'''<br />
After the successful installation of BlueSpice, you see a confirmation page that you confirm with "Next".<br />
|-<br />
|[[File:Setup:10.png|alt=Download localsettings.php|300x300px]]<br />
||'''Step 10: Download LocalSettings.php'''<br />
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.<br />
|-<br />
|<br />
|'''Step 11: Rename the template folders'''<br />
#Open the folder <code><installpath-bluespice>\extensions\BluesSpiceFoundation</code> and rename the subfolder <code>config.template</code> to <code>config</code> and create the new folder <code>data</code>. <span /><span /><span /><span /><span /><span /><br />These folders should have read and write access, see [[Setup:Installation Guide/Security Settings/File System Permissions|File System Permissions]]. <br /><span class="col-purple">Note: Since BlueSpice 4.3.0, <code>config.template</code> directory no longer exists, so step of renaming it should be skipped</span><br />
#Run <code>php <installpath-bluespic</code><span /><span /><span /><span /><span /><span /><code>e></code><span /><span /><span /><span /><span /><span /><span /><span /><span /><span /><span /><span /><code>\maintenance\update.php</code> from the console.<br />
|-<br />
|[[File:Setup:11.png|alt=BlueSpice start page|300x300px]]<br />
||'''Step 12: Load the BlueSpice welcome page'''<br />
If you now access the URL you specified for BlueSpice, you now see the BlueSpice welcome page. You can start using BlueSpice immediately.<br />
|}<br />
<br />
==BlueSpice WikiFarm==<br />
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.]]<br />
<br />
Now open a command line and change to the folder <code><installpath-bluespice></code>. <br />
<br />
Run the following command:<br />
<br />
*<code>php maintenance/update.php</code> ''(Linux)''<br />
*<code>php maintenance\update.php</code> ''(Windows)''<br />
==Next steps==<br />
{{Messagebox|boxtype=note|Note text=If the page is not loading, give the group "users" change-permissions for the folder C:\Windows\Temp.}}<br />
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:<br />
<br />
<span><span /><span /><span /><span /><span /><br /></span><br />
=Linux=<br />
In Apache, add the following entry to the file <code>000-bluespice.conf</code>:<br />
<pre><br />
<Directory /var/www/bluespice/w/mw-config><br />
Require all denied<br />
</Directory><br />
</pre><br />
<br />
<span><span /><span /><span /><span /><br /></span><br />
=Windows=<br />
In IIS, create a file <code>web.config</code> in the sub-directory <code>mw-config/</code> with the following content:<br />
<pre><br />
<?xml version="1.0" encoding="UTF-8"?><br />
<configuration><br />
<system.webServer><br />
<security><br />
<authentication><br />
<anonymousAuthentication enabled="false" /><br />
</authentication><br />
</security><br />
</system.webServer><br />
</configuration><br />
</pre><br />
<headertabs /><notabtoc/><br />
Please note that this entry may have to be removed temporarily if the web installer is used to update the application.<br />
<br />
{{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]].}}<br />
[[en:{{FULLPAGENAME}}]]<br />
[[de:Setup:Installationsanleitung/Installation von BlueSpice]]</div>WikiSysophttps://en.wiki.bluespice.com/w/index.php?title=Setup:Installation_Guide/Advanced/Backup&diff=8440Setup:Installation Guide/Advanced/Backup2024-03-07T07:31:51Z<p>WikiSysop: </p>
<hr />
<div>=== Manual backup ===<br />
<br />
==== Backup of the database ====<br />
To back up your database, use the native program <code>mysqldump</code> of MySQL/MariaDB: Open a console, switch to the directory <code><installpath-bluespice></code> and backup your database with the following command:<br />
mysqldump -u <username> -p --lock-tables <database> > database.sql<br />
For <code><username></code> , use the administrative database user, and for <code><database></code> , use the database of your MediaWiki/BlueSpice installation. <br />
<br />
{{Textbox|boxtype=important|header=|text=On Windows, make sure that your environment variables are set correctly, so that you can access the command <code>mysqldump</code>.|icon=yes}}<br />
<br />
==== Backup of the file system ====<br />
Back up the complete directory <code><installpath-bluespice></code>, which now also includes the database image, to a different location on your server.<br />
<br />
'''For security reasons, immediately delete the file<code><installpath-bluespice>/database.sql</code>, since it can be accessed from the browser.'''<br />
<br />
=== Using the <code>mediawiki-adm</code> tool ===<br />
To eas backup and restore one can also use the <code>mediawiki-adm</code> tool. It can be downloaded here: https://github.com/hallowelt/misc-mediawiki-adm<br />
<br />
<br />
'''Example usage:'''<br />
mediawiki-adm wiki-backup \<br />
--mediawiki-root <installpath-bluespice> \<br />
--dest /mnt/backup/<br />
The tool will leave out all unnecessary data (like temporary files and cache database tables)and produce much smaller backup files that the manual method described above. It also allows to create versioned backups.</div>WikiSysophttps://en.wiki.bluespice.com/w/index.php?title=Setup:Installation_Guide/Webservices/Mathoid&diff=8055Setup:Installation Guide/Webservices/Mathoid2024-01-10T15:28:45Z<p>WikiSysop: </p>
<hr />
<div>Mathoid is a nodjs service which takes various forms of math input and converts it to MathML + SVG or PNG output.<br />
<br />
{{Messagebox|boxtype=important|icon=|Note text=Beginning with BlueSpice 4.x, Mathoid is no longer distributed and has to installed separately.<br />
<br /><br />
Download: <br />
<br />
https://buildservice.bluespice.com/webservices/REL1_39-4.3.x/mathoid.tar.gz or https://buildservice.bluespice.com/webservices/REL1_39-4.3.x/mathoid.zip|bgcolor=}}<br />
<br />
If mathematical formulas are not rendered in your wiki, please check that <code>extensions/Math/webservices/mathoid.tar.gz</code> is deployed in the correct folder:<br />
*Linux: <code>/opt/mathoid</code><br />
*Windows: <code>C:\BlueSpice\bin\mathoid</code><br />
<br />
<br />
{{Textbox<br />
|boxtype=neutral<br />
|header=PDF-Export integration<br />
|text=The PDF-Export does not support SVGs at the moment. Therefore the SVG needs to be converted into a PNG when embedded into a PDF. This is done automatically, but requires <code>$wgSVGConverter</code> to be set up properly. It is recommended to use <code>rsvg</code> as a converter. On Debian based linux environments it can be installed with<br />
<br />
apt install librsvg2-bin<br />
<br />
In the <code>LocalSettings.php</code> file it must be configured with<br />
<br />
$GLOBALS['wgSVGConverter'] = 'rsvg';<br />
|icon=yes<br />
}}<br />
<br />
== Next step ==<br />
<span style="color: rgb(37, 37, 37)">If you have completed all steps successfully and want to install BlueSpice pro, proceed to the next step</span> [[Setup:Installation Guide/System Preparation/Linux/PhantomJS|PhantomJS]]</div>WikiSysophttps://en.wiki.bluespice.com/w/index.php?title=Setup:Installation_Guide/Advanced/Backup&diff=7098Setup:Installation Guide/Advanced/Backup2023-08-03T15:15:12Z<p>WikiSysop: </p>
<hr />
<div><br />
===Backup of the database===<br />
To back up your database, use the native program "mysqldump" of MySQL/MariaDB: Open a console, switch to the directory <code><installpath-bluespice></code> and backup your database with the following command:<br />
mysqldump -u <username> -p --lock-tables <database> > database.sql<br />
For <code><username></code> , use the administrative database user, and for <code><database></code> , use the database of your MediaWiki/BlueSpice installation. <br />
{{Messagebox|boxtype=Hint|Note text=In Windows, make sure that your environment variables are set correctly, so that you can access the command "mysqldump".}}<br />
===Backup of the file system===<br />
Back up the complete directory <code><installpath-bluespice></code>, which now also includes the database image, to a different location on your server.<br />
<br />
'''For security reasons, immediately delete the file<code><installpath-bluespice>/database.sql</code>, since it can be accessed from the browser.'''</div>WikiSysophttps://en.wiki.bluespice.com/w/index.php?title=Template:Messagebox&diff=7097Template:Messagebox2023-08-03T15:14:55Z<p>WikiSysop: </p>
<hr />
<div><includeonly><templatestyles src="Messagebox/styles.css" /><div class="hw-messagebox notification-{{{boxtype}}} {{#switch: {{{icon}}}|yes=icon|ja=icon}}" {{#if:{{{bgcolor|}}}|style="background:{{{bgcolor}}}"|}}><span class="boxlabel">{{#switch: {{{boxtype}}} | note = Note: | Hinweis = Hinweis: | Hint = Hint: | tip = Tip: | Tipp = Tipp: | warning = Warning! | Warnung = Achtung! | example = Example: | Beispiel = Beispiel: | important = Important! | Wichtig = Wichtig! | neutral = | Neutral = }}</span>{{{Note text}}}</div></includeonly><br />
<noinclude><br />
Kopiervorlage:<br />
<pre><br />
{{Messagebox|boxtype = |Note text =| bgcolor =}}<br />
</pre><br />
<templatedata><br />
{<br />
"params": {<br />
"Note text": {<br />
"required": true,<br />
"label": {<br />
"de": "Text"<br />
}<br />
},<br />
"boxtype": {<br />
"example": {<br />
"en": "note, tip, warning, important, example, neutral",<br />
"de": "Hinweis, Tipp, Wichtig, Warnung, Beispiel, Neutral"<br />
},<br />
"type": "string",<br />
"default": "Hint",<br />
"required": true,<br />
"label": {<br />
"de": "Art von Box",<br />
"en": "Type of box"<br />
},<br />
"description": {<br />
"en": "note, tip, warning, important, example, neutral",<br />
"de": "Hinweis, Tipp, Wichtig, Warnung, Beispiel, Neutral"<br />
}<br />
},<br />
"bgcolor": {<br />
"label": {<br />
"de": "Hintergrundfarbe",<br />
"en": "Background color"<br />
},<br />
"description": {<br />
"en": "Background color for neutral box in hex-format (#ececec)",<br />
"de": "Hintergrundfarbe für neutrale Box in Hex-format (#ececec)"<br />
},<br />
"type": "string",<br />
"example": "#ececec",<br />
"suggested": true<br />
},<br />
"icon": {<br />
"label": {<br />
"en": "Show icon",<br />
"de": "Symbol anzeigen"<br />
},<br />
"description": {<br />
"en": "Shows icon before the label",<br />
"de": "Zeigt ein passendes Symbol "<br />
},<br />
"example": {<br />
"en": "yes, no",<br />
"de": "ja, nein"<br />
},<br />
"suggested": true<br />
}<br />
},<br />
"description": {<br />
"de": "Infobox für Hinweise, Warnungen, Tipps, etc.",<br />
"en": "Infobox for notes, warnings, tips, etc."<br />
},<br />
"paramOrder": [<br />
"boxtype",<br />
"icon",<br />
"Note text",<br />
"bgcolor"<br />
]<br />
}<br />
</templatedata><br />
</noinclude></div>WikiSysophttps://en.wiki.bluespice.com/w/index.php?title=Setup:Installation_Guide/Advanced/Backup&diff=7096Setup:Installation Guide/Advanced/Backup2023-08-03T11:45:45Z<p>WikiSysop: </p>
<hr />
<div><br />
===Backup of the database===<br />
To back up your database, use the native program "mysqldump" of MySQL/MariaDB: Open a console, switch to the directory <code><installpath-bluespice></code> and backup your database with the following command:<br />
mysqldump -u <username> -p --lock-tables <database> > database.sql<br />
For <code><username></code> , use the administrative database user, and for <code><database></code> , use the database of your MediaWiki/BlueSpice installation. <br />
{{Messagebox|boxtype=Hinweis|Note text=In Windows, make sure that your environment variables are set correctly, so that you can access the command "mysqldump".}}<br />
===Backup of the file system===<br />
Back up the complete directory <code><installpath-bluespice></code>, which now also includes the database image, to a different location on your server.<br />
<br />
'''For security reasons, immediately delete the file<code><installpath-bluespice>/database.sql</code>, since it can be accessed from the browser.'''</div>WikiSysophttps://en.wiki.bluespice.com/w/index.php?title=Setup:Installation_Guide/Advanced/Backup&diff=7095Setup:Installation Guide/Advanced/Backup2023-08-03T11:41:36Z<p>WikiSysop: </p>
<hr />
<div><br />
===<span class="mw-headline" id="Backup_der_Datenbank" style="box-sizing: inherit;">Backup of the database</span>===<br />
To back up your database, use the native program "mysqldump" of MySQL/MariaDB: Open a console, switch to the directory <code style="box-sizing: inherit; font-family: monospace, Courier; font-size: 13.5px; padding: 1px 4px; color: black; background-color: rgb(249, 249, 249); border-radius: 2px; border: 1px solid rgb(221, 221, 221);"><installpath-bluespice></code> and backup your database with the following command:<br />
mysqldump -u <username> -p --lock-tables <database> > database.sql<br />
For <code style="box-sizing: inherit; font-family: monospace, Courier; font-size: 13.5px; padding: 1px 4px; color: black; background-color: rgb(249, 249, 249); border-radius: 2px; border: 1px solid rgb(221, 221, 221);"><username></code> <span>,</span> use the administrative database user, and for <code style="box-sizing: inherit; font-family: monospace, Courier; font-size: 13.5px; padding: 1px 4px; color: black; background-color: rgb(249, 249, 249); border-radius: 2px; border: 1px solid rgb(221, 221, 221);"><database></code> <span>, use the database of your</span> MediaWiki/BlueSpice installation. <br />
{{Messagebox|boxtype=Hinweis|Note text=In Windows, make sure that your environment variables are set correctly, so that you can access the command "mysqldump".}}<br />
===<span class="mw-headline" id="Backup_des_Filesystems" style="box-sizing: inherit;">Backup of the file system</span>===<br />
Back up the complete directory <code style="box-sizing: inherit; font-family: monospace, Courier; font-size: 13.5px; padding: 1px 4px; color: black; background-color: rgb(249, 249, 249); border-radius: 2px; border: 1px solid rgb(221, 221, 221);"><installpath-bluespice></code>, which now also includes the database image, to a different location on your server.<br />
<br />
'''For security reasons, immediately delete the file<code style="box-sizing: inherit; font-family: monospace, Courier; font-size: 13.5px; padding: 1px 4px; color: black; background-color: rgb(249, 249, 249); border-radius: 2px; border: 1px solid rgb(221, 221, 221);"><installpath-bluespice>/database.sql</code>, since it can be accessed from the browser.'''</div>WikiSysophttps://en.wiki.bluespice.com/w/index.php?title=Setup:Installation_Guide/Advanced/Maintenance_scripts/export&diff=6256Setup:Installation Guide/Advanced/Maintenance scripts/export2023-06-14T12:00:11Z<p>WikiSysop: </p>
<hr />
<div>== Running the script ==<br />
The script to export wiki pages to PDF is executed from: <syntaxhighlight lang="text"><br />
php {MW_ROOT}/extensions/BlueSpiceUniversalExport/maintenance/export.php --specification-file=spec.json<br />
</syntaxhighlight>The specification file <code>spec.json</code> can have the following content:<syntaxhighlight lang="text"><br />
{<br />
"module": "pdf",<br />
"attachments": 1,<br />
"recursive": 1,<br />
"title": "MyPDF",<br />
"target": "localfilesystem",<br />
"target-file-name": "All.pdf",<br />
"target-file-path": "/path/to/target-file"<br />
}<br />
</syntaxhighlight><br />
{| class="wikitable" style="width: 100%;"<br />
|+<br />
! style="width:200px;" |Key<br />
! style="width:200px;" |Value<br />
!Description<br />
|-<br />
| style="width:200px;" |module<br />
| style="width:200px;" |pdf<br />
|Output type<br />
|-<br />
| style="width:200px;" |attachments<br />
| style="width:200px;" |1<br />
0<br />
|Attachments will be included in the export<br />
|-<br />
| style="width:200px;" |recursive<br />
| style="width:200px;" |1<br />
0<br />
|Linked pages (one level deep) will be included.<br />
|-<br />
| style="width:200px;" |title<br />
| style="width:200px;" |string<br />
|Title of the wiki page that contains the list of pages to be exported. '''The pages need to be links.'''<br />
|-<br />
| style="width:200px;" |target<br />
| style="width:200px;" |localfilesystem<br />
|The file will be exported to a local file system.<br />
|-<br />
| style="width:200px;" |target-file-name<br />
| style="width:200px;" |<br />
|Name of the exported PDF file<br />
|-<br />
| style="width:200px;" |target-file-path<br />
| style="width:200px;" |<br />
|Target file location<br />
|}<br />
<br />
== Creating a page list for the export ==<br />
The export list is defined in the wiki page that is shown as the <code>title</code> in the json-file. (In the example above, this is the page <code>MyPDF</code> .)<br />
<br />
The page <code>MyPDF</code> now needs to list all pages that will be exported to PDF. <br />
<br />
This list can be created with an [[SMW queries|SMW inline query]] (BlueSpice free) or with a [[Manual:Extension/DynamicPageList3|DPL3 list]] (BlueSpice free).<br />
Example of an SMW query to create an export for all pages in the categories <code>Process</code> and <code>Work instruction</code>:<br />
<br />
You would add the following to your <code>MyPDF</code> page in the wiki:<syntaxhighlight lang="text"><br />
==All processes==<br />
{{#ask:[[Process:+]]|format=ul|limit=99999}}<br />
<br />
==All work instructions==<br />
{{#ask:[[Work instruction:+]]|format=ul|limit=99999}}<br />
</syntaxhighlight>The same list can be created with the following DPL3 syntax:<syntaxhighlight lang="text"><br />
==All processes==<br />
{{#dpl:category=Process}}<br />
<br />
==All work instructions==<br />
{{#dpl:category=Work instruction}}<br />
</syntaxhighlight><br />
<br />
== Setting up a CronJob ==<br />
To automate the export, the following CronJob is available:<syntaxhighlight lang="text"><br />
php {MW_ROOT}/extensions/BlueSpiceUniversalExport/maintenance/export.php --specification-file={MW_ROOT}/extensions/BlueSpiceFoundation/data/spec.json<br />
</syntaxhighlight><br />
__FORCETOC__</div>WikiSysophttps://en.wiki.bluespice.com/w/index.php?title=Manual:Extension/BlueSpiceConfigManager&diff=6255Manual:Extension/BlueSpiceConfigManager2023-06-14T11:55:13Z<p>WikiSysop: </p>
<hr />
<div><bookshelf src="Book:Admin manual" /><br />
{{DISPLAYTITLE:Config manager}}<br />
__TOC__<br />
<br />
With the Config manager, a wiki user with ''sysop'' rights can manage wiki-wide settings in one place. In the [[Manual:Extension/BlueSpiceDiscovery/Main navigation|navigation]], it is located at ''Global navigation > Management > Configuration''. This link loads the page ''Special:BluespiceConfigManager.''<br />
<br />
==Layout==<br />
<br />
===Filter options===<br />
All settings can be accessed through the following filter options:<br />
<br />
*'''Feature:''' group by type of functionality the setting belongs to (search, administration...)<br />
*'''Extension:''' group by extension name<br />
*'''Package:''' group by BlueSpice edition and services (BlueSpice free, BlueSpice pro, Matomo)<br /><br />
[[File:Manual:ConfigManager2a.png|alt=config manager filters|center|thumb|401x401px|config manager filter]]<br />
<br />
<br />
All settings are available in any type of grouping. Changing the grouping type does not add or remove setting options. It just groups them differently. After settings are adjusted, they can be saved by clicking ''Save'', or cancelled by clicking ''Reset''.<br />
<br />
{{Messagebox|boxtype=note|Note text=If a server administrator has configured a setting to no longer be writable, it will be shown as greyed-out in the config manager. You will have to talk to your server administrator about changing such a setting.}}<br />
<br />
===Searching for settings===<br />
A search bar is located above the list of settings. Type in a keyword such as "logo" to find the corresponding setting. The search returns settings regardless of the currently selected group. {{Messagebox|boxtype=note|Note text=The search field has to be empty if you want to see the filter menu instead of the search.}}<br /><br />
[[File:Manual:configmanager-search.png|alt=Config manager search box|center|thumb|400x400px|Config manager search box]]<br />
<br />
==Settings by extension==<br />
<br />
=== EventBus ===<br />
Eventbus sends notifications to external urls in case something happens in the wiki. For example, if a page is created, an external service could then be started and create a pdf of that page. See the extension's page on [[mediawikiwiki:Extension:EventBus|mediawiki.org]].<br />
<br />
=== EnhancedUpload {{Bsvs|bsvFrom=4.3|bsvTo=|bsvFeature=}} ===<br />
Sets the defaults for the [[Manual:Extension/VisualEditor/Insert images#Advanced settings|advanced image settings]] when uploading and embedding an image into the wiki via drag-and-drop functionality. The default settings determine the orientation, type, and size of the image. These can be adjusted after embedding via the "Advanced settings" of the image on the page.<br />
<br />
===BlueSpiceFoundation===<br />
<br />
====Updating logo and favicon====<br />
{{Messagebox|boxtype=note|icon=|Note text=Since BlueSpice 4.2, the logo and favicon can also be managed via the page [[Manual:Extension/FlexiSkin|Special:Flexiskin]] together with further skin customizations.|bgcolor=}}<br />
*'''Logo path:''' The logo image should be stored in the /images folder of your installation. If you store it in the /skins folder of your BlueSpice installation, it could be overwritten with an upgrade.<br />
<br />
'''To upload the logo directly in the wiki:'''<br />
<br />
#'''Upload''' the logo on the page from the menu ''Global actions'' > ''File list'' (''Special:ExtendedFilelist''). <br />
#'''Click''' on the thumbnail image of the logo. This opens the logo on a separate page.<br />[[File:Manual:config-logo1.png|link=https://en.wiki.bluespice.com/wiki/File:Manual:config-logo1.png|alt=logo thumbnail image|center|thumb|280x280px|logo thumbnail image]]<br />
#'''Copy''' the relative logo path from the address bar. In a typical Wiki configuration, this path starts with ''/w/....'' .<br />[[File:Manual:config-logo2.png|alt=relative image path|center|thumb|450x450px|relative image path]]<br />
#'''Paste''' the logo path into the text field for the logo.<br />[[File:Manual:config-logo3.png|link=https://en.wiki.bluespice.com/wiki/File:Manual:config-logo3.png|alt=logo path|center|thumb|450x450px|logo path]]<br />
#'''Click''' ''Save''.<br />
#'''Refresh''' the page (Strg+F5). <br />If the uploaded logo is too large, you can add the following code snippet to the page ''MediaWiki:Common.css''. This automatically adjusts the image to the height of the main toolbar:<syntaxhighlight lang="css"><br />
.bs-logo a {background-size: contain;}<br />
</syntaxhighlight><br />
<br />
*'''Favicon path:''' The favicon image should be stored in the ''/images'' folder of your installation. If you store it in the /skins folder of your BlueSpice installation, it could be overwritten with an upgrade. [https://de.wikipedia.org/wiki/Favicon Favicon images] have the file extension ''.ico''.<br />
<br />
====System====<br />
<br />
*'''Allowed file extensions:''' For security reasons, the types of files that users can upload are restricted. Here, you can allow additional file formats. If a file format is blacklisted in the server configuration, adding this file extension here will not allow this file type to be uploaded. See [https://mediawikiwiki:Manual:$wgFileExtensions mediawiki.org/wiki/Manual:$wgFileExtensions] for more info.<br />
<br />
*'''Allowed image extensions:''' The standard web image types are listed here. In general, you want to restrict image uploads to web images. See [https://developer.mozilla.org/en-US/docs/Web/Media/Formats/Image_types developer.mozilla.org/en-US/docs/Web/Media/Formats/Image_types] for more on browser-supported image types.<br />
<br />
===BlueSpiceArticleInfo===<br />
''BlueSpiceArticleInfo'', together with ''[[Manual:Extension/BlueSpiceAuthors|BlueSpiceAuthors]], [[Manual:Extension/BlueSpiceReaders|BlueSpiceReaders]], and [[Manual:Extension/BlueSpiceExtendedSearch|BlueSpiceExtendedSearch]]'' is part of the ''Page information'' in the quality management tools.<br />
<br />
*'''Update interval in seconds:''' Sets the refresh rate for the "Last edit" value. By default, this date is updated every 10 seconds via JavaScript.<br />
[[File:Manual:ArticleInfo.png|link=link=Special:FilePath/ArticleInfo3.jpg|alt=|center|thumb|374x374px|article info]]<br />
<br />
===BlueSpiceAuthors===<br />
''BlueSpiceAuthors,'' together with ''[[Manual:Extension/BlueSpiceArticleInfo|BlueSpiceArticleInfo]]'' and ''BlueSpiceReaders'', is part of the ''Page information'' in the quality management tools.<br />
<br />
*'''Display authors:''' Show or hide authors on the page information page.<br />
[[File:Manual:PageInformation Authors.png|alt=|center|page=authors in page information|thumb|332x332px|Authors of page]]<br />
<br />
===BlueSpiceAvatars===<br />
[[File:Manual:configmanager-instantavatar.png|thumb|101x101px|InstantAvatar|link=Special:FilePath/Manual:configmanager-instantavatar.png]]<br />
An avatar image is automatically generated if the user does not upload a profile picture or if the user decides to create an avatar image in the preferences.<br />
<br />
*'''Generator'''<br />
**'''InstantAvatar:''' Generates an avatar image based on using the initials of the Real name or the Username<br />
**'''[[wikipedia:Identicon|Identicon:]]''' Generates an avatar image based on parts of the user's IP address.<br />[[File:Manual:configmanager-identicon.png|alt=Identicon|center|thumb|500x500px|Identicon]]<br />
<br />
===BlueSpiceBookshelf===<br />
<br />
*'''Show book chapter pager after content:''' Displays previous/next book page navigation at the end of each book page. (1)<br />
*'''Show book chapter pager before content:''' Displays previous/next book page navigation at the beginning of each book page. (2) <br />[[File:Manual:book-pagenav.png|alt=Book navigation|center|thumb|450x450px|Book navigation ]]<br /><br />
*'''Use the display title from book source on article:''' Shows the title from the book navigation as page title instead of the page name. <br /><br />
[[File:Manual:bookdisplaytitle.png|alt=book display title|center|thumb|450x450px|book display title]]<br />
{{Messagebox|boxtype=note|Note text=If the page additionally contains a <nowiki>{{DISPLAYTITLE}}</nowiki> tag, the display title of the page is shown instead of the book title.}}<br />
<br />
*'''Prepend article table of contents and headlines with book numberation:''' The page TOC does not start with the main heading 1, but with the actual number from the book chapter (see screenshot). If users have activated in their [[Manual:Preferences#Advanced options|user preferences]] to "auto-number headings", the numbering system is matched accordingly. [[File:prepand TOC with book chapter.png|alt=Prepended chapter numbers|center|thumb|650x650px|Prepended chapter numbers]]<br />
*'''Supress namespace prefix of book articles in output:''' The namespace prefix of an article is not shown in PDFs.<br />
<br />
===BlueSpiceChecklist===<br />
<br />
*'''Mark checklist changes as minor edit:''' If this setting is active, changes to a checklist (for example, checking a checkbox) in view mode are logged as minor edits. If this setting is inactive, a change to the checklist is recorded as a regular version in the page history.<br />[[File:Manual:configmanager-checklistminoredit.png|alt=minor edit|center|thumb|550x550px|minor edit]]<br />
<br />
===BlueSpiceExtendedSearch===<br />
<br />
*'''External file paths''': External locations to scan for and index files from. These locations are entered in key/value pairs of Physical path and URL prefix.<br />
**''Physical path: S''torage path. For mounted drives, for example: ''X:\Documents''<br />
**''URL prefix:'' All files indexed from the indexed physical location are prefixed in the search results. It should be used if files are available from a web server. By default, the URL prefix is set to the same value as ''Physical path''.<br />
<br />
<br />
{| class="wikitable" style="width:100%;"<br />
|+Examples for external file paths<br />
!Example file<br />
!Phys. Path<br />
!URL Prefix<br />
!Link in results list<br />
|-<br />
| rowspan="3" |S:\Sales\Info\glossaryy.pdf<br />
| rowspan="3" |S:\<br />
|<nowiki>file:///S:/</nowiki><br />
|<nowiki>file:///S:/Sales/Info/glossary.pdf</nowiki><br />
|-<br />
|<span class="mw-lingo-term" data-lingo-term-id="5e056c500a1c4b6a7110b50d807bade5" data-hasqtip="8">https</span>://sharepoint/Sales/<br />
documents/<br />
|<span class="mw-lingo-term" data-lingo-term-id="5e056c500a1c4b6a7110b50d807bade5" data-hasqtip="9">https</span>://sharepoint/Sales/<br />
documents/Sales/Info/glossary.pdf<br />
|-<br />
|<span class="mw-lingo-term" data-lingo-term-id="5e056c500a1c4b6a7110b50d807bade5" data-hasqtip="10">https</span>://intranet/showdocs<br />
inline.aspx?path=<br />
|<span class="mw-lingo-term" data-lingo-term-id="5e056c500a1c4b6a7110b50d807bade5" data-hasqtip="11">https</span>://intranet/showdocsinline.aspx?<br />
path=/Sales/Info/glossary.pdf<br />
|-<br />
|/var/www/bluespice/w/mounted_<br />
share/Sales/Info/glossary.pdf<br />
|/var/www/bluespice/w/<br />
mounted_share/<br />
|<br />
|<span class="mw-lingo-term" data-lingo-term-id="5e056c500a1c4b6a7110b50d807bade5" data-hasqtip="12">https</span>://wiki.company.local/w/mounted_<br />
share/Sales/Info/glossary.pdf<br />
|}<br />
[[File:Manual:configmanager-addfilepath.png|alt=Add an external file path|center|thumb|650x650px|Add an external file path: (1) confirm the checkmark and (2) save the settings.]]<br />
<br /><br />
<br />
*'''Use simple autocomplete:''' forces a more compact autocomplete (1-column Sales thumbnail preview).<br />[[File:Manual:configuration-autocomplete-simple.1575886540740.png|alt=compact autocomplete|center|thumb|450x450px|compact autocomplete]][[File:Manual:configuration-autocomplete-regular.1575886496796.png|alt=regular autocomplete|center|thumb|450x450px|Salesautocompletey]]<br /><br />
*'''Automatically set language filter''': This setting applies to multi-languages. It returns search results for a user only in the user's language. Users can set their language in their [[Manual:Preferences|preferences]].<br />
*'''Exclude patterns:''' Files at external file locations can be exluded from search based on regular expression patterns.<br />
<br />
===BlueSpiceExtendedStatistics===<br />
<br />
*'''Exclude these users:''' Some user groups, like WikiSysop can skew the statistics, for example the statistics for search queries or because they complete automated maintenance tasks. These types of user groups can be excluded from the statistical results.<br />
*'''Maximum number of interval steps:''' Sets the size of the x-axis for the results. For a few days, select the interval ''Day'' or ''Calendar Week'', for periods over one year, select ''Year'' or ''Month''. If you do not get any results for your query, try to adjust the interval accordingly.<br />
<br />
===BlueSpiceInsertCategory===<br />
<br />
*Insert category with its parent categories<br />
*Preset categories of a page in the upload dialog<br />
<br />
===BlueSpiceInsertLink===<br />
<br />
*'''Allow unmapped links<span class="col-red">:</span>''' if there is no prefix in the map, the link will still be inserted. Example: S:\HR. If this setting is unchecked, the link will not be inserted.<br />
*'''Allowed locations for external files''':<br />
{| class="wikitable" style="width:100%;"<br />
!Example file<br />
!Filesystem prefix<br />
!Web accessible Prefix<br />
!Link output<br />
|-<br />
| rowspan="3" |S:\Sales\Info\glossaryy.pdf<br />
| rowspan="3" |S:\<br />
|<nowiki>file:///S:/</nowiki><br />
|<nowiki>file:///S:/Sales/Info/glossary.pdf</nowiki><br />
|-<br />
|<span class="mw-lingo-term" data-lingo-term-id="5e056c500a1c4b6a7110b50d807bade5" data-hasqtip="8">https</span>://sharepoint/Sales/<br />
documents/<br />
|<span class="mw-lingo-term" data-lingo-term-id="5e056c500a1c4b6a7110b50d807bade5" data-hasqtip="9">https</span>://sharepoint/Sales/<br />
documents/Sales/Info/glossary.pdf<br />
|-<br />
|<span class="mw-lingo-term" data-lingo-term-id="5e056c500a1c4b6a7110b50d807bade5" data-hasqtip="10">https</span>://intranet/showdocs<br />
inline.aspx?path=<br />
|<span class="mw-lingo-term" data-lingo-term-id="5e056c500a1c4b6a7110b50d807bade5" data-hasqtip="11">https</span>://intranet/showdocsinline.aspx?<br />
path=/Sales/Info/glossary.pdf<br />
|-<br />
|/var/www/bluespice/w/mounted_<br />
share/Sales/Info/glossary.pdf<br />
|/var/www/bluespice/w/<br />
mounted_share/<br />
|<br />
|<span class="mw-lingo-term" data-lingo-term-id="5e056c500a1c4b6a7110b50d807bade5" data-hasqtip="12">https</span>://wiki.company.local/w/mounted_<br />
share/Sales/Info/glossary.pdf<br />
|}<br />
===BlueSpicePageTemplates===<br />
<br />
*'''Force target namespace:''' The page is always created in the target namespace that is associated with the template, even if the user provided a different namespace prefix. In the screenshot below, the user wants to create the page "NewPage" and then selects a template for the QM namespace. The page is, therefore, created as "QM:NewPage" if this setting is activated. [[File:force namespace from template.png|alt=force the namespace of the template|center|thumb|650x650px|force the namespace of the template]]<br />
<br />
*'''Hide default templates:''' Hides the default ''Empty page'' template.<br />
*'''Hide template if the page is not to be created in the target namespace:''' Depending on the namespace prefix of the page to be created, templates that are associated with other namespaces will not be shown to the user for selection.<br />
<br />
===BlueSpicePermissionManager===<br />
<br />
*'''Backup limit:''' Sets the number of backups for the permissions manager. Each time the page ''Special:PermissionManager'' is saved, a backup is created. If the backup limit is set to 5, the last five versions of the permissions configuration are saved as backups.<br />
<br />
===BlueSpiceRSSFeeder===<br />
<br />
*'''URL whitelist:''' RSS feeds need to be whitelisted here by an administrator before they can be displayed in a wiki page.<br />
*'''Maximum number of allowed redirects:''' If there are URL redirects for any of the whitelisted URLs, the number of redirects needs to be adjusted (usually to 1 or 2).<br />
<br />
[[File:Manual:configmanager-RSS.png|alt=RSS Feed settings|center|thumb|450x450px|RSS Feed settings]]<br />
<br /><br />
===BlueSpiceReaders ===<br />
<br />
*'''Number of readers to display:''' Sets the number of readers that are displayed on the Page information in the Quality management tools. <br />[[File:Manual:PageInformation Reader.png|link=link=Special:FilePath/Manual:configmanager-readers.png|alt=displays readers of the page|center|page=readers|thumb|displays readers of the page]]<br /><br />
<br />
=== BlueSpiceSaferEdit===<br />
<br />
*'''Interval for lookup for concurrent editings:''' Sets the time in seconds for checking if another person is editing the page.<br />
*'''Show name of current editor:''' Shows or hides the name of the user who is currently editing the page.<br />
<br />
===BlueSpiceUEModuleBookPDF===<br />
<br />
* Table of Contents<br />
**''Only article titles (indent by grade):'' Only shows the article titles in the main contents table of the PDF.<br />[[File:Manual:configmanager-toc-simple.png|alt=PDF table of contents without article TOCs|center|thumb|450x450px|PDF table of contents without article TOCs]]<br /><br />
**''Embed article TOCs (No indent of article titles):'' Shows the table of contents for each article in the main contents table of the PDF.[[File:Manual:configmanager-toc-embed.png|alt=Embed article TOCs|center|thumb|450x450px|Embed article TOCs]]<br />
<br />
===BlueSpiceUEModuleHTML===<br />
<br />
*'''Hide namespace prefix in HTML:''' If activated, the namespace is shown in the HTML main heading.<br />
{{Messagebox|boxtype=note|Note text=If the page contains a "displaytitle" tag in the page source, the page display title is shown and this setting has no effect.}}<br />
<br />
===BlueSpiceUEModulePDF===<br />
<br />
*'''Hide namespace prefix in PDF:''' If activated, the namespace is shown in the PDF main heading for a page.<br />
<br />
[[File:Manual:configmanager-pdfhidenamespace.png|alt=namespace in heading|center|thumb|450x450px|namespace in heading]]<br />
{{Messagebox|boxtype=note|Note text=If the page contains a "displaytitle" tag in the page source, the page display title is shown and this setting has no effect.}}<br />
<br />
===BlueSpiceUniversalExport===<br />
<br />
*<span class="oo-ui-fieldLayout-header">'''Metadata (standard, JSON):'''</span> Additional data to be passed to the rendering template in JSON format. This data can be used in the export template. The template itself is maintened server-side.<br />
*'''Metadata (override, JSON)''': Allows overriding standard data sent to the rendering template in JSON format. Values that are set by default can be overriden with this option.<br />
<br />
===BlueSpiceVisualEditorConnector===<br />
<br />
*'''<span class="col-red">Enable VisualEditor for BlueSpice extensions</span>'''<br />
*'''<span class="oo-ui-fieldLayout-header">Configuration variable to use a simplified save process</span>'''<br />
*'''Upload type'''<br />
**Original (Here a confirmation of the rights of use/upload is obtained, file name and namespace of the file can be changed, a category can be assigned and a description of the file <span class="col-red">MUST</span> be given).<br />
**Simple (No confirmation of required rights is obtained here, the name and namespace of the file can be changed, a description and a category can be assigned, but does not have to be specified)<br />
**One click (No confirmation about required rights is obtained here, the image cannot be renamed and no category can be assigned. Only the namespace can, but does not have to be adjusted before uploading) <!-- verify what one-click means, since the next screens appear. --><br /><br />
<br />
===BlueSpiceWhoIsOnline===<br />
<br />
*<span class="oo-ui-fieldLayout-header">'''Time in seconds until a user is marked as offline:'''</span> The system checks every ''x'' seconds if a user logged out and no longer displayed as online. This can be less frequent than the update inteval for newly logged-in users.<br />
*<span class="oo-ui-fieldLayout-header">'''Update interval in seconds:'''</span> The system checks every ''x'' seconds for users.<br />
<br />
===BlueSpiceExpiry===<br />
<br />
*'''<span class="oo-ui-fieldLayout-header">Show watermark for expired pages in PDF</span>:''' Shows the watermark for expired pages in PDFs.<br />
*<span class="oo-ui-fieldLayout-header">'''Show watermark for expired pages in print version:''' Shows the watermark for expired pages when a page is printed.</span><br />
*<span class="oo-ui-fieldLayout-header">'''Show watermark for expired pages'''</span>: Shows a watermark on the page itself.<br />[[File:Manual:configmanager-watermark.png|alt=watermark|center|thumb|250x250px|watermark]]<br />
<br />
===BlueSpiceFlaggedRevsConnector===<br />
{{BSVersion|bsvFrom=|bsvTo=4.2|bsvFeature=BlueSpiceFlaggedRevsConnector|text=It is replaced by [[#Content Stabilization]].}}<br />
'''Export'''<br />
<br />
The export settings affect how the pages of a book are generated in the PDF export.<br />
<br />
*'''<span class="oo-ui-fieldLayout-header">Bookshelf: List approved revisions log</span>:''' Shows a log of stable page versions of pages in the PDF and when these pages were put into accepted status. If editors did not provide a comment when accepting the page, the ''Stable comment'' field for a revision is empty. <br />[[File:Manual:configmanager-bookshelf-revisionslog.png|alt=accepted revisions log|center|thumb|450x450px|accepted revisions log]]<br /><br />
*'''Bookshelf: List pages without stable revision:''' Displays a list of PDF pages at the beginning of the PDF that only exist as a first draft and have no released version.[[File:configmanager-book-nichtfreigegebeneseiten-EN.png|center|thumb|300x300px|Pages without acceptance feature|link=Special:FilePath/configmanager-book-nichtfreigegebeneseiten-EN.png]]<br /><br />
*'''Bookshelf: List pages without FlaggedRevs:''' Displays a list of PDF pages that do not have a release mechanism at the beginning of the PDF.<br />
<br />
<br /><br />
[[File:Manual:configmanager-book-listnoflaggedrev.png|alt=Pages with no FlaggedRevs feature.|center|thumb|260x260px|Pages with no FlaggedRevs feature.]]<br />
<br /><br />
<br />
*<span class="oo-ui-fieldLayout-header">'''UEModulePDF: Show FlaggedRevs info below main heading'''</span>: Prints the latest revision dates (last acceptance and last edit date) below the heading. <br />[[File:Manual:configmanager-bookshelf-flaggedrevsinfo.png|alt=FlaggedRevs info below heading|center|thumb|350x350px|FlaggedRevs info below heading]]<br />
<br />
'''Quality assurance'''<br />
<br />
*'''Include handling:''' If resources are embedded in a page and those resources are located in namespaces with approval mechanism, then the following settings can be selected. For example: If an approved page contains a template or a file that has been changed after the page itself has been approved, the page will not get another draft version, but instead one of two configurations applies:<br />
**Current versions: Always show the latest version of the embedded resource.<br />
**Stable versions: Always show the stable (=approved) version of a resource. <br />
<br />
*<span class="oo-ui-fieldLayout-header">'''Show unstable pages for following groups:'''</span> If the group ''user'' is removed from the ''BlueSpiceFlaggedRevs'' configuration, users in this group will not be able to see draft versions when they are added as reviewers in a review process. When the group user is removed, only ''sysop'' and ''reviewer'' users can access drafts. If you want other groups, for example ''editor'', to see draft versions, you need to add them to the configuration. If no user groups are specified in the configuration field, not even reviewers and sysops users will see a visual status indication of a page. They will have access to drafts through the revision history for the page instead.<br />
<br />
'''Searching and Navigation'''<br />
<br />
*<span class="oo-ui-fieldLayout-header">'''Indexing only stable versions:''' Draft versions are excluded from the search results. If a page does not have a stable version, it is not shown as a search result.</span><span class="oo-ui-fieldLayout-field"><span id="bsgFlaggedRevsConnectorUEModulePDFShowFRTag" class="oo-ui-widget oo-ui-widget-enabled oo-ui-inputWidget oo-ui-checkboxInputWidget" aria-disabled="false" data-ooui><span class="oo-ui-checkboxInputWidget-checkIcon oo-ui-widget oo-ui-widget-enabled oo-ui-iconElement oo-ui-iconElement-icon oo-ui-icon-check oo-ui-iconWidget oo-ui-image-invert" aria-disabled="false"></span></span></span><span class="oo-ui-fieldLayout-field"><span id="bsgFlaggedRevsConnectorUEModulePDFShowFRTag" class="oo-ui-widget oo-ui-widget-enabled oo-ui-inputWidget oo-ui-checkboxInputWidget" aria-disabled="false" data-ooui><span class="oo-ui-checkboxInputWidget-checkIcon oo-ui-widget oo-ui-widget-enabled oo-ui-iconElement oo-ui-iconElement-icon oo-ui-icon-check oo-ui-iconWidget oo-ui-image-invert" aria-disabled="false"></span></span></span><br />
<br />
=== BlueSpiceSocial ===<br />
<br />
* '''Show entrypoint "Timeline":''' Shows a link to the page ''Special:Timeline'' in the main navigation.<br />
<br />
===BlueSpiceSocialBlog===<br />
<br />
*'''Use teaser text for blog entries in the timeline:''' When you create a blog entry, you can create a teaser text for it by clicking the cogwheel symbol in the blog entry form. If this setting is active, the teaser text will be shown on the page ''Special:Timeline'' instead of the first part of the content.<br />
<br />
<br />[[File:Manual:configmanager-blogteaser.png|center|thumb|380x380px|blog teaser text|link=Special:FilePath/Manual:configmanager-blogteaser.png]]<br />
<br />
* '''Show entrypoint "Blog":''' Shows a link to the page ''Special:Blog'' in the main navigation.<br />
<br />
===BlueSpiceSocialTopics===<br />
<br />
*'''Automatically create all discussion pages.''' If a user creates the first discussion topic for a page using the link in the page footer of a wiki page, the needed discussion page is automatically created first. <br />[[File:Manual:configmanager-socialtopics-create.png|alt=create discussion topic|center|thumb|350x350px|create discussion topic]]<br />A message "This discussion page was created automatically" is inserted on the discussion page. <br />[[File:Manual:configmanager-socialtopics.png|alt=automatically created discussion page|center|thumb|350x350px|automatically created discussion page]]<br /><br />
<br />
If this setting is deactivated, the user is directed to the "Create page" default page first.<br /><br />
<br />
== BlueSpiceDiscovery ==<br />
<br />
====Deactivating the Entrypoint links====<br />
[[File:discovery-entrypoint links.png|alt=Entrypoint links for Discovery skin|center|thumb|650x650px|Entrypoint links for Discovery skin]]<br />
<br />
====Positioning of skin elements====<br />
[[File:BlueSpice-Discovery2.png|alt=positioning skin elements|center|thumb|600x600px|positioning skin elements]]<br />
<br />
*page-sentence: display of page status ([[Manual:Extension/FlaggedRevs|Approval status]], [[Manual:Extension/BlueSpiceExpiry|Expiry]])<br />
*categories: display of [[:de:Handbuch:Kategorien_erstellen_und_nutzen|page categories]]<br />
<br />
*rating: display of [[Manual:Extension/BlueSpiceRating|page ratings]]<br />
<br />
*recommendations: display of [[Manual:Extension/BlueSpiceRating|page recommendations]]<br />
<br />
=== Content Stabilization{{bsvs|bsvFrom=4.3|bsvTo=|bsvFeature=}} ===<br />
The following configuration options are available for page approvals:<br />
[[Datei:Handbuch:config-contentstabilization.png|alt=Screenshot for approval settings|center|mini|650x650px|Settings for page approvals]]<br />
<br />
*'''Include handling (1):''' Wenn Ressourcen in eine Seite eingebettet sind '''und sich diese Ressourcen in Namensräumen mit Freigabe befinden''', können die folgenden Einstellungen ausgewählt werden. Es gibt zwei mögliche Einstellungen:<br />
<br />
{| class="wikitable" style="width:100%;" data-ve-attributes="{&quot;style&quot;:&quot;width:100%;&quot;}"<br />
! style="width:220px;" data-ve-attributes="{&quot;style&quot;:&quot;width:220px;&quot;}" |<br />
!Verhalten<br />
|-<br />
| style="width:220px;" data-ve-attributes="{&quot;style&quot;:&quot;width:220px;&quot;}" |<span class="col-red ve-pasteProtect">Stable versions of included pages</span><br />
|Shows the approved (stable) version of a resource, even if it was approved after the page that includes the resource was approved. (This works only if the resource is located in a namespace with active approval feature).<br />
|-<br />
| style="width:220px;" data-ve-attributes="{&quot;style&quot;:&quot;width:220px;&quot;}" |<span class="col-red ve-pasteProtect">Versions that were current at the time of approval</span><br />
|Shows the version of the resource which was embedded at the time of the last approval of the wiki page where it is embedded. (This works only if the resource is located in a namespace with active approval feature).<br />
|}For example, if an approved page contains a template that was modified after the page itself was approved, the page will not show a draft version. Approvals work directly via the embedded resource.<br />
<br />
*'''Allow viewing of first draft version (2):''' If this setting is activated, then all users with read rights can view the first draft. When disabled, only groups from the "Show unstable pages for following groups" setting can see first drafts.<br />
*'''Update semantic properties from stable pages only (3):''' The property value of the page is read from the stable version of the page and not from the draft version.<br />
<br />
*'''Entwurfsseiten für folgende Gruppen anzeigen (4):''' If the group <code>user</code> has been removed from the configuration, users in this group will not be able to see draft versions when they are added as reviewers in a review process. In this case, only users with the roles <code>sysop</code> and <code>reviewer</code> can access drafts unless other groups are specified. These system groups can only access drafts through the site's version history.<br />
{{translation}}<br />
[[Category:Administration]]</div>WikiSysophttps://en.wiki.bluespice.com/w/index.php?title=Setup:Installation_Guide/Optimization/Cronjobs&diff=6254Setup:Installation Guide/Optimization/Cronjobs2023-06-14T11:46:44Z<p>WikiSysop: </p>
<hr />
<div>{{DISPLAYTITLE:Cronjobs}}<br />
__TOC__<br />
<br />
<br />
This document describes cronjobs an related configurations, which should be set for your BlueSpice (depending on the used version).<br />
<br />
==Tips for this Document==<br />
{{Setup-document-note}}<br />
<br />
==runJobs.php==<br />
Time-consuming processes will be moved to a processing queue in the background of BlueSpice. With every page impression, a part of these will be processed. For the case that there are lots of processes in the queue and there are relatively litte page impressions, the tasks will not be processed promptly. <br />
<br />
For this reason, the queue should be processed regularly by cronjob. <br />
<br />
Now create a cronjob (Windows: "Scheduled task") depending on your operating system. The command to execute is:<br />
<br />
php <code>&lt;installpath-bluespice&gt;</code>/maintenance/runJobs.php ''(Linux)''<br />
php.exe <code>&lt;installpath-bluespice&gt;</code>\maintenance\runJobs.php ''(Windows)''<br />
<br />
{{Messagebox|boxtype=Hinweis|Note text=It is recommended to specify the complete path to php.exe under Windows. For more information, see the [[Setup:Installation_Guide/Services_and_system_configuration/Environment_Variables|environment variables]] document.}}<br />
Execute the cronjob every '''10 minutes'''. <br />
<br />
[[en:{{FULLPAGENAME}}]]<br />
[[de:Setup:Installationsanleitung/Optimierungen/Cronjobs]]</div>WikiSysophttps://en.wiki.bluespice.com/w/index.php?title=User:WikiSysop&diff=6227User:WikiSysop2023-06-06T14:41:00Z<p>WikiSysop: Undo revision 6224 by WikiSysop (talk)</p>
<hr />
<div>{{Userpage standard content}}</div>WikiSysophttps://en.wiki.bluespice.com/w/index.php?title=User:WikiSysop&diff=6226User:WikiSysop2023-06-06T14:40:33Z<p>WikiSysop: Undo revision 6225 by WikiSysop (talk)</p>
<hr />
<div>{{Userpage standard content}}<br />
<br />
{{#ask:[[Reference:+]][[Category:Extension]][[Revision ID::!27855]][[Modification date::+]] <br />
|?BSExtensionInfoDescription=Description<br />
|?BSExtensionInfoLicense=License<br />
|?BSExtensionInfoType=Maintainer<br />
|limit=9999<br />
}}</div>WikiSysophttps://en.wiki.bluespice.com/w/index.php?title=User:WikiSysop&diff=6225User:WikiSysop2023-06-06T14:36:06Z<p>WikiSysop: </p>
<hr />
<div>{{Userpage standard content}}<br />
<br />
{{#ask:[[Reference:+]][[Category:Extension]][[Revision ID::!27855]][[Modification date::+]] <br />
|?BSExtensionInfoDescription=Description<br />
|?BSExtensionInfoType=Maintainer<br />
|limit=9999<br />
}}</div>WikiSysophttps://en.wiki.bluespice.com/w/index.php?title=User:WikiSysop&diff=6224User:WikiSysop2023-06-06T14:34:52Z<p>WikiSysop: </p>
<hr />
<div>{{Userpage standard content}}<br />
<br />
{{#ask:[[Reference:+]][[Category:Extension]][[Revision ID::!27855]][[Modification date::+]] <br />
|?BSExtensionInfoDescription=Description<br />
|?BSExtensionInfoLicense=License<br />
|?BSExtensionInfoType=Maintainer<br />
|limit=9999<br />
}}</div>WikiSysophttps://en.wiki.bluespice.com/w/index.php?title=Setup:Installation_Guide/With_Installer&diff=6167Setup:Installation Guide/With Installer2023-05-24T08:25:43Z<p>WikiSysop: </p>
<hr />
<div>== Download installation package ==<br />
{{DISPLAYTITLE:Installation BlueSpice 4 with Installer}}<br />
<br />
{{Messagebox|boxtype=neutral|icon=yes|Note text=[https://bluespice.com/download/ Download the installation package] from the bluespice.com website.<br />
<br />
<br />
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.<br />
<br />
<br />
Make sure that [[Setup:Installation_Guide/Security_Settings/File_System_Permissions|file system permissions]] are set up properly.|bgcolor=}}<br />
==Introduction==<br />
BlueSpice 4 is installed as a complete package with MediaWiki 1.35 and BlueSpice 4.<br />
This installation guide gives you step-by-step instructions to install BlueSpice.<br />
<br />
{{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.<br />
<br />
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]].<br />
<br />
Further help on optimizing the operating system can be found in our [[Setup:Installation Guide/Advanced|compendium]].<br />
==Step-by-step installation==<br />
<br />
{{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!<br />
|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=}}<br />
<br />
First use your browser to call up the URL under which the web application can be reached. Then complete the following steps: <br />
{| class="wikitable" style=""<br />
|-<br />
|[[File:Setup:1.png|alt=MediaWiki setup page php error|300x300px]]<br />
||'''Step 1: Start the installation setup'''<br />
First, open the URL of your web application in your browser. Then click on "set up the wiki" to start the installation. <br />
<br />
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).<br />
<br />
|-<br />
|[[File:Setup:2.png|alt=Select language|300x300px]]<br />
||'''Step 2: Select your language'''<br />
You are now in the language selection.<br />
"Your language" defines the language that guides you through the installer,<br />
<br />
"Wiki language" the later language settings of your wiki.<br />
|-<br />
|[[File:Setup:3.png|alt=Installation check|300x300px]]<br />
||'''Step 3: MediaWiki installation check'''<br />
This step takes you to the MediaWiki installation check. <br />
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.<br />
Make the necessary corrections to your system and reload the page in your browser before proceeding with the setup.<br />
|-<br />
|[[File:Setup:4.png|alt=Database connection|300x300px]]<br />
||'''Step 4: Establish the database connection'''<br />
In this step, you configure the database connection. <br />
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. <br />
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]].<br />
|-<br />
|[[File:Setup:5.png|alt=Database user|300x300px]]<br />
||'''Step 5: Create the BlueSpice database user'''<br />
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".<br />
|-<br />
|[[File:Setup:6.png|alt=Wiki name and admin account|300x300px]]<br />
||'''Step 6: Create your wiki name and administrator account'''<br />
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.<br />
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.<br />
|-<br />
|[[File:Setup:7.png|alt=Email options|center|300x300px]]<br />
||'''Step 7: Options'''<br />
In this step, you specify the e-mail address for notification e-mails.<br />
|-<br />
|[[File:Setup:8.png|alt=|thumb]]<br />
||'''Step 8: Installation'''<br />
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.<br />
|-<br />
|[[File:Setup:9.png|alt=Installation status|center|300x300px]]<br />
||'''Step 9: Installation status'''<br />
After the successful installation of BlueSpice, you see a confirmation page that you confirm with "Next".<br />
|-<br />
|[[File:Setup:10.png|alt=Download localsettings.php|300x300px]]<br />
||'''Step 10: Download LocalSettings.php'''<br />
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.<br />
|-<br />
|<br />
|'''Step 11: Rename the template folders'''<br />
#Open the folder <code><installpath-bluespice>\extensions\BluesSpiceFoundation</code> and rename the subfolder <code>config.template</code> to <code>config</code> and create the new folder <code>data</code>. <span /><span /><span /><span /><span /><span /><br />These folders should have read and write access, see [[Setup:Installation Guide/Security Settings/File System Permissions|File System Permissions]]. <br /><span class="col-purple">Note: Since BlueSpice 4.3.0, <code>config.template</code> directory no longer exists, so step of renaming it should be skipped</span><br />
#Run <code>php <installpath-bluespic</code><span /><span /><span /><span /><span /><span /><code>e></code><span /><span /><span /><span /><span /><span /><span /><span /><span /><span /><span /><span /><code>\maintenance\update.php</code> from the console.<br />
|-<br />
|[[File:Setup:11.png|alt=BlueSpice start page|300x300px]]<br />
||'''Step 12: Load the BlueSpice welcome page'''<br />
If you now access the URL you specified for BlueSpice, you now see the BlueSpice welcome page. You can start using BlueSpice immediately.<br />
|}<br />
<br />
==BlueSpice WikiFarm==<br />
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.]]<br />
<br />
Now open a command line and change to the folder <code><installpath-bluespice></code>. <br />
<br />
Run the following command:<br />
<br />
*<code>php maintenance/update.php</code> ''(Linux)''<br />
*<code>php maintenance\update.php</code> ''(Windows)''<br />
==Next steps==<br />
{{Messagebox|boxtype=note|Note text=If the page is not loading, give the group "users" change-permissions for the folder C:\Windows\Temp.}}<br />
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:<br />
<br />
<span><span /><span /><span /><span /><span /><br /></span><br />
=Linux=<br />
In Apache, add the following entry to the file <code>000-bluespice.conf</code>:<br />
<pre><br />
<Directory /var/www/bluespice/w/mw-config><br />
Require all denied<br />
</Directory><br />
</pre><br />
<br />
<span><span /><span /><span /><span /><br /></span><br />
=Windows=<br />
In IIS, create a file <code>web.config</code> in the sub-directory <code>mw-config/</code> with the following content:<br />
<pre><br />
<?xml version="1.0" encoding="UTF-8"?><br />
<configuration><br />
<system.webServer><br />
<security><br />
<authentication><br />
<anonymousAuthentication enabled="false" /><br />
</authentication><br />
</security><br />
</system.webServer><br />
</configuration><br />
</pre><br />
<headertabs /><notabtoc/><br />
Please note that this entry may have to be removed temporarily if the web installer is used to update the application.<br />
<br />
{{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]].}}<br />
[[en:{{FULLPAGENAME}}]]<br />
[[de:Setup:Installationsanleitung/Installation von BlueSpice]]</div>WikiSysophttps://en.wiki.bluespice.com/w/index.php?title=Setup:Installation_Guide/With_Installer&diff=6166Setup:Installation Guide/With Installer2023-05-24T08:22:55Z<p>WikiSysop: </p>
<hr />
<div>== Download installation package ==<br />
{{DISPLAYTITLE:Installation BlueSpice 4 with Installer}}<br />
<br />
{{Messagebox|boxtype=neutral|icon=yes|Note text=[https://bluespice.com/download/ Download the installation package] from the bluespice.com website.<br />
<br />
<br />
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.<br />
<br />
<br />
Make sure that [[Setup:Installation_Guide/Security_Settings/File_System_Permissions|file system permissions]] are set up properly.|bgcolor=}}<br />
==Introduction==<br />
BlueSpice 4 is installed as a complete package with MediaWiki 1.35 and BlueSpice 4.<br />
This installation guide gives you step-by-step instructions to install BlueSpice.<br />
<br />
{{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.<br />
<br />
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]].<br />
<br />
Further help on optimizing the operating system can be found in our [[Setup:Installation Guide/Advanced|compendium]].<br />
==Step-by-step installation==<br />
<br />
{{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!<br />
|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=}}<br />
<br />
First use your browser to call up the URL under which the web application can be reached. Then complete the following steps: <br />
{| class="wikitable" style=""<br />
|-<br />
|[[File:Setup:1.png|alt=MediaWiki setup page php error|300x300px]]<br />
||'''Step 1: Start the installation setup'''<br />
First, open the URL of your web application in your browser. Then click on "set up the wiki" to start the installation. <br />
<br />
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).<br />
<br />
|-<br />
|[[File:Setup:2.png|alt=Select language|300x300px]]<br />
||'''Step 2: Select your language'''<br />
You are now in the language selection.<br />
"Your language" defines the language that guides you through the installer,<br />
<br />
"Wiki language" the later language settings of your wiki.<br />
|-<br />
|[[File:Setup:3.png|alt=Installation check|300x300px]]<br />
||'''Step 3: MediaWiki installation check'''<br />
This step takes you to the MediaWiki installation check. <br />
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.<br />
Make the necessary corrections to your system and reload the page in your browser before proceeding with the setup.<br />
|-<br />
|[[File:Setup:4.png|alt=Database connection|300x300px]]<br />
||'''Step 4: Establish the database connection'''<br />
In this step, you configure the database connection. <br />
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. <br />
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]].<br />
|-<br />
|[[File:Setup:5.png|alt=Database user|300x300px]]<br />
||'''Step 5: Create the BlueSpice database user'''<br />
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".<br />
|-<br />
|[[File:Setup:6.png|alt=Wiki name and admin account|300x300px]]<br />
||'''Step 6: Create your wiki name and administrator account'''<br />
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.<br />
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.<br />
|-<br />
|[[File:Setup:7.png|alt=Email options|center|300x300px]]<br />
||'''Step 7: Options'''<br />
In this step, you specify the e-mail address for notification e-mails.<br />
|-<br />
|[[File:Setup:8.png|alt=|thumb]]<br />
||'''Step 8: Installation'''<br />
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.<br />
|-<br />
|[[File:Setup:9.png|alt=Installation status|center|300x300px]]<br />
||'''Step 9: Installation status'''<br />
After the successful installation of BlueSpice, you see a confirmation page that you confirm with "Next".<br />
|-<br />
|[[File:Setup:10.png|alt=Download localsettings.php|300x300px]]<br />
||'''Step 10: Download LocalSettings.php'''<br />
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.<br />
|-<br />
|<br />
|'''Step 11: Rename the template folders'''<br />
#Open the folder <code><installpath-bluespice>\extensions\BluesSpiceFoundation</code> and rename the subfolder <code>config.template</code> to <code>config</code> and create the new folder <code>data</code>. <span /><span /><span /><span /><span /><span /><br />These folders should have read and write access, see [[Setup:Installation Guide/Security Settings/File System Permissions|File System Permissions]]. <br /><span class="col-purple">Note: Since BlueSpice 4.3 config.template directory no longer exists, so step of renaming it should be skipped</span><br />
#Run <code>php <installpath-bluespic</code><span /><span /><span /><span /><span /><span /><code>e></code><span /><span /><span /><span /><span /><span /><span /><span /><span /><span /><span /><span /><code>\maintenance\update.php</code> from the console.<br />
|-<br />
|[[File:Setup:11.png|alt=BlueSpice start page|300x300px]]<br />
||'''Step 12: Load the BlueSpice welcome page'''<br />
If you now access the URL you specified for BlueSpice, you now see the BlueSpice welcome page. You can start using BlueSpice immediately.<br />
|}<br />
<br />
==BlueSpice WikiFarm==<br />
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.]]<br />
<br />
Now open a command line and change to the folder <code><installpath-bluespice></code>. <br />
<br />
Run the following command:<br />
<br />
*<code>php maintenance/update.php</code> ''(Linux)''<br />
*<code>php maintenance\update.php</code> ''(Windows)''<br />
==Next steps==<br />
{{Messagebox|boxtype=note|Note text=If the page is not loading, give the group "users" change-permissions for the folder C:\Windows\Temp.}}<br />
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:<br />
<br />
<span><span /><span /><span /><span /><span /><br /></span><br />
=Linux=<br />
In Apache, add the following entry to the file <code>000-bluespice.conf</code>:<br />
<pre><br />
<Directory /var/www/bluespice/w/mw-config><br />
Require all denied<br />
</Directory><br />
</pre><br />
<br />
<span><span /><span /><span /><span /><br /></span><br />
=Windows=<br />
In IIS, create a file <code>web.config</code> in the sub-directory <code>mw-config/</code> with the following content:<br />
<pre><br />
<?xml version="1.0" encoding="UTF-8"?><br />
<configuration><br />
<system.webServer><br />
<security><br />
<authentication><br />
<anonymousAuthentication enabled="false" /><br />
</authentication><br />
</security><br />
</system.webServer><br />
</configuration><br />
</pre><br />
<headertabs /><notabtoc/><br />
Please note that this entry may have to be removed temporarily if the web installer is used to update the application.<br />
<br />
{{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]].}}<br />
[[en:{{FULLPAGENAME}}]]<br />
[[de:Setup:Installationsanleitung/Installation von BlueSpice]]</div>WikiSysophttps://en.wiki.bluespice.com/w/index.php?title=Setup:Installation_Guide/With_Installer&diff=6165Setup:Installation Guide/With Installer2023-05-24T08:22:33Z<p>WikiSysop: </p>
<hr />
<div>== Download installation package ==<br />
{{DISPLAYTITLE:Installation BlueSpice 4 with Installer}}<br />
<br />
{{Messagebox|boxtype=neutral|icon=yes|Note text=[https://bluespice.com/download/ Download the installation package] from the bluespice.com website.<br />
<br />
<br />
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.<br />
<br />
<br />
Make sure that [[Setup:Installation_Guide/Security_Settings/File_System_Permissions|file system permissions]] are set up properly.|bgcolor=}}<br />
==Introduction==<br />
BlueSpice 4 is installed as a complete package with MediaWiki 1.35 and BlueSpice 4.<br />
This installation guide gives you step-by-step instructions to install BlueSpice.<br />
<br />
{{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.<br />
<br />
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]].<br />
<br />
Further help on optimizing the operating system can be found in our [[Setup:Installation Guide/Advanced|compendium]].<br />
==Step-by-step installation==<br />
<br />
{{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!<br />
|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=}}<br />
<br />
First use your browser to call up the URL under which the web application can be reached. Then complete the following steps: <br />
{| class="wikitable" style=""<br />
|-<br />
|[[File:Setup:1.png|alt=MediaWiki setup page php error|300x300px]]<br />
||'''Step 1: Start the installation setup'''<br />
First, open the URL of your web application in your browser. Then click on "set up the wiki" to start the installation. <br />
<br />
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).<br />
<br />
|-<br />
|[[File:Setup:2.png|alt=Select language|300x300px]]<br />
||'''Step 2: Select your language'''<br />
You are now in the language selection.<br />
"Your language" defines the language that guides you through the installer,<br />
<br />
"Wiki language" the later language settings of your wiki.<br />
|-<br />
|[[File:Setup:3.png|alt=Installation check|300x300px]]<br />
||'''Step 3: MediaWiki installation check'''<br />
This step takes you to the MediaWiki installation check. <br />
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.<br />
Make the necessary corrections to your system and reload the page in your browser before proceeding with the setup.<br />
|-<br />
|[[File:Setup:4.png|alt=Database connection|300x300px]]<br />
||'''Step 4: Establish the database connection'''<br />
In this step, you configure the database connection. <br />
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. <br />
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]].<br />
|-<br />
|[[File:Setup:5.png|alt=Database user|300x300px]]<br />
||'''Step 5: Create the BlueSpice database user'''<br />
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".<br />
|-<br />
|[[File:Setup:6.png|alt=Wiki name and admin account|300x300px]]<br />
||'''Step 6: Create your wiki name and administrator account'''<br />
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.<br />
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.<br />
|-<br />
|[[File:Setup:7.png|alt=Email options|center|300x300px]]<br />
||'''Step 7: Options'''<br />
In this step, you specify the e-mail address for notification e-mails.<br />
|-<br />
|[[File:Setup:8.png|alt=|thumb]]<br />
||'''Step 8: Installation'''<br />
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.<br />
|-<br />
|[[File:Setup:9.png|alt=Installation status|center|300x300px]]<br />
||'''Step 9: Installation status'''<br />
After the successful installation of BlueSpice, you see a confirmation page that you confirm with "Next".<br />
|-<br />
|[[File:Setup:10.png|alt=Download localsettings.php|300x300px]]<br />
||'''Step 10: Download LocalSettings.php'''<br />
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.<br />
|-<br />
|<br />
|'''Step 11: Rename the template folders'''<br />
#Open the folder <code><installpath-bluespice>\extensions\BluesSpiceFoundation</code> and rename the subfolder <code>config.template</code> to <code>config</code> and create the new folder <code>data</code>. <span /><span /><span /><span /><span /><span /><br />These folders should have read and write access, see [[Setup:Installation Guide/Security Settings/File System Permissions|File System Permissions]]. <span class="col-purple">Note: Since BlueSpice 4.3 config.template directory no longer exists, so step of renaming it should be skipped</span><br />
#Run <code>php <installpath-bluespice></code><span /><span /><span /><span /><span /><span /><code>\maintenance\update.php</code> from the console.<br />
|-<br />
|[[File:Setup:11.png|alt=BlueSpice start page|300x300px]]<br />
||'''Step 12: Load the BlueSpice welcome page'''<br />
If you now access the URL you specified for BlueSpice, you now see the BlueSpice welcome page. You can start using BlueSpice immediately.<br />
|}<br />
<br />
==BlueSpice WikiFarm==<br />
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.]]<br />
<br />
Now open a command line and change to the folder <code><installpath-bluespice></code>. <br />
<br />
Run the following command:<br />
<br />
*<code>php maintenance/update.php</code> ''(Linux)''<br />
*<code>php maintenance\update.php</code> ''(Windows)''<br />
==Next steps==<br />
{{Messagebox|boxtype=note|Note text=If the page is not loading, give the group "users" change-permissions for the folder C:\Windows\Temp.}}<br />
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:<br />
<br />
<span><span /><span /><span /><span /><span /><br /></span><br />
=Linux=<br />
In Apache, add the following entry to the file <code>000-bluespice.conf</code>:<br />
<pre><br />
<Directory /var/www/bluespice/w/mw-config><br />
Require all denied<br />
</Directory><br />
</pre><br />
<br />
<span><span /><span /><span /><span /><br /></span><br />
=Windows=<br />
In IIS, create a file <code>web.config</code> in the sub-directory <code>mw-config/</code> with the following content:<br />
<pre><br />
<?xml version="1.0" encoding="UTF-8"?><br />
<configuration><br />
<system.webServer><br />
<security><br />
<authentication><br />
<anonymousAuthentication enabled="false" /><br />
</authentication><br />
</security><br />
</system.webServer><br />
</configuration><br />
</pre><br />
<headertabs /><notabtoc/><br />
Please note that this entry may have to be removed temporarily if the web installer is used to update the application.<br />
<br />
{{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]].}}<br />
[[en:{{FULLPAGENAME}}]]<br />
[[de:Setup:Installationsanleitung/Installation von BlueSpice]]</div>WikiSysophttps://en.wiki.bluespice.com/w/index.php?title=Manual:Extension/Page_Forms/Snippets&diff=6164Manual:Extension/Page Forms/Snippets2023-05-24T06:55:04Z<p>WikiSysop: </p>
<hr />
<div>== Providing input values from a (sub-) category ==<br />
=== Using input type "tree" ===<br />
(see official documentation: [[mediawikiwiki:Extension:Page_Forms/Input_types#tree|mediawiki.org/wiki/Extension:Page_Forms/Input_types#tree]] )<syntaxhighlight lang="text"><br />
{{{field|doctype|input type=tree|top category=Document type|depth=1|hideroot|list}}}<br />
</syntaxhighlight>Form display:<br />
[[File:PF tree.png|alt=screenshot of category tree with one value selected|none|thumb|Field type tree]]<br />
<br />
<br />
Example output of template parameter: <code>doctype=Process</code><br />
<br />
=== Using DPL query (dropdown) ===<br />
(Solution found at: https://www.mediawiki.org/wiki/Extension_talk:DynamicPageList3#Return_page_titles_as_plain_text?<syntaxhighlight lang="text"><br />
{{{field<br />
| doctype<br />
| input type=dropdown<br />
| values = {{#dpl: namespace = Category<br />
| category = Document type<br />
| mode = inline<br />
| format = ,¶%TITLE%,,<br />
| inlinetext = ,<br />
}}<br />
}}}<br />
</syntaxhighlight>Form field:<br />
[[File:PF-subcat-dpl.png|alt=screenshot of the dropdown result for the dpl3 solution|none|thumb|values provided by dpl3 parser function]]<br />
<br />
<br />
Example template output: <br />
<br />
<code>doctype=Process</code><br />
<br />
<br />
Using an SMW inline query<br />
<br />
<syntaxhighlight lang="text"><br />
{{{field|doctype|input type=dropdown|values={{#ask: [[Subcategory of::Document type]]|format=plainlist|sep=,|link=none|template=SMW Pagename}} }}}<br />
</syntaxhighlight>The above example uses the mapping template ''Template:SMW Pagename'' to avoid showing the namespace prefix "Category:" in the dropdown. Create the template with the following content:<syntaxhighlight lang="text"><br />
{{PAGENAME:{{{1|}}} }}<br />
</syntaxhighlight>Although the category prefix is then not shown in the dropdown, the value the form passes to its associated template parameter still includes the namespace prefix.<br />
<br />
Example template output:<br />
<br />
<code>doctype=Process</code><br />
=== Using an SMW concept ===<br />
Create the page Concept:Doctype with the following content:<syntaxhighlight lang="text"><br />
{{#concept:<br />
[[Subcategory of::Documenttype]][[Modification date::+]]<br />
|List of sub categories of the category Documenttype<br />
}}<br />
</syntaxhighlight>Use this concept as the source for the values of your field:<syntaxhighlight lang="text"><br />
{{{field|doctype|input type=dropdown|values from concept=doctype|mapping template=catConcept}}}<br />
</syntaxhighlight>The above example uses the mapping template ''Template:catConcept'' to avoid showing the namespace prefix "Category:" in the dropdown. Create the template with the following content:<syntaxhighlight lang="text"><br />
{{PAGENAME:{{{1|}}} }}<br />
</syntaxhighlight>Although the category prefix is then not shown in the dropdown, the value the form passes to its associated template parameter still includes the namespace prefix.<br />
<br />
Example template output:<br />
<br />
<code>doctype=Category:Process</code></div>WikiSysophttps://en.wiki.bluespice.com/w/index.php?title=Setup:Installation_Guide/System_Preparation/Linux/Apache_and_PHP&diff=6152Setup:Installation Guide/System Preparation/Linux/Apache and PHP2023-05-17T13:20:11Z<p>WikiSysop: </p>
<hr />
<div>{{DISPLAYTITLE:Installing Apache and PHP on Linux}}<br />
__TOC__<br />
{{Messagebox|boxtype=important|Note text=The web server delivers your BlueSpice installation to the user's browser. Without a web server, BlueSpice cannot be used. The source code of BlueSpice is based on the scripting language "PHP". This must also be installed on your server in order to operate BlueSpice. The steps listed here are required.}}<br />
==Introduction==<br />
Apache or Nginx are available as web servers under Linux. BlueSpice can theoretically also be operated with Nginx, but in this documentation only Apache is treated in detail. Of course, you can also install Nginx with the appropriate expertise and operate it according to the here documented Virtualhost configuration of Apache.<br />
{{Messagebox|boxtype=note|Note text=If "User is not in the sudoers file." type "su" in the terminal and execute. Write a "sudo" in front of a command.}}<br />
==Installation==<br />
Install Apache and PHP using the Aptitude package manager with the following steps:<br />
<pre><br />
apt update; \<br />
apt install apache2 \<br />
libapache2-mod-php7.4 \<br />
php7.4 \<br />
php7.4-cli \<br />
php7.4-common \<br />
php7.4-curl \<br />
php7.4-gd \<br />
php7.4-intl \<br />
php7.4-json \<br />
php7.4-mbstring \<br />
php7.4-mysql \<br />
php7.4-opcache \<br />
php7.4-tidy \<br />
php7.4-xml \<br />
php7.4-zip; \<br />
apt clean<br />
</pre>Depending on requirements, further PHP extensions may be necessary, e.g. for an LDAP connection.<br />
<br />
==Configuring PHP==<br />
After the installation has been completed, first configure PHP. First change to the directory <code>/etc/php/7.4/apache2</code> through the terminal and then execute the <code>php.ini</code> file with the command <code>nano php.ini.</code><br />
<br />
Find the following settings and change the values accordingly. If a setting is commented out with a semicolon in front of it, please remove it.<br />
<br />
<pre><br />
date.timezone = Europe/Berlin<br />
max_execution_time = 600<br />
post_max_size = 128M<br />
upload_max_filesize = 128M<br />
</pre><br />
<br />
Set the value for 'date.timezone' according to your own time zone.<br />
<br />
Save and exit the php.ini again.<br />
==Configuring Apache==<br />
{{Messagebox|boxtype=note|icon=|Note text=In this documentation, we assume the recommended installation with [https://www.mediawiki.org/wiki/Manual:Short_URL ShortURL]. In this case, the root directory of the web server is in <code>/var/www/bluespice</code>, but the actual source code of BlueSpice is in <code>/var/www/bluespice/w</code>. This configuration is designed accordingly.<br />
<br><br />
'''Multiple virtual hosts'''<br />
This guide applies to cases where BlueSpice is being installed on a dedicated server. If you have other virtual hosts configured, you may need to specify an alias for the <code>/w/</code> subfolder. Add the following to your Apache's http-specific configuration: <code>Alias /w/ /path/to/w/</code> (e.g., <code>Alias /w/ /var/www/html/example.com/w/</code>) <br />
<br />
|bgcolor=}}<br />
<br />
To configure a VirtualHost for BlueSpice, please proceed as follows:<br />
<br />
#Change to the directory <code>/etc/apache2/sites-available </code>.<br />
#In a text editor of your choice, open the file <code>bluespice.conf</code>, which does not yet exist, and create it. Copy the entire contents of the following file into this new configuration file:<br />
##For BlueSpice free: [[Media:Setup:apache vhost bluespice free.txt|apache_vhost_bluespice_free.txt]]<br />
##For BlueSpice pro: [[Media:Setup:apache vhost bluespice pro.txt|apache_vhost_bluespice_pro.txt]]<br />
#In rows 3 and 4, replace "SERVERNAME" and "SERVERALIAS" according to your server name and domain. If the server is explicitly operated with only one VirtualHost for BlueSpice, you can also completely remove these two lines.<br />
#Save the file and close it.<br />
<br />
<br />
<br />
Delete the VirtualHost created by default during the Apache installation with the command <code>a2dissite 000-default</code>. Then activate the just created VirtualHost with the command <code>a2ensite bluespice</code>.<br />
<br />
Next, activate the Module Rewrite, which we configured in the <code>bluespice.conf</code>, by entering the following command: <code>a2enmod rewrite</code><br />
<br />
Next, create the directory <code>/var/www/bluespice</code>(<code>mkdir/var/www/bluespice</code>) and restart Apache with the command <code>service apache2 restart</code>.<br />
<br />
Next, call up the URL of your BlueSpice server (localhost). If configured correctly, Apache should respond to the request with the error message "Not found", which is completely correct at the time of installation.<br />
<br />
[[File:Setup:apache_not_found.png|frameless]]<br />
<br />
==Next step==<br />
If you have successfully completed all these steps, you can proceed to the next step "[[Setup: Installation Guide/System Preparation/Linux/MariaDB | MariaDB]]".<br />
<br />
[[en:{{FULLPAGENAME}}]]<br />
[[de:Setup:Installationsanleitung/Systemvorbereitung/Linux/Apache_und_PHP]]</div>WikiSysophttps://en.wiki.bluespice.com/w/index.php?title=Setup:Installation_Guide/System_Preparation/Linux/Apache_and_PHP&diff=6151Setup:Installation Guide/System Preparation/Linux/Apache and PHP2023-05-17T13:14:36Z<p>WikiSysop: </p>
<hr />
<div>{{DISPLAYTITLE:Installing Apache and PHP on Linux}}<br />
__TOC__<br />
{{Messagebox|boxtype=important|Note text=The web server delivers your BlueSpice installation to the user's browser. Without a web server, BlueSpice cannot be used. The source code of BlueSpice is based on the scripting language "PHP". This must also be installed on your server in order to operate BlueSpice. The steps listed here are required.}}<br />
==Introduction==<br />
Apache or Nginx are available as web servers under Linux. BlueSpice can theoretically also be operated with Nginx, but in this documentation only Apache is treated in detail. Of course, you can also install Nginx with the appropriate expertise and operate it according to the here documented Virtualhost configuration of Apache.<br />
{{Messagebox|boxtype=note|Note text=If "User is not in the sudoers file." type "su" in the terminal and execute. Write a "sudo" in front of a command.}}<br />
==Installation==<br />
Install Apache and PHP using the Aptitude package manager with the following steps:<br />
<pre><br />
apt update; \<br />
apt install apache2 \<br />
libapache2-mod-php7.4 \<br />
php7.4 \<br />
php7.4-cli \<br />
php7.4-common \<br />
php7.4-curl \<br />
php7.4-gd \<br />
php7.4-intl \<br />
php7.4-json \<br />
php7.4-mbstring \<br />
php7.4-mysql \<br />
php7.4-opcache \<br />
php7.4-tidy \<br />
php7.4-xml \<br />
php7.4-zip; \<br />
apt clean<br />
</pre>Depending on requirements, further PHP extensions may be necessary, e.g. for an LDAP connection.<br />
<br />
==Configuring PHP==<br />
After the installation has been completed, first configure PHP. First change to the directory <code>/etc/php/7.4/apache2</code> through the terminal and then execute the <code>php.ini</code> file with the command <code>nano php.ini.</code><br />
<br />
Find the following settings and change the values accordingly. If a setting is commented out with a semicolon in front of it, please remove it.<br />
<br />
<pre><br />
date.timezone = Europe/Berlin<br />
max_execution_time = 600<br />
post_max_size = 128M<br />
upload_max_filesize = 128M<br />
</pre><br />
<br />
Set the value for 'date.timezone' according to your own time zone.<br />
<br />
Save and exit the php.ini again.<br />
==Configuring Apache==<br />
{{Messagebox|boxtype=note|icon=|Note text=In this documentation, we assume the recommended installation with [https://www.mediawiki.org/wiki/Manual:Short_URL ShortURL]. In this case, the root directory of the web server is in <code>/var/www/bluespice</code>, but the actual source code of BlueSpice is in <code>/var/www/bluespice/w</code>. This configuration is designed accordingly.<br />
<br><br />
'''Multiple virtual hosts'''<br />
This guide applies to cases where BlueSpice is being installed on a dedicated server. If you have other virtual hosts configured, you may need to specify an alias for the <code>/w/</code> subfolder by adding the following to your Apache's http-specific configuration: <code>Alias /w/ /path/to/w/</code>). <br />
<br />
|bgcolor=}}<br />
<br />
To configure a VirtualHost for BlueSpice, please proceed as follows:<br />
<br />
#Change to the directory <code>/etc/apache2/sites-available </code>.<br />
#In a text editor of your choice, open the file <code>bluespice.conf</code>, which does not yet exist, and create it. Copy the entire contents of the following file into this new configuration file:<br />
##For BlueSpice free: [[Media:Setup:apache vhost bluespice free.txt|apache_vhost_bluespice_free.txt]]<br />
##For BlueSpice pro: [[Media:Setup:apache vhost bluespice pro.txt|apache_vhost_bluespice_pro.txt]]<br />
#In rows 3 and 4, replace "SERVERNAME" and "SERVERALIAS" according to your server name and domain. If the server is explicitly operated with only one VirtualHost for BlueSpice, you can also completely remove these two lines.<br />
#Save the file and close it.<br />
<br />
<br />
<br />
Delete the VirtualHost created by default during the Apache installation with the command <code>a2dissite 000-default</code>. Then activate the just created VirtualHost with the command <code>a2ensite bluespice</code>.<br />
<br />
Next, activate the Module Rewrite, which we configured in the <code>bluespice.conf</code>, by entering the following command: <code>a2enmod rewrite</code><br />
<br />
Next, create the directory <code>/var/www/bluespice</code>(<code>mkdir/var/www/bluespice</code>) and restart Apache with the command <code>service apache2 restart</code>.<br />
<br />
Next, call up the URL of your BlueSpice server (localhost). If configured correctly, Apache should respond to the request with the error message "Not found", which is completely correct at the time of installation.<br />
<br />
[[File:Setup:apache_not_found.png|frameless]]<br />
<br />
==Next step==<br />
If you have successfully completed all these steps, you can proceed to the next step "[[Setup: Installation Guide/System Preparation/Linux/MariaDB | MariaDB]]".<br />
<br />
[[en:{{FULLPAGENAME}}]]<br />
[[de:Setup:Installationsanleitung/Systemvorbereitung/Linux/Apache_und_PHP]]</div>WikiSysophttps://en.wiki.bluespice.com/w/index.php?title=Setup:Installation_Guide/System_Preparation/Linux/Apache_and_PHP&diff=6150Setup:Installation Guide/System Preparation/Linux/Apache and PHP2023-05-17T12:58:47Z<p>WikiSysop: </p>
<hr />
<div>{{DISPLAYTITLE:Installing Apache and PHP on Linux}}<br />
__TOC__<br />
{{Messagebox|boxtype=important|Note text=The web server delivers your BlueSpice installation to the user's browser. Without a web server, BlueSpice cannot be used. The source code of BlueSpice is based on the scripting language "PHP". This must also be installed on your server in order to operate BlueSpice. The steps listed here are required.}}<br />
==Introduction==<br />
Apache or Nginx are available as web servers under Linux. BlueSpice can theoretically also be operated with Nginx, but in this documentation only Apache is treated in detail. Of course, you can also install Nginx with the appropriate expertise and operate it according to the here documented Virtualhost configuration of Apache.<br />
{{Messagebox|boxtype=note|Note text=If "User is not in the sudoers file." type "su" in the terminal and execute. Write a "sudo" in front of a command.}}<br />
==Installation==<br />
Install Apache and PHP using the Aptitude package manager with the following steps:<br />
<pre><br />
apt update; \<br />
apt install apache2 \<br />
libapache2-mod-php7.4 \<br />
php7.4 \<br />
php7.4-cli \<br />
php7.4-common \<br />
php7.4-curl \<br />
php7.4-gd \<br />
php7.4-intl \<br />
php7.4-json \<br />
php7.4-mbstring \<br />
php7.4-mysql \<br />
php7.4-opcache \<br />
php7.4-tidy \<br />
php7.4-xml \<br />
php7.4-zip; \<br />
apt clean<br />
</pre>Depending on requirements, further PHP extensions may be necessary, e.g. for an LDAP connection.<br />
<br />
==Configuring PHP==<br />
After the installation has been completed, first configure PHP. First change to the directory <code>/etc/php/7.4/apache2</code> through the terminal and then execute the <code>php.ini</code> file with the command <code>nano php.ini.</code><br />
<br />
Find the following settings and change the values accordingly. If a setting is commented out with a semicolon in front of it, please remove it.<br />
<br />
<pre><br />
date.timezone = Europe/Berlin<br />
max_execution_time = 600<br />
post_max_size = 128M<br />
upload_max_filesize = 128M<br />
</pre><br />
<br />
Set the value for 'date.timezone' according to your own time zone.<br />
<br />
Save and exit the php.ini again.<br />
==Configuring Apache==<br />
{{Messagebox|boxtype=note|Note text=In this documentation, we assume the recommended installation with [https://www.mediawiki.org/wiki/Manual:Short_URL ShortURL]. In this case, the root directory of the web server is in <code>/var/www/bluespice</code>, but the actual source code of BlueSpice is in <code>/var/www/bluespice/w</code>. This configuration is designed accordingly.<br />
<br><br />
'''Multiple virtual hosts'''<br />
This guide applies to cases where BlueSpice is being installed on a dedicated server. If you have other virtual hosts configured, you may need to specify an alias for the <code>/w/</code> subfolder (e.g., by using <code>Alias /w/ /path/to/w/</code>). <br />
<br />
}}<br />
<br />
To configure a VirtualHost for BlueSpice, please proceed as follows:<br />
<br />
#Change to the directory <code>/etc/apache2/sites-available </code>.<br />
#In a text editor of your choice, open the file <code>bluespice.conf</code>, which does not yet exist, and create it. Copy the entire contents of the following file into this new configuration file:<br />
##For BlueSpice free: [[Media:Setup:apache vhost bluespice free.txt|apache_vhost_bluespice_free.txt]]<br />
##For BlueSpice pro: [[Media:Setup:apache vhost bluespice pro.txt|apache_vhost_bluespice_pro.txt]]<br />
#In rows 3 and 4, replace "SERVERNAME" and "SERVERALIAS" according to your server name and domain. If the server is explicitly operated with only one VirtualHost for BlueSpice, you can also completely remove these two lines.<br />
#Save the file and close it.<br />
<br />
<br />
<br />
Delete the VirtualHost created by default during the Apache installation with the command <code>a2dissite 000-default</code>. Then activate the just created VirtualHost with the command <code>a2ensite bluespice</code>.<br />
<br />
Next, activate the Module Rewrite, which we configured in the <code>bluespice.conf</code>, by entering the following command: <code>a2enmod rewrite</code><br />
<br />
Next, create the directory <code>/var/www/bluespice</code>(<code>mkdir/var/www/bluespice</code>) and restart Apache with the command <code>service apache2 restart</code>.<br />
<br />
Next, call up the URL of your BlueSpice server (localhost). If configured correctly, Apache should respond to the request with the error message "Not found", which is completely correct at the time of installation.<br />
<br />
[[File:Setup:apache_not_found.png|frameless]]<br />
<br />
==Next step==<br />
If you have successfully completed all these steps, you can proceed to the next step "[[Setup: Installation Guide/System Preparation/Linux/MariaDB | MariaDB]]".<br />
<br />
[[en:{{FULLPAGENAME}}]]<br />
[[de:Setup:Installationsanleitung/Systemvorbereitung/Linux/Apache_und_PHP]]</div>WikiSysophttps://en.wiki.bluespice.com/w/index.php?title=Setup:Installation_Guide/System_Preparation/Linux/Apache_and_PHP&diff=6149Setup:Installation Guide/System Preparation/Linux/Apache and PHP2023-05-17T12:58:08Z<p>WikiSysop: </p>
<hr />
<div>{{DISPLAYTITLE:Installing Apache and PHP on Linux}}<br />
__TOC__<br />
{{Messagebox|boxtype=important|Note text=The web server delivers your BlueSpice installation to the user's browser. Without a web server, BlueSpice cannot be used. The source code of BlueSpice is based on the scripting language "PHP". This must also be installed on your server in order to operate BlueSpice. The steps listed here are required.}}<br />
==Introduction==<br />
Apache or Nginx are available as web servers under Linux. BlueSpice can theoretically also be operated with Nginx, but in this documentation only Apache is treated in detail. Of course, you can also install Nginx with the appropriate expertise and operate it according to the here documented Virtualhost configuration of Apache.<br />
{{Messagebox|boxtype=note|Note text=If "User is not in the sudoers file." type "su" in the terminal and execute. Write a "sudo" in front of a command.}}<br />
==Installation==<br />
Install Apache and PHP using the Aptitude package manager with the following steps:<br />
<pre><br />
apt update; \<br />
apt install apache2 \<br />
libapache2-mod-php7.4 \<br />
php7.4 \<br />
php7.4-cli \<br />
php7.4-common \<br />
php7.4-curl \<br />
php7.4-gd \<br />
php7.4-intl \<br />
php7.4-json \<br />
php7.4-mbstring \<br />
php7.4-mysql \<br />
php7.4-opcache \<br />
php7.4-tidy \<br />
php7.4-xml \<br />
php7.4-zip; \<br />
apt clean<br />
</pre>Depending on requirements, further PHP extensions may be necessary, e.g. for an LDAP connection.<br />
<br />
==Configuring PHP==<br />
After the installation has been completed, first configure PHP. First change to the directory <code>/etc/php/7.4/apache2</code> through the terminal and then execute the <code>php.ini</code> file with the command <code>nano php.ini.</code><br />
<br />
Find the following settings and change the values accordingly. If a setting is commented out with a semicolon in front of it, please remove it.<br />
<br />
<pre><br />
date.timezone = Europe/Berlin<br />
max_execution_time = 600<br />
post_max_size = 128M<br />
upload_max_filesize = 128M<br />
</pre><br />
<br />
Set the value for 'date.timezone' according to your own time zone.<br />
<br />
Save and exit the php.ini again.<br />
==Configuring Apache==<br />
{{Messagebox|boxtype=note|Note text=In this documentation, we assume the recommended installation with [https://www.mediawiki.org/wiki/Manual:Short_URL ShortURL]. In this case, the root directory of the web server is in <code>/var/www/bluespice</code>, but the actual source code of BlueSpice is in <code>/var/www/bluespice/w</code>. This configuration is designed accordingly.<br />
<br><br />
'''Multiple virtual hosts'''<br />
This guide applies to cases where BlueSpice is being installed on a dedicated server. If you have other virtual hosts configured, you may need to specify an alias for the <code>/w/</code> subfolder (e.g. by using <code>Alias /w/ /path/to/w/</code>). <br />
<br />
}}<br />
<br />
To configure a VirtualHost for BlueSpice, please proceed as follows:<br />
<br />
#Change to the directory <code>/etc/apache2/sites-available </code>.<br />
#In a text editor of your choice, open the file <code>bluespice.conf</code>, which does not yet exist, and create it. Copy the entire contents of the following file into this new configuration file:<br />
##For BlueSpice free: [[Media:Setup:apache vhost bluespice free.txt|apache_vhost_bluespice_free.txt]]<br />
##For BlueSpice pro: [[Media:Setup:apache vhost bluespice pro.txt|apache_vhost_bluespice_pro.txt]]<br />
#In rows 3 and 4, replace "SERVERNAME" and "SERVERALIAS" according to your server name and domain. If the server is explicitly operated with only one VirtualHost for BlueSpice, you can also completely remove these two lines.<br />
#Save the file and close it.<br />
<br />
<br />
<br />
Delete the VirtualHost created by default during the Apache installation with the command <code>a2dissite 000-default</code>. Then activate the just created VirtualHost with the command <code>a2ensite bluespice</code>.<br />
<br />
Next, activate the Module Rewrite, which we configured in the <code>bluespice.conf</code>, by entering the following command: <code>a2enmod rewrite</code><br />
<br />
Next, create the directory <code>/var/www/bluespice</code>(<code>mkdir/var/www/bluespice</code>) and restart Apache with the command <code>service apache2 restart</code>.<br />
<br />
Next, call up the URL of your BlueSpice server (localhost). If configured correctly, Apache should respond to the request with the error message "Not found", which is completely correct at the time of installation.<br />
<br />
[[File:Setup:apache_not_found.png|frameless]]<br />
<br />
==Next step==<br />
If you have successfully completed all these steps, you can proceed to the next step "[[Setup: Installation Guide/System Preparation/Linux/MariaDB | MariaDB]]".<br />
<br />
[[en:{{FULLPAGENAME}}]]<br />
[[de:Setup:Installationsanleitung/Systemvorbereitung/Linux/Apache_und_PHP]]</div>WikiSysophttps://en.wiki.bluespice.com/w/index.php?title=Setup:Installation_Guide/System_Preparation/Linux/Apache_and_PHP&diff=6148Setup:Installation Guide/System Preparation/Linux/Apache and PHP2023-05-17T12:57:51Z<p>WikiSysop: </p>
<hr />
<div>{{DISPLAYTITLE:Installing Apache and PHP on Linux}}<br />
__TOC__<br />
{{Messagebox|boxtype=important|Note text=The web server delivers your BlueSpice installation to the user's browser. Without a web server, BlueSpice cannot be used. The source code of BlueSpice is based on the scripting language "PHP". This must also be installed on your server in order to operate BlueSpice. The steps listed here are required.}}<br />
==Introduction==<br />
Apache or Nginx are available as web servers under Linux. BlueSpice can theoretically also be operated with Nginx, but in this documentation only Apache is treated in detail. Of course, you can also install Nginx with the appropriate expertise and operate it according to the here documented Virtualhost configuration of Apache.<br />
{{Messagebox|boxtype=note|Note text=If "User is not in the sudoers file." type "su" in the terminal and execute. Write a "sudo" in front of a command.}}<br />
==Installation==<br />
Install Apache and PHP using the Aptitude package manager with the following steps:<br />
<pre><br />
apt update; \<br />
apt install apache2 \<br />
libapache2-mod-php7.4 \<br />
php7.4 \<br />
php7.4-cli \<br />
php7.4-common \<br />
php7.4-curl \<br />
php7.4-gd \<br />
php7.4-intl \<br />
php7.4-json \<br />
php7.4-mbstring \<br />
php7.4-mysql \<br />
php7.4-opcache \<br />
php7.4-tidy \<br />
php7.4-xml \<br />
php7.4-zip; \<br />
apt clean<br />
</pre>Depending on requirements, further PHP extensions may be necessary, e.g. for an LDAP connection.<br />
<br />
==Configuring PHP==<br />
After the installation has been completed, first configure PHP. First change to the directory <code>/etc/php/7.4/apache2</code> through the terminal and then execute the <code>php.ini</code> file with the command <code>nano php.ini.</code><br />
<br />
Find the following settings and change the values accordingly. If a setting is commented out with a semicolon in front of it, please remove it.<br />
<br />
<pre><br />
date.timezone = Europe/Berlin<br />
max_execution_time = 600<br />
post_max_size = 128M<br />
upload_max_filesize = 128M<br />
</pre><br />
<br />
Set the value for 'date.timezone' according to your own time zone.<br />
<br />
Save and exit the php.ini again.<br />
==Configuring Apache==<br />
{{Messagebox|boxtype=note|Note text=In this documentation, we assume the recommended installation with [https://www.mediawiki.org/wiki/Manual:Short_URL ShortURL]. In this case, the root directory of the web server is in <code>/var/www/bluespice</code>, but the actual source code of BlueSpice is in <code>/var/www/bluespice/w</code>. This configuration is designed accordingly.<br><br />
<br />
'''Multiple virtual hosts'''<br />
This guide applies to cases where BlueSpice is being installed on a dedicated server. If you have other virtual hosts configured, you may need to specify an alias for the <code>/w/</code> subfolder (e.g. by using <code>Alias /w/ /path/to/w/</code>). <br />
<br />
}}<br />
<br />
To configure a VirtualHost for BlueSpice, please proceed as follows:<br />
<br />
#Change to the directory <code>/etc/apache2/sites-available </code>.<br />
#In a text editor of your choice, open the file <code>bluespice.conf</code>, which does not yet exist, and create it. Copy the entire contents of the following file into this new configuration file:<br />
##For BlueSpice free: [[Media:Setup:apache vhost bluespice free.txt|apache_vhost_bluespice_free.txt]]<br />
##For BlueSpice pro: [[Media:Setup:apache vhost bluespice pro.txt|apache_vhost_bluespice_pro.txt]]<br />
#In rows 3 and 4, replace "SERVERNAME" and "SERVERALIAS" according to your server name and domain. If the server is explicitly operated with only one VirtualHost for BlueSpice, you can also completely remove these two lines.<br />
#Save the file and close it.<br />
<br />
<br />
<br />
Delete the VirtualHost created by default during the Apache installation with the command <code>a2dissite 000-default</code>. Then activate the just created VirtualHost with the command <code>a2ensite bluespice</code>.<br />
<br />
Next, activate the Module Rewrite, which we configured in the <code>bluespice.conf</code>, by entering the following command: <code>a2enmod rewrite</code><br />
<br />
Next, create the directory <code>/var/www/bluespice</code>(<code>mkdir/var/www/bluespice</code>) and restart Apache with the command <code>service apache2 restart</code>.<br />
<br />
Next, call up the URL of your BlueSpice server (localhost). If configured correctly, Apache should respond to the request with the error message "Not found", which is completely correct at the time of installation.<br />
<br />
[[File:Setup:apache_not_found.png|frameless]]<br />
<br />
==Next step==<br />
If you have successfully completed all these steps, you can proceed to the next step "[[Setup: Installation Guide/System Preparation/Linux/MariaDB | MariaDB]]".<br />
<br />
[[en:{{FULLPAGENAME}}]]<br />
[[de:Setup:Installationsanleitung/Systemvorbereitung/Linux/Apache_und_PHP]]</div>WikiSysophttps://en.wiki.bluespice.com/w/index.php?title=Site:Privacy_policy&diff=6147Site:Privacy policy2023-05-17T12:24:39Z<p>WikiSysop: Created blank page</p>
<hr />
<div></div>WikiSysophttps://en.wiki.bluespice.com/w/index.php?title=Site:Terms_of_service&diff=6146Site:Terms of service2023-05-17T12:24:33Z<p>WikiSysop: Created blank page</p>
<hr />
<div></div>WikiSysophttps://en.wiki.bluespice.com/w/index.php?title=Community&diff=6145Community2023-05-17T12:24:26Z<p>WikiSysop: </p>
<hr />
<div>{{Banner|banner-image=pexels-jeffrey-czum-2346289.jpg|image-width=300|imagealign=|banner-title=Community|titlesize=|titlecolor=|banner-text=Be part of the community and exchange your knowledge about wikis and BlueSpice!|textsize=|textcolor=|contentpadding=20px 40px|boxpadding=10px|boxbgcolor=}}<br />
<br /><br />
<div class="sectionflex col3"><br />
<div><br />
== Email Support ==<br />
<center><br />
<span class="bi bi-envelope-open-fill bi-big"></span><br />
<br /><br />
<br />
Contact us by email at<br />
<br /><br />
[mailto:support@hallowelt.com support@hallowelt.com]<br />
</center><br />
</div><br />
<div><br />
== Support forums ==<br />
<center><br />
<span class="bi bi-chat-dots-fill bi-big"></span><br />
<br /><br />
<br />
[http://sourceforge.net/tracker/?func=add&group_id=358032&atid=1494709 Sourceforge bug report]<br />
<br /><br />
[http://sourceforge.net/p/bluespice/discussion/1249668 Sourceforge help forum]<br />
</center><br />
</div><br />
<div><br />
== Newsletter ==<br />
<center><br />
<span class="bi bi-newspaper bi-big"></span><br />
<br /><br />
<br />
[https://bluespice.com/newsletter Subscribe to our newsletter. <br />We send 1-2 mails per month.]<br />
</center><br />
</div><br />
<div><br />
== Social Media ==<br />
<center><br />
<span class="bi bi-facebook bi-big"></span> <span class="bi bi-twitter bi-big"></span><br />
<br /><br />
[https://www.facebook.com/BlueSpice.MediaWiki Contact us via Facebook]<br />
<br /><br />
[https://twitter.com/BlueSpiceTweets Follow us on Twitter!]<br />
</center><br />
</div><br />
<div><br />
== YouTube ==<br />
<center><br />
<span class="bi bi-youtube bi-big"></span><br />
<br /><br />
[https://www.youtube.com/user/BlueSpiceVideo Leave a comment on our videos. <br />We appreciate it!]<br />
</center><br />
</div><br />
<div><br />
== Participate! ==<br />
<center><br />
<span class="bi bi-laptop-fill bi-big"></span><br />
<br /><br />
[[How to become a BlueSpice hacker|BlueSpice hackers wanted!]]<br />
</center><br />
</div><br />
</div><br />
<br />
__NODISCUSSION__<br />
__HIDETITLE__<br />
__NOTOC__<br />
[[de:{{FULLPAGENAME}}]]<br />
[[en:Community]]</div>WikiSysophttps://en.wiki.bluespice.com/w/index.php?title=Setup:Installation_Guide/System_Preparation/Linux/Apache_and_PHP&diff=6144Setup:Installation Guide/System Preparation/Linux/Apache and PHP2023-05-17T11:45:36Z<p>WikiSysop: </p>
<hr />
<div>{{DISPLAYTITLE:Installing Apache and PHP on Linux}}<br />
__TOC__<br />
{{Messagebox|boxtype=important|Note text=The web server delivers your BlueSpice installation to the user's browser. Without a web server, BlueSpice cannot be used. The source code of BlueSpice is based on the scripting language "PHP". This must also be installed on your server in order to operate BlueSpice. The steps listed here are required.}}<br />
==Introduction==<br />
Apache or Nginx are available as web servers under Linux. BlueSpice can theoretically also be operated with Nginx, but in this documentation only Apache is treated in detail. Of course, you can also install Nginx with the appropriate expertise and operate it according to the here documented Virtualhost configuration of Apache.<br />
{{Messagebox|boxtype=note|Note text=If "User is not in the sudoers file." type "su" in the terminal and execute. Write a "sudo" in front of a command.}}<br />
==Installation==<br />
Install Apache and PHP using the Aptitude package manager with the following steps:<br />
<pre><br />
apt update; \<br />
apt install apache2 \<br />
libapache2-mod-php7.4 \<br />
php7.4 \<br />
php7.4-cli \<br />
php7.4-common \<br />
php7.4-curl \<br />
php7.4-gd \<br />
php7.4-intl \<br />
php7.4-json \<br />
php7.4-mbstring \<br />
php7.4-mysql \<br />
php7.4-opcache \<br />
php7.4-tidy \<br />
php7.4-xml \<br />
php7.4-zip; \<br />
apt clean<br />
</pre>Depending on requirements, further PHP extensions may be necessary, e.g. for an LDAP connection.<br />
<br />
==Configuring PHP==<br />
After the installation has been completed, first configure PHP. First change to the directory <code>/etc/php/7.4/apache2</code> through the terminal and then execute the <code>php.ini</code> file with the command <code>nano php.ini.</code><br />
<br />
Find the following settings and change the values accordingly. If a setting is commented out with a semicolon in front of it, please remove it.<br />
<br />
<pre><br />
date.timezone = Europe/Berlin<br />
max_execution_time = 600<br />
post_max_size = 128M<br />
upload_max_filesize = 128M<br />
</pre><br />
<br />
Set the value for 'date.timezone' according to your own time zone.<br />
<br />
Save and exit the php.ini again.<br />
==Configuring Apache==<br />
{{Messagebox|boxtype=note|Note text=In this documentation, we assume the recommended installation with [https://www.mediawiki.org/wiki/Manual:Short_URL ShortURL]. In this case, the root directory of the web server is in <code>/var/www/bluespice</code>, but the actual source code of BlueSpice is in <code>/var/www/bluespice/w</code>. This configuration is designed accordingly.}}<br />
<br />
To configure a VirtualHost for BlueSpice, please proceed as follows:<br />
<br />
#Change to the directory <code>/etc/apache2/sites-available </code>.<br />
#In a text editor of your choice, open the file <code>bluespice.conf</code>, which does not yet exist, and create it. Copy the entire contents of the following file into this new configuration file:<br />
##For BlueSpice free: [[Media:Setup:apache vhost bluespice free.txt|apache_vhost_bluespice_free.txt]]<br />
##For BlueSpice pro: [[Media:Setup:apache vhost bluespice pro.txt|apache_vhost_bluespice_pro.txt]]<br />
#In rows 3 and 4, replace "SERVERNAME" and "SERVERALIAS" according to your server name and domain. If the server is explicitly operated with only one VirtualHost for BlueSpice, you can also completely remove these two lines.<br />
#Save the file and close it.<br />
<br />
This guide applies to cases where BlueSpice is being installed on a dedicated server. If you have other virtual hosts configured, you may need to specify an alias for the <code>/w/</code> subfolder (e.g. by using <code>Alias /w/ /path/to/w/</code>). <br />
<br />
Delete the VirtualHost created by default during the Apache installation with the command <code>a2dissite 000-default</code>. Then activate the just created VirtualHost with the command <code>a2ensite bluespice</code>.<br />
<br />
Next, activate the Module Rewrite, which we configured in the <code>bluespice.conf</code>, by entering the following command: <code>a2enmod rewrite</code><br />
<br />
Next, create the directory <code>/var/www/bluespice</code>(<code>mkdir/var/www/bluespice</code>) and restart Apache with the command <code>service apache2 restart</code>.<br />
<br />
Next, call up the URL of your BlueSpice server (localhost). If configured correctly, Apache should respond to the request with the error message "Not found", which is completely correct at the time of installation.<br />
<br />
[[File:Setup:apache_not_found.png|frameless]]<br />
<br />
==Next step==<br />
If you have successfully completed all these steps, you can proceed to the next step "[[Setup: Installation Guide/System Preparation/Linux/MariaDB | MariaDB]]".<br />
<br />
[[en:{{FULLPAGENAME}}]]<br />
[[de:Setup:Installationsanleitung/Systemvorbereitung/Linux/Apache_und_PHP]]</div>WikiSysophttps://en.wiki.bluespice.com/w/index.php?title=Reference:MenuEditor&diff=5785Reference:MenuEditor2023-04-11T11:04:17Z<p>WikiSysop: </p>
<hr />
<div>{{BSExtensionInfo<br />
|status=stable<br />
|developer=HalloWelt<br />
|type=BlueSpice<br />
|edition=BlueSpice pro, BlueSpice free, BlueSpice Farm, BlueSpice Cloud<br />
|compatible=BlueSpice<br />
|category=Content Structuring<br />
|license=GPL v3 only<br />
|features={{BSVersion|bsvFrom=4.2|bsvTo=|bsvFeature=}}<br />
*Graphical user interface allows editing of the left sidebar as well as the user menu via drag and drop<br />
<br />
}}<br />
{{wcagCheck}}<br />
{{translation}}</div>WikiSysophttps://en.wiki.bluespice.com/w/index.php?title=AutoDoc:MenuEditor&diff=5784AutoDoc:MenuEditor2023-04-11T11:03:27Z<p>WikiSysop: Created page with "==DescriptionMsg== {{AutoDocDescriptionMsg |name = MenuEditor |desc = {{int:menueditor-desc }} }} ==License== {{AutoDocLicense |name = GPL-3.0-only }} ==Requirements== {{AutoD..."</p>
<hr />
<div>==DescriptionMsg==<br />
{{AutoDocDescriptionMsg<br />
|name = MenuEditor<br />
|desc = {{int:menueditor-desc<br />
}}<br />
}}<br />
==License==<br />
{{AutoDocLicense<br />
|name = GPL-3.0-only<br />
}}<br />
==Requirements==<br />
{{AutoDocRequirements<br />
|mediawiki = {{AutoDocVersion<br />
|name = MediaWiki<br />
|version = 1.35.0<br />
}}<br />
}}<br />
==IntegratesInto==<br />
{{AutoDocIntegratesInto<br />
|into = {{AutoDocListItem<br />
|item = MenuEditor<br />
}}<br />
}}<br />
==Hooks==<br />
{{AutoDocHooks<br />
|Hooks = {{AutoDocCallback<br />
|name = [https://www.mediawiki.org/wiki/Manual:Hooks/BeforeInitialize BeforeInitialize]<br />
|callback = initializeMenus<br />
}}<br />
{{AutoDocCallback<br />
|name = [https://www.mediawiki.org/wiki/Manual:Hooks/BlueSpiceDiscoveryTemplateDataProviderAfterInit BlueSpiceDiscoveryTemplateDataProviderAfterInit]<br />
|callback = editActions<br />
}}<br />
{{AutoDocCallback<br />
|name = [https://www.mediawiki.org/wiki/Manual:Hooks/MediaWikiPerformAction MediaWikiPerformAction]<br />
|callback = editActions<br />
}}<br />
{{AutoDocCallback<br />
|name = [https://www.mediawiki.org/wiki/Manual:Hooks/SkinTemplateNavigation::Universal SkinTemplateNavigation::Universal]<br />
|callback = editActions<br />
}}<br />
}}</div>WikiSysophttps://en.wiki.bluespice.com/w/index.php?title=Reference:MenuEditor&diff=5783Reference:MenuEditor2023-04-11T11:02:12Z<p>WikiSysop: </p>
<hr />
<div>{{BSExtensionInfo<br />
|status=stable<br />
|developer=HalloWelt<br />
|type=BlueSpice<br />
|edition=BlueSpice pro, BlueSpice free, BlueSpice Farm, BlueSpice Cloud<br />
|compatible=BlueSpice<br />
|category=Content Structuring<br />
|license=GPL v3 only<br />
|features=<div class="hw-messagebox notification-bsversion icon"> is available from BlueSpice [[bsvFrom::4.2]] </div><span></span><br />
*Graphical user interface allows editing of the left sidebar as well as the user menu via drag and drop<br />
*Allows to embed the name of a wiki page, external links as well as interwiki links<br />
}}<br />
{{wcagCheck}}<br />
{{translation}}</div>WikiSysophttps://en.wiki.bluespice.com/w/index.php?title=Reference:MenuEditor&diff=5782Reference:MenuEditor2023-04-11T11:00:07Z<p>WikiSysop: </p>
<hr />
<div>{{BSExtensionInfo<br />
|status=stable<br />
|developer=HalloWelt<br />
|type=BlueSpice<br />
|edition=BlueSpice free, BlueSpice pro, BlueSpice Farm, BlueSpice Cloud<br />
|compatible=BlueSpice<br />
|category=Inhaltliche Strukturierung<br />
|license=GPL v3 only<br />
|features=<br />
{{BSVersion|bsvFrom=4.2|bsvTo=|bsvFeature=}}<br />
* Graphical user interface allows editing of the left sidebar as well as the user menu via drag and drop<br />
* Allows to embed the name of a wiki page, external links as well as interwiki links<br />
}}<br />
<br />
<br />
<br />
{{translation}}</div>WikiSysophttps://en.wiki.bluespice.com/w/index.php?title=Sandbox2&diff=5562Sandbox22023-02-20T09:05:31Z<p>WikiSysop: (username removed) (log details removed)</p>
<hr />
<div>==ASK==<br />
{{#ask:[[Category:Administration]]<br />
|format=table<br />
|?Category<br />
}}<br />
<br />
Eine Auswahl von standardmäßig integrierten Inhaltselementen - so hauchen Sie dem Wiki Leben ein!<br />
Wechseln Sie in den <span class="plainlinks">[{{fullurl:{{FULLPAGENAME}}|action=edit}} Bearbeitungsmodus]</span>, um die Seite selbst zu bearbeiten. .<br />
<br />
<div id="use_cases"><br />
==PDF Handler==<br />
[[File:Manual:Manual Wikitext Wikitext reference.pdf|thumb|alt=|283x283px]]<br />
<br />
<span><span /><span /><br /></span><br />
<br />
<span><span /><br /></span><br />
<br />
<span><span /><br /></span><br />
<br />
<span><span /><br /></span><br />
<br />
<span><span /><br /></span><br />
<br />
== Image preview ==<br />
[[File:Insert files 2.png|none|thumb]]<br />
<br />
==Tabellen==<br />
<br />
<span><span /><span /><br /></span><br />
Tabellen haben praktische Filter- und Sortiermöglichkeiten. Zum Filtern und Sortieren können Benutzer im Ansichtsmodus auf die jeweilige Kopfzeile einer Spalte klicken. Diese Funktion steht im Bearbeitungsmodus nicht zur Verfügung. Beispiel einer filterbaren Tabelle:<span /><span /><span /><br /><br />
{| class="wikitable sortable" style="width:100%;"<br />
!Funktion!!Wert<br />
|-<br />
|Filterbare Tabelle||funktioniert<br />
|-<br />
|Kategoriencheck||nicht vorhanden<br />
|-<br />
|Sortierbare Tabelle<br />
|funktioniert<br />
|}<br />
==<span class="bi bi-diagram-3-fill"></span> Diagramme / Infografiken==<br />
<br />
<span><span /><span /><br /></span><br />
Ablaufdiagramme, Organigramme, Prozesslandkarten, BPMN-Diagramme und mehr. Hier als Beispiel eine Infografik, erstellt mit dem eingebunden drawio-Tool:<br />
<br />
<bs:drawio filename="Sandkasten-11346612" /><br />
==<span class="bi bi-camera-video"></span> Videos==<br />
<br />
<span><br /></span><br />
Video geht natürlich auch. Egal, ob es direkt im Wiki gespeichert ist oder ob es auf einem gängigen Video-Service läuft. Hier ein Video, das ins Demowiki hochgeladen wurde:<br />
==<span class="bi bi-list-ul"></span> Seitenlisten==<br />
<br />
<span><span /><span /><br /></span><br />
<br />
Mit der integrierten Erweiterung ''Smartlist'' lassen sich ganz leicht Seitenlisten erstellen. <smartlist new="false" count="7" trim="false" /><br />
<br />
==<span class="bi bi-input-cursor-text"></span> Inputbox==<br />
<br />
Inputboxen sind praktische Werkzeuge, um neue Seiten in bestimmte Namensräume (Wikibereiche) zu lenken. Eine Seite, die Sie hier anlegen, wird im Namensraum IMS gespeichert:<inputbox><br />
type=create<br />
prefix=IMS:<br />
break=no<br />
width=30<br />
buttonlabel=Seite erstellen<br />
</inputbox><br />
<span /><span /><span /><br /><br />
==<span class="bi bi-code-slash"></span> Codebeispiele dokumentieren==<br />
<br />
<span><span /><span /><br /></span><br />
<br />
Code läßt sich übersichtlich über die enthaltene Erweiterung ''SyntaxHighlight'' darstellen:<syntaxhighlight lang="php" line="1"><br />
<?php<br />
echo "Hallo Welt";<br />
?><br />
</syntaxhighlight><br />
<br />
==<span class="bi bi-rss"></span> RSS-Feed==<br />
<br />
<span><span /><span /><br /></span><br />
Hier ein Feed aus Bluespice.com. Mit oder ohne Beschreibung formatierbar.<rss max="4" highlight="MediaWiki BlueSpice">https://blog.bluespice.com/feed/</rss><br />
<br />
==<span class="bi bi-emoji-smile"></span> Emoticons==<br />
<br />
<span><span /><span /><br /></span><br />
Weil sie immer noch Spaß machen. Smileys sind mit an Bord.<br />
<br />
Hello :-)<br />
<span /><span /><span /><br /><br />
==<span class="bi bi-calculator"></span> CountThings==<br />
<br />
<span><span /><span /><br /></span><br />
<bs:countcharacters mode="words">SmokeTest</bs:countcharacters><br />
==<span class="bi bi-diagram-2"></span> Kategorienbaum==<br />
<br />
<span><span /><span /><br /></span><br />
Der Kategorienbaum zeigt die Kategorienhierarchie - mal mit, mal ohne die zugehörigen Seiten. Ganz wie Sie wollen...<br />
<categorytree>Produkt</categorytree><br />
==<span class="bi bi-cloud"></span> Tag Cloud==<br />
<br />
<span><span /><span /><br /></span><br />
Welche Kategorie wächst am schnellsten? Mit einer TagCloud sehe ich es auf den ersten Blick.<br />
<br />
<bs:tagcloud width="98%" float="left" count="10" renderer="text" store="category" showcount="true" minsize="5" maxsize="30" exclude="Pages with syntax highlighting errors, Pages with borken file links, Pages with RSS feeds, Pages with broken file links" /><br />
<br />
<span /><span /><span /><br /><br />
==<span class="bi bi-calendar-week"></span> Widgets==<br />
<br />
<span><span /><span /><br /></span><br />
Iframes, Google Kalendar, Wetteranzeige und mehr. Oder eigene Widgets entwickeln. test<br />
<br />
{{#widget:Weather}}<br />
</div><br />
<br />
== Math ==<br />
<br />
<math>\sum_{n=1}^\infty \frac 1{n^3}=\frac{\pi^2}{5}</math><br />
<br />
<span><span /><span /><br /></span><br />
<br />
[[de:Seitenentwurf:Sandkasten]] <br />
[[en:{{FULLPAGENAME}}]]</div>WikiSysophttps://en.wiki.bluespice.com/w/index.php?title=Sandbox2&diff=5561Sandbox22023-02-20T09:04:52Z<p>WikiSysop: Created page with "==ASK== {{#ask:Category:Administration |format=table |?Category }} Eine Auswahl von standardmäßig integrierten Inhaltselementen - so hauchen Sie dem Wiki Leben ein! Wec..."</p>
<hr />
<div>==ASK==<br />
{{#ask:[[Category:Administration]]<br />
|format=table<br />
|?Category<br />
}}<br />
<br />
Eine Auswahl von standardmäßig integrierten Inhaltselementen - so hauchen Sie dem Wiki Leben ein!<br />
Wechseln Sie in den <span class="plainlinks">[{{fullurl:{{FULLPAGENAME}}|action=edit}} Bearbeitungsmodus]</span>, um die Seite selbst zu bearbeiten. .<br />
<br />
<div id="use_cases"><br />
==PDF Handler==<br />
[[File:Manual:Manual Wikitext Wikitext reference.pdf|thumb|alt=|283x283px]]<br />
<br />
<span><span /><span /><br /></span><br />
<br />
<span><span /><br /></span><br />
<br />
<span><span /><br /></span><br />
<br />
<span><span /><br /></span><br />
<br />
<span><span /><br /></span><br />
<br />
== Image preview ==<br />
[[File:Insert files 2.png|none|thumb]]<br />
<br />
==Tabellen==<br />
<br />
<span><span /><span /><br /></span><br />
Tabellen haben praktische Filter- und Sortiermöglichkeiten. Zum Filtern und Sortieren können Benutzer im Ansichtsmodus auf die jeweilige Kopfzeile einer Spalte klicken. Diese Funktion steht im Bearbeitungsmodus nicht zur Verfügung. Beispiel einer filterbaren Tabelle:<span /><span /><span /><br /><br />
{| class="wikitable sortable" style="width:100%;"<br />
!Funktion!!Wert<br />
|-<br />
|Filterbare Tabelle||funktioniert<br />
|-<br />
|Kategoriencheck||nicht vorhanden<br />
|-<br />
|Sortierbare Tabelle<br />
|funktioniert<br />
|}<br />
==<span class="bi bi-diagram-3-fill"></span> Diagramme / Infografiken==<br />
<br />
<span><span /><span /><br /></span><br />
Ablaufdiagramme, Organigramme, Prozesslandkarten, BPMN-Diagramme und mehr. Hier als Beispiel eine Infografik, erstellt mit dem eingebunden drawio-Tool:<br />
<br />
<bs:drawio filename="Sandkasten-11346612" /><br />
==<span class="bi bi-camera-video"></span> Videos==<br />
<br />
<span><br /></span><br />
Video geht natürlich auch. Egal, ob es direkt im Wiki gespeichert ist oder ob es auf einem gängigen Video-Service läuft. Hier ein Video, das ins Demowiki hochgeladen wurde:<br />
==<span class="bi bi-list-ul"></span> Seitenlisten==<br />
<br />
<span><span /><span /><br /></span><br />
<br />
Mit der integrierten Erweiterung ''Smartlist'' lassen sich ganz leicht Seitenlisten erstellen. <smartlist new="false" count="7" trim="false" /><br />
<br />
==<span class="bi bi-input-cursor-text"></span> Inputbox==<br />
<br />
Inputboxen sind praktische Werkzeuge, um neue Seiten in bestimmte Namensräume (Wikibereiche) zu lenken. Eine Seite, die Sie hier anlegen, wird im Namensraum IMS gespeichert:<inputbox><br />
type=create<br />
prefix=IMS:<br />
break=no<br />
width=30<br />
buttonlabel=Seite erstellen<br />
</inputbox><br />
<span /><span /><span /><br /><br />
==<span class="bi bi-code-slash"></span> Codebeispiele dokumentieren==<br />
<br />
<span><span /><span /><br /></span><br />
<br />
Code läßt sich übersichtlich über die enthaltene Erweiterung ''SyntaxHighlight'' darstellen:<syntaxhighlight lang="php" line="1"><br />
<?php<br />
echo "Hallo Welt";<br />
?><br />
</syntaxhighlight><br />
<br />
==<span class="bi bi-rss"></span> RSS-Feed==<br />
<br />
<span><span /><span /><br /></span><br />
Hier ein Feed aus Bluespice.com. Mit oder ohne Beschreibung formatierbar.<rss max="4" highlight="MediaWiki BlueSpice">https://blog.bluespice.com/feed/</rss><br />
<br />
==<span class="bi bi-emoji-smile"></span> Emoticons==<br />
<br />
<span><span /><span /><br /></span><br />
Weil sie immer noch Spaß machen. Smileys sind mit an Bord.<br />
<br />
Hello :-)<br />
<span /><span /><span /><br /><br />
==<span class="bi bi-calculator"></span> CountThings==<br />
<br />
<span><span /><span /><br /></span><br />
<bs:countcharacters mode="words">SmokeTest</bs:countcharacters><br />
==<span class="bi bi-diagram-2"></span> Kategorienbaum==<br />
<br />
<span><span /><span /><br /></span><br />
Der Kategorienbaum zeigt die Kategorienhierarchie - mal mit, mal ohne die zugehörigen Seiten. Ganz wie Sie wollen...<br />
<categorytree>Produkt</categorytree><br />
==<span class="bi bi-cloud"></span> Tag Cloud==<br />
<br />
<span><span /><span /><br /></span><br />
Welche Kategorie wächst am schnellsten? Mit einer TagCloud sehe ich es auf den ersten Blick.<br />
<br />
<bs:tagcloud width="98%" float="left" count="10" renderer="text" store="category" showcount="true" minsize="5" maxsize="30" exclude="Pages with syntax highlighting errors, Pages with borken file links, Pages with RSS feeds, Pages with broken file links" /><br />
<br />
<span /><span /><span /><br /><br />
==<span class="bi bi-calendar-week"></span> Widgets==<br />
<br />
<span><span /><span /><br /></span><br />
Iframes, Google Kalendar, Wetteranzeige und mehr. Oder eigene Widgets entwickeln. test<br />
<br />
{{#widget:Weather}}<br />
</div><br />
<br />
== Math ==<br />
<br />
<math>\sum_{n=1}^\infty \frac 1{n^3}=\frac{\pi^2}{5}</math><br />
<br />
<span><span /><span /><br /></span><br />
<br />
[[de:Seitenentwurf:Sandkasten]] <br />
[[en:{{FULLPAGENAME}}]]</div>WikiSysophttps://en.wiki.bluespice.com/w/index.php?title=File:Sandkasten-11346612.drawio.png&diff=5559File:Sandkasten-11346612.drawio.png2023-02-20T09:02:06Z<p>WikiSysop: (username removed) (log details removed)</p>
<hr />
<div></div>WikiSysophttps://en.wiki.bluespice.com/w/index.php?title=File:Setup:apache_vhost_bluespice_free.txt&diff=3147File:Setup:apache vhost bluespice free.txt2022-04-08T06:49:09Z<p>WikiSysop: (username removed) (log details removed)</p>
<hr />
<div></div>WikiSysophttps://en.wiki.bluespice.com/w/index.php?title=File:Setup:apache_vhost_bluespice_pro.txt&diff=3146File:Setup:apache vhost bluespice pro.txt2022-04-08T06:48:42Z<p>WikiSysop: (username removed) (log details removed)</p>
<hr />
<div></div>WikiSysophttps://en.wiki.bluespice.com/w/index.php?title=Setup:Installation_Guide/System_Preparation/Linux/Apache_and_PHP&diff=3145Setup:Installation Guide/System Preparation/Linux/Apache and PHP2022-04-08T06:43:55Z<p>WikiSysop: </p>
<hr />
<div>{{DISPLAYTITLE:Installing Apache and PHP on Linux}}<br />
__TOC__<br />
{{Messagebox|boxtype=important|Note text=The web server delivers your BlueSpice installation to the user's browser. Without a web server, BlueSpice cannot be used. The source code of BlueSpice is based on the scripting language "PHP". This must also be installed on your server in order to operate BlueSpice. The steps listed here are required.}}<br />
==Introduction==<br />
Apache or Nginx are available as web servers under Linux. BlueSpice can theoretically also be operated with Nginx, but in this documentation only Apache is treated in detail. Of course, you can also install Nginx with the appropriate expertise and operate it according to the here documented Virtualhost configuration of Apache.<br />
{{Messagebox|boxtype=note|Note text=If "User is not in the sudoers file." type "su" in the terminal and execute. Write a "sudo" in front of a command.}}<br />
==Installation==<br />
Install Apache and PHP using the Aptitude package manager with the following steps:<br />
<pre><br />
apt update; \<br />
apt install apache2 \<br />
libapache2-mod-php7.4 \<br />
php7.4 \<br />
php7.4-cli \<br />
php7.4-common \<br />
php7.4-curl \<br />
php7.4-gd \<br />
php7.4-intl \<br />
php7.4-json \<br />
php7.4-mbstring \<br />
php7.4-mysql \<br />
php7.4-opcache \<br />
php7.4-tidy \<br />
php7.4-xml \<br />
php7.4-zip; \<br />
apt clean<br />
</pre><br />
==Configuring PHP==<br />
After installation, configure PHP. Open <code>php.ini</code> with a text editor of your choice (nano, vi), which, in our Debian version, is located in the directory <code>/etc/php/7.3/apache2</code>.<br />
<br />
Find the following settings and change the values accordingly. If a setting is commented out with a semicolon in front of it, please remove it. Or open the terminal with <code>sudo nano /etc/php/7.4/apache2/php.ini</code>.<br />
<br />
<pre><br />
date.timezone = Europe/Berlin<br />
max_execution_time = 600<br />
post_max_size = 128M<br />
upload_max_filesize = 128M<br />
</pre><br />
<br />
Set the value for 'date.timezone' according to your own time zone.<br />
<br />
Save and exit the php.ini again.<br />
==Configuring Apache==<br />
{{Messagebox|boxtype=note|Note text=In this documentation, we assume the recommended installation with [https://www.mediawiki.org/wiki/Manual:Short_URL ShortURL]. In this case, the root directory of the web server is in <code>/var/www/bluespice</code>, but the actual source code of BlueSpice is in <code>/var/www/bluespice/w</code>. This configuration is designed accordingly.}}<br />
<br />
To configure a VirtualHost for BlueSpice, please proceed as follows:<br />
<br />
#Change to the directory <code>/etc/apache2/sites-available </code>.<br />
#In a text editor of your choice, open the file <code>bluespice.conf</code>, which does not yet exist, and create it. Copy the entire contents of the following file into this new configuration file:<br />
##For BlueSpice free: [[Media:Setup:apache vhost bluespice free.txt|apache_vhost_bluespice_free.txt]]<br />
##For BlueSpice pro: [[Media:Setup:apache vhost bluespice pro.txt|apache_vhost_bluespice_pro.txt]]<br />
#In rows 3 and 4, replace "SERVERNAME" and "SERVERALIAS" according to your server name and domain. If the server is explicitly operated with only one VirtualHost for BlueSpice, you can also completely remove these two lines.<br />
#Save the file and close it.<br />
<br />
'''If you do not have rights to save:'''<br />
<br />
#Open a text editor of your choice.<br />
#Copy the complete contents of the following file into this new configuration file.<br />
##For BlueSpice free: [[Media:Setup:apache vhost bluespice free.txt|apache_vhost_bluespice_free.txt]]<br />
##For BlueSpice pro: [[Media:Setup:apache vhost bluespice pro.txt|apache_vhost_bluespice_pro.txt]]<br />
#In rows 3 and 4, replace "SERVERNAME" and "SERVERALIAS" according to your server name and domain. If the server is explicitly operated with only one VirtualHost for BlueSpice, you can also completely remove these two lines.<br />
#Save the file as <code>bluespice.conf</code> under any file path and exit it.<br />
#In terminal, run the command <code>sudo mv /yourfilepath/bluespice.conf /etc/apache2/sites-available</code>.<br />
<br />
Delete the VirtualHost created by default during the Apache installation with the command <code>a2dissite 000-default</code>. Then activate the just created VirtualHost with the command <code>a2ensite bluespice</code>.<br />
<br />
Next, activate the Module Rewrite, which we configured in the <code>bluespice.conf</code>, by entering the following command: <code>a2enmod rewrite</code><br />
<br />
Next, create the directory <code>/var/www/bluespice</code>(<code>mkdir/var/www/bluespice</code>) and restart Apache with the command <code>service apache2 restart</code>.<br />
<br />
Next, call up the URL of your BlueSpice server. If configured correctly, Apache should respond to the request with the error message "Not found", which is completely correct at the time of installation.<br />
<br />
[[File:Setup:apache_not_found.png|frameless]]<br />
<br />
==Next step==<br />
If you have successfully completed all these steps, you can proceed to the next step "[[Setup: Installation Guide/System Preparation/Linux/MariaDB | MariaDB]]".<br />
<br />
[[en:{{FULLPAGENAME}}]]<br />
[[de:Setup:Installationsanleitung/Systemvorbereitung/Linux/Apache_und_PHP]]</div>WikiSysophttps://en.wiki.bluespice.com/w/index.php?title=Setup:Installation_Guide/System_Preparation/Linux&diff=3144Setup:Installation Guide/System Preparation/Linux2022-04-08T06:43:07Z<p>WikiSysop: </p>
<hr />
<div>**[[Setup:Installation Guide/System Preparation/Linux/Introduction|Introduction]]<br />
**[[Setup:Installation Guide/System Preparation/Linux/Apache_and_PHP|Apache and PHP]]<br />
**[[Setup:Installation Guide/System Preparation/Linux/MariaDB|MariaDB]]<br />
**[[Setup:Installation Guide/System Preparation/Linux/Jetty|Jetty]]<br />
**[[Setup:Installation Guide/System Preparation/Linux/Elasticsearch|Elasticsearch]]<br />
**[[Setup:Installation Guide/System Preparation/Linux/Python|Python]]<br />
**[[Setup:Installation Guide/System Preparation/Linux/Memcached|Memcached]]<br />
**[[Setup:Installation Guide/System Preparation/Linux/Texvc|Texvc]] '''(BlueSpice pro only)'''<br />
**[[Setup:Installation Guide/System Preparation/Linux/PhantomJS|PhantomJS]] '''(BlueSpice pro only)'''<br />
<br />
<br />
[[en:{{FULLPAGENAME}}]][[de:Setup:Installationsanleitung/Systemvorbereitung/Linux]]</div>WikiSysophttps://en.wiki.bluespice.com/w/index.php?title=File:Sandkasten-11346612.drawio.png&diff=2082File:Sandkasten-11346612.drawio.png2022-01-18T15:15:19Z<p>WikiSysop: </p>
<hr />
<div></div>WikiSysophttps://en.wiki.bluespice.com/w/index.php?title=SocialEntity:187&diff=2080SocialEntity:1872022-01-18T15:02:03Z<p>WikiSysop: </p>
<hr />
<div>{<br />
"wikipageid": 1184,<br />
"namespace": 0,<br />
"titletext": "Sandbox",<br />
"description": "",<br />
"parentid": 0,<br />
"id": 187,<br />
"ownerid": 1,<br />
"type": "wikipage",<br />
"archived": false,<br />
"tags": [<br />
"Sandbox"<br />
],<br />
"resolved": false<br />
}</div>WikiSysophttps://en.wiki.bluespice.com/w/index.php?title=SocialEntity:89&diff=1551SocialEntity:892021-12-20T16:15:58Z<p>WikiSysop: </p>
<hr />
<div>{<br />
"wikipageid": 890,<br />
"namespace": 0,<br />
"titletext": "Manual:Extension/Workflows",<br />
"description": "",<br />
"parentid": 0,<br />
"id": 89,<br />
"ownerid": 1,<br />
"type": "wikipage",<br />
"archived": false,<br />
"tags": [<br />
"Manual:Extension/Workflows"<br />
],<br />
"resolved": false<br />
}</div>WikiSysophttps://en.wiki.bluespice.com/w/index.php?title=Manual:Extension/Workflows&diff=1550Manual:Extension/Workflows2021-12-20T16:15:57Z<p>WikiSysop: Created page with "==Einleitung== Workflows basieren in BlueSpice 4.1 auf BPMN 2.0. Vier verschiedene Arten von seitenbasierten Workflows sind bereits..."</p>
<hr />
<div>==Einleitung==<br />
Workflows basieren in BlueSpice 4.1 auf [[:de:Business_Process_Model_and_Notation|BPMN 2.0]]. Vier verschiedene Arten von seitenbasierten Workflows sind bereits integriert. Ihr Zweck ist es, eine Seite begutachten zu lassen und über eine Abstimmung ein Feedback einzuholen oder eine Seitenfreigabe auszulösen. Im folgenden werden diese Workflows daher Begutachtungen genannt.<br />
<br />
{| class="wikitable" style="width:100%;"<br />
|+Arten von Begutachtungen<br />
! style="width:300px;" |Workflow-Typ<br />
! style="width:100px;" |Beteiligte<br />
!Beschreibung<br />
|-<br />
| style="width:300px;" |'''[[Manual:Extension/Workflows#Single user approval|Single user approval]]'''<br />
| style="width:100px;" |1 Benutzer<br />
|Ein einzelner Benutzer wird aufgefordert, über eine Seite abzustimmen. Am Ende wird bei einer "Zustimmung" des Begutachters die Seite automatisch freigegeben.<br />
|-<br />
| style="width:300px;" |'''[[Manual:Extension/Workflows#Expert document control|Expert document control]]'''<br />
| style="width:100px;" |3 Benutzer<br />
|Nach Bearbeitung einer Seite durch einen bestimmten Benutzer wird die Seite von einem Experten überprüft und über einen Hauptverantwortlichen freigegeben.<br />
|-<br />
| style="width:300px;" |'''[[Manual:Extension/Workflows#Goup Feedback|Group Feedback]]'''<br />
| style="width:100px;" |1 Gruppe<br />
|Eine in der Gruppenverwaltung existierende Gruppe wird aufgefordert, über eine Seite einen Kommentar abzugeben.<br />
|-<br />
| style="width:300px;" |'''[[Manual:Extension/Workflows#Single user feedback|Single user feedback]]'''<br />
| style="width:100px;" |1 Benutzer<br />
|Ein einzelner Benutzer wird aufgefordert, über eine Seite einen Kommentar abzugeben.<br />
|}<br />
<br />
==Benachrichtigungen und Reports==<br />
<br />
*'''Bei der Zuweisung einer Aufgabe:''' Wenn ein Benutzer eine Workflow-Aufgabe durchführen soll, wird sowohl eine Benachrichtigung als auch eine Aufgabe erstellt. Wird die Seite zur Bearbeitung gesperrt,<br />
*'''Nach Abschluss der Begutachtung:''' Nach Abschluss einer Begutachtung wird der Initiator benachrichtigt und eine Email an einen Reportempfänger verschickt.<br />
<br />
==Workflow-Aktivitäten==<br />
Alle Begutachtungsworkflows beginnen mit der Eingabe der Workflow-Einstellungen durch einen Benutzer (Workflow-Initiator) und resultieren in Worfklow-Aktivitäten. <br />
<br />
===Single user approval===<br />
'''Zweck:''' Freigabe einer Entwurfsseite durch einen Benutzer mit Freigaberechten. Dieser Workflow macht nur Sinn, wenn auf einer Seite die [[Referenz:FlaggedRevs|Freigabe-Funktion]] aktiviert ist.<br />
<br />
'''Workflow-Instanzen:''' Es kann immer nur ein Freigabe-Worfklow pro Seite laufen.<br />
<br />
[[Datei:Handbuch:bpmn-SingleUserApproval.svg|verweis=https://bs4-de.wiki.bluespice.com/wiki/Datei:Handbuch:bpmn-SingleUserApproval.svg|alternativtext=BMMN Diagramm des Freigabe Worfklows.|zentriert|mini|750x750px|BMMN Diagramm des Freigabe Worfklows.]]<br />
{| class="wikitable" style="width:100%;"<br />
!Aktivität<br />
!Beschreibung<br />
|-<br />
|CollectData<br />
|Im ersten Workflow-Schritt werden die Einstellungen des Worfklows vorgenommen:<br />
<br />
* ''Benutzer:'' Benutzer (oder Gruppe, die in der Gruppenverwaltung angelegt ist), die die Begutachtung durchführen soll(en).<br />
* ''Anweisungen:'' Eine Mitteilung an den Benutzer oder die Benutzergruppe zur Durchführung der Begutachtung.<br />
* ''Reportempfänger:'' An diese Email-Adresse wird beim Abschluss der Begutachtung ein Email-Report mit den Resultaten gesendet. Wird hier ein Benutzername angegeben, so muss in der Benutzerverwaltung eine Email-Adresse hinterlegt sein, damit der Report versendet werden kann.<br />
|-<br />
|PageCheckout<br />
|Wenn eine Begutachung läuft, ist die Seite für eine Bearbeitung gesperrt. <br />
|-<br />
|PageCheckout<br />
|Die Seite wird für die anstehende Abstimmung zur Bearbeitung gesperrt.<br />
|-<br />
|UserVote<br />
|Der zugewiesene Benutzer führt eine Abstimmung durch und stimmt entweder zu oder lehnt ab. Alternativ kann die Aufgabe delegiert werden. Bei einer Ablehnung wird die Begutachtung abgebrochen.<br />
|-<br />
|ApprovePage<br />
|Bei einer Zustimmung wird die Seite freigegeben.<br />
|-<br />
|SendMail<br />
|Eine Email-Report wird an die angegebene Email-Adresse versandt.<br />
|-<br />
|PageCheckin<br />
|Die Seite wird abschließend entsperrt.<br />
|}<br />
<br />
===Expert document control===<br />
'''Zweck:''' Freigabe einer Entwurfsseite nach dem "6-Augen-Prinzip".<br />
<br />
'''Workflow-Instanzen:''' Es kann immer nur ein Freigabe-Workflow pro Seite laufen.<br />
<br />
[[Datei:Handbuch:bpmn-ExpertDocControl.svg|verweis=https://bs4-de.wiki.bluespice.com/wiki/Datei:Handbuch:bpmn-ExpertDocControl.svg|alternativtext=BPMN Diagramm des Workflows "Qualitätsgesicherte Bearbeitung"|zentriert|mini|550x550px|BPMN Diagramm des Workflows "Qualitätsgesicherte Bearbeitung"]]<br />
{| class="wikitable" style="width:100%;"<br />
!Aktivität<br />
!Beschreibung<br />
|-<br />
|CollectData<br />
|Im ersten Workflow-Schritt werden die Einstellungen des Worfklows vorgenommen:<br />
<br />
* ''Benutzer:'' Benutzer (oder Gruppe, die in der Gruppenverwaltung angelegt ist), die die Begutachtung durchführen soll(en).<br />
* ''Anweisungen:'' Eine Mitteilung an den Benutzer oder die Benutzergruppe zur Durchführung der Begutachtung.<br />
* ''Reportempfänger:'' An diese Email-Adresse wird beim Abschluss der Begutachtung ein Email-Report mit den Resultaten gesendet. Wird hier ein Benutzername angegeben, so muss in der Benutzerverwaltung eine Email-Adresse hinterlegt sein, damit der Report versendet werden kann.<br />
|-<br />
|PageCheckout<br />
|Die Seite wird für die anstehende Abstimmung zur Bearbeitung gesperrt.<br />
|-<br />
|EditPage<br />
|Begutachter 1 kann die Seite bearbeiten und schließt die Aufgabe kommentarlos ab.<br />
|-<br />
|UserVote<br />
|Begutachter 2 und 3 stimmen ab. Sobald ein Begutachter ablehnt, started die Begutachtung erneut mit Begutachter 1.<br />
|-<br />
|ApprovePage<br />
|Nach Zustimmung von Begutachter 2 und 3 wird die Seite freigegeben.<br />
|-<br />
|SendMail<br />
|Eine Email-Report wird an die angegebene Email-Adresse versandt.<br />
|-<br />
|PageCheckin<br />
|Die Seite wird abschließend entsperrt.<br />
|}<br />
<br />
===Group feedback===<br />
'''Zweck:''' Einholen von Feedback von einer Benutzergruppe. Die Gruppe muss in der Gruppenverwaltung angelegt sein.<br />
<br />
'''Workflow-Instanzen:''' Es können unabhängig voneinander mehrere Feedback-Worfklows gleichzeitig auf einer Seite laufen.<br />
<br />
[[Datei:Handbuch:bpmn-GroupFeedback..svg|verweis=https://bs4-de.wiki.bluespice.com/wiki/Datei:Handbuch:bpmn-GroupFeedback..svg|alternativtext=BPMN Diagramm des Workflows "Gruppen-Feedback"|zentriert|mini|450x450px|BPMN Diagramm des Workflows "Gruppen-Feedback"]]<br />
{| class="wikitable" style="width:100%;"<br />
!Aktivität<br />
!Beschreibung<br />
|-<br />
|CollectData<br />
|Im ersten Workflow-Schritt werden die Einstellungen des Worfklows vorgenommen:<br />
<br />
* ''Benutzer:'' Benutzer (oder Gruppe, die in der Gruppenverwaltung angelegt ist), die die Begutachtung durchführen soll(en).<br />
* ''Anweisungen:'' Eine Mitteilung an den Benutzer oder die Benutzergruppe zur Durchführung der Begutachtung.<br />
* ''Reportempfänger:'' An diese Email-Adresse wird beim Abschluss der Begutachtung ein Email-Report mit den Resultaten gesendet. Wird hier ein Benutzername angegeben, so muss in der Benutzerverwaltung eine Email-Adresse hinterlegt sein, damit der Report versendet werden kann.<br />
|-<br />
|GroupFeedback<br />
|Alle Benutzer in der zugewiesenen Gruppe geben über ein Kommentarfeld ein Feedback ab. Hierbei handelt es sich um einen parallelen Workflow, das heißt, die Reihenfolge der Rückmeldungen ist egal.<br />
|-<br />
|SendMail<br />
|Eine Email-Report wird an die angegebene Email-Adresse versandt.<br />
|}<br />
<br />
=== Feedback ===<br />
'''Zweck:''' Einholen von Feedback eines einzelnen Benutzers zu einer Seite. <br />
<br />
'''Workflow-Instanzen:''' Es können unabhängig voneinander mehrere Feedback-Worfklows gleichzeitig auf einer Seite laufen.<br />
<br />
[[Datei:Handbuch:bpmn-UserFeedback.svg|verweis=https://bs4-de.wiki.bluespice.com/wiki/Datei:Handbuch:bpmn-UserFeedback.svg|alternativtext=BPMN Diagramm des Feedback Worfklows|zentriert|mini|500x500px|BPMN Diagramm des Feedback-Worfklows]]<br />
{| class="wikitable" style="width:100%;"<br />
!Aktivität<br />
!Beschreibung<br />
|-<br />
|CollectData<br />
|Im ersten Workflow-Schritt werden die Einstellungen des Worfklows vorgenommen:<br />
<br />
* ''Benutzer:'' Benutzer (oder Gruppe, die in der Gruppenverwaltung angelegt ist), die die Begutachtung durchführen soll(en).<br />
* ''Anweisungen:'' Eine Mitteilung an den Benutzer oder die Benutzergruppe zur Durchführung der Begutachtung.<br />
* ''Reportempfänger:'' An diese Email-Adresse wird beim Abschluss der Begutachtung ein Email-Report mit den Resultaten gesendet. Wird hier ein Benutzername angegeben, so muss in der Benutzerverwaltung eine Email-Adresse hinterlegt sein, damit der Report versendet werden kann.<br />
|-<br />
|PageCheckout<br />
|Wenn eine Begutachung läuft, ist die Seite für eine Bearbeitung gesperrt. (Hinweis: In der ''Qualitätsgesicherten Bearbeitung'' wird erst nach dem ersten Begutachter gesperrt)´).<br />
|-<br />
|UserFeedback<br />
|Der zugewiesene Benutzer gibt über ein Kommentarfeld ein Feedback ab.<br />
|-<br />
|SendMail<br />
|Eine Email-Report wird an die angegebene Email-Adresse versandt.<br />
|}<br />
<br />
== Overview page==<br />
Alle Workflows sind auf der Seite ''Spezial:Workflows overview'' aufgeführt. Es gibt eine Ansicht der aktuellen Workflows und eine Ansicht aller Workflows:<br />
[[Datei:Handbuch:wf-übersicht.png|alternativtext=Workflows Übersicht|zentriert|mini|750x750px|Workflows Übersicht]]<br />
<br />
=== Tasks ===<br />
Benutzer werden über ihre Workflows auf ihrer Benachrichtungsseite sowie auf der Seite [[Manual:Extension/UnifiedTaskOverview|Meine Aufgaben]] über zugewiesene Workflow-Aufgaben informiert.<br />
<br />
==How to add a workflow==<br />
Die xml-Datei eines BPMN-Diagramms kann durch das Einfügen sogenannter Aktivitäten angepasst werden. Derzeit gibt es folgende definierte Aktivitäten: <br />
<br />
'''Extension: Workflows''' <br />
<br />
* [[Manual:Extension/Workflows/Activity/CustomForm|CustomForm]]<br />
* [[Manual:Extension/Workflows/Activity/UserVote|UserVote]]<br />
* [[Manual:Extension/Workflows/Activity/GroupVote|GroupVote]]<br />
* [[Manual:Extension/Workflows/Activity/UserFeedback|UserFeedback]]<br />
* [[Manual:Extension/Workflows/Activity/GrouppFeedback|GroupFeedback]]<br />
* [[Manual:Extension/Workflows/Activity/SendMail|SendMail]]<br />
* [[Manual:Extension/Workflows/Activity/EditRequest|EditRequest]]<br />
<br />
<br />
'''Extension: PageCheckout'''<br />
<br />
* [[Manual:Extension/Workflows/Activity/PageCheckOut|PageCheckOut]]<br />
* [[Manual:Extension/Workflows/Activity/PageCheckIn|PageCheckIn]]<br />
<br />
<br />
'''Extension: BlueSpiceFlaggedRevsConnector'''<br />
<br />
* [[Manual:Extension/Workflows/Activity/ApprovePage|ApprovePage]]<br />
<br />
<br />
Beispiel zum erstellen eines neuen Workflows</div>WikiSysophttps://en.wiki.bluespice.com/w/index.php?title=Reference:CognitiveProcessDesigner&diff=1549Reference:CognitiveProcessDesigner2021-12-20T16:10:28Z<p>WikiSysop: </p>
<hr />
<div>{{BSExtensionInfobox<br />
|desc=Draw BPMN processes with a graphical user interface in Semantic MediaWiki<br />
|status=stable<br />
|developer=Tobias Weller, Maria Maleshkova, Alexander Pinchuk<br />
|type=MediaWiki<br />
|edition=BlueSpice pro, BlueSpice Farm, BlueSpice Cloud<br />
|compatible=MediaWiki<br />
|category=Rich Articles<br />
|license=Apache license 2.0<br />
|docu=https://www.mediawiki.org/wiki/Extension:Cognitive_Process_Designer<br />
}}<br />
<span style="color: rgb(32, 33, 34)">The</span> '''Cognitive Process Designer''' <span style="color: rgb(32, 33, 34)">extension supports the creation, importing, exporting and annotating of BPMN (Business Process Model and Notation) processes by using an intuitive GUI (graphical user interface). Each element (node and edge) is represented by its own wiki page, which publishes the information according to the</span> [https://www.w3.org/DesignIssues/LinkedData.html Linked Data Principles]<span style="color: rgb(32, 33, 34)">. Cognitive Process is based on</span> [https://bpmn.io/ bpmn.io]<span style="color: rgb(32, 33, 34)">, an open source project by</span> [https://camunda.com/ Camunda]<span style="color: rgb(32, 33, 34)">. Bpmn.io is an JavaScript renderer that allows to model BPMN processes and checks the syntax.</span> [[mediawikiwiki:Semantic_Forms|Semantic Forms]] <span style="color: rgb(32, 33, 34)">is used to facilitate the input of information for each element.</span><br />
<br />
<br />
<br />
[[Category:Extension]]<br />
{{translation}}</div>WikiSysophttps://en.wiki.bluespice.com/w/index.php?title=SocialEntity:88&diff=1548SocialEntity:882021-12-20T16:08:58Z<p>WikiSysop: </p>
<hr />
<div>{<br />
"wikipageid": 888,<br />
"namespace": 0,<br />
"titletext": "Apache license 2.0",<br />
"description": "",<br />
"parentid": 0,<br />
"id": 88,<br />
"ownerid": 1,<br />
"type": "wikipage",<br />
"archived": false,<br />
"tags": [<br />
"Apache license 2.0"<br />
],<br />
"resolved": false<br />
}</div>WikiSysophttps://en.wiki.bluespice.com/w/index.php?title=Apache_license_2.0&diff=1547Apache license 2.02021-12-20T16:08:58Z<p>WikiSysop: Created page with "<span style="color: rgb(51, 51, 51)">The 2.0 version of the Apache License, approved by the ASF in 2004, aims to provide reliable and long-lived software products through coll..."</p>
<hr />
<div><span style="color: rgb(51, 51, 51)">The 2.0 version of the Apache License, approved by the ASF in 2004, aims to provide reliable and long-lived software products through collaborative, open-source software development.</span><br />
<br />
<br />
For more license info, visit:<br />
<br />
https://www.apache.org/licenses/LICENSE-2.0</div>WikiSysophttps://en.wiki.bluespice.com/w/index.php?title=SocialEntity:87&diff=1546SocialEntity:872021-12-20T16:07:28Z<p>WikiSysop: </p>
<hr />
<div>{<br />
"wikipageid": 886,<br />
"namespace": 0,<br />
"titletext": "Reference:CognitiveProcessDesigner",<br />
"description": "",<br />
"parentid": 0,<br />
"id": 87,<br />
"ownerid": 1,<br />
"type": "wikipage",<br />
"archived": false,<br />
"tags": [<br />
"Reference:CognitiveProcessDesigner"<br />
],<br />
"resolved": false<br />
}</div>WikiSysophttps://en.wiki.bluespice.com/w/index.php?title=Reference:CognitiveProcessDesigner&diff=1545Reference:CognitiveProcessDesigner2021-12-20T16:07:27Z<p>WikiSysop: Created page with "{{BSExtensionInfobox |desc=Draw BPMN processes with a graphical user interface in Semantic MediaWiki |status=stable |developer=Tobias Weller, Maria Maleshkova, Alexander Pinch..."</p>
<hr />
<div>{{BSExtensionInfobox<br />
|desc=Draw BPMN processes with a graphical user interface in Semantic MediaWiki<br />
|status=stable<br />
|developer=Tobias Weller, Maria Maleshkova, Alexander Pinchuk<br />
|type=MediaWiki<br />
|edition=BlueSpice pro, BlueSpice Farm, BlueSpice Cloud<br />
|compatible=MediaWiki<br />
|category=Quality assurance<br />
|license=Apache license 2.0<br />
|docu=https://www.mediawiki.org/wiki/Extension:Cognitive_Process_Designer<br />
}}<br />
<span style="color: rgb(32, 33, 34)">The</span> '''Cognitive Process Designer''' <span style="color: rgb(32, 33, 34)">extension supports the creation, importing, exporting and annotating of BPMN (Business Process Model and Notation) processes by using an intuitive GUI (graphical user interface). Each element (node and edge) is represented by its own wiki page, which publishes the information according to the</span> [https://www.w3.org/DesignIssues/LinkedData.html Linked Data Principles]<span style="color: rgb(32, 33, 34)">. Cognitive Process is based on</span> [https://bpmn.io/ bpmn.io]<span style="color: rgb(32, 33, 34)">, an open source project by</span> [https://camunda.com/ Camunda]<span style="color: rgb(32, 33, 34)">. Bpmn.io is an JavaScript renderer that allows to model BPMN processes and checks the syntax.</span> [[mediawikiwiki:Semantic_Forms|Semantic Forms]] <span style="color: rgb(32, 33, 34)">is used to facilitate the input of information for each element.</span><br />
<br />
<br />
<br />
[[Category:Extension]]<br />
{{translation}}</div>WikiSysophttps://en.wiki.bluespice.com/w/index.php?title=Reference:UnifiedTaskOverview&diff=1544Reference:UnifiedTaskOverview2021-12-20T16:00:57Z<p>WikiSysop: </p>
<hr />
<div>{{BSExtensionInfobox<br />
|desc=Provides the special page "My tasks"<br />
|status=stable<br />
|developer=Hallo Welt!<br />
|type=MediaWiki<br />
|edition=BlueSpice pro, BlueSpice Farm, BlueSpice Cloud<br />
|compatible=MediaWiki<br />
|category=Personalization<br />
}}<br />
The new overview page “My Tasks” (Special:My_tasks) allows users to view their upcoming tasks in the wiki. The special page can be reached via the [[Manual:Extension/BlueSpiceDiscovery#Header bar|user menu]] under ''Personal Tools> Tasks''.<br />
<br />
*Currently, workflow tasks and pending read confirmations are displayed.<br />
*When there are tasks, this is announced via a red notification icon in the user menu.<br />
*Each task card leads to the wiki page that is linked to the task.<br />
[[File:my tasks.png|alt=Special page "My tasks"|center|thumb|650x650px|Special page "My tasks"]]</div>WikiSysophttps://en.wiki.bluespice.com/w/index.php?title=Reference:UnifiedTaskOverview&diff=1543Reference:UnifiedTaskOverview2021-12-20T16:00:37Z<p>WikiSysop: </p>
<hr />
<div>{{BSExtensionInfobox<br />
|desc=Provides the special page "My tasks"<br />
|status=stable<br />
|developer=Hallo Welt!<br />
|type=MediaWiki<br />
|edition=BlueSpice pro, BlueSpice Farm, BlueSpice Cloud<br />
|compatible=MediaWiki<br />
|category=Personalization<br />
|docu=dfdfdf<br />
}}<br />
The new overview page “My Tasks” (Special:My_tasks) allows users to view their upcoming tasks in the wiki. The special page can be reached via the [[Manual:Extension/BlueSpiceDiscovery#Header bar|user menu]] under ''Personal Tools> Tasks''.<br />
<br />
*Currently, workflow tasks and pending read confirmations are displayed.<br />
*When there are tasks, this is announced via a red notification icon in the user menu.<br />
*Each task card leads to the wiki page that is linked to the task.<br />
[[File:my tasks.png|alt=Special page "My tasks"|center|thumb|650x650px|Special page "My tasks"]]</div>WikiSysop