BlueSpice Wiki - User contributions [en]

Setup:BlueSpice Operating Manual

2022-01-10T09:48:23Z

Mglaser: adding external call to chemical formulas

{{DISPLAYTITLE:BlueSpice Operating Manual}}
<bs:ueparams template="BlueSpice Book" />
==Objective==
The objective of this operating manual is to enable you to run BlueSpice smoothly and successfully in your IT environment. It aims to answer your questions as deciders, IT auditors and server administrators, such as:

*Where do I get information about BlueSpice and its development?
*What do I have to consider when operating BlueSpice?
*How do I backup and monitor BlueSpice?

The most current version can be found at https://wiki.bluespice.com . This manual is designed to provide general information. Feel free to copy it over to your local BlueSpice and amend it according to your process and documentation requirements. Since the IT environment can change over time through updates and restructuring, it is advisable to check the information in the operating manual for being up-to-date.

The structure of this manual is based on the recommendations of the German [https://www.bsi.bund.de/EN/TheBSI/thebsi_node.html Federal Office for Information Security], which [https://www.bsi.bund.de/SharedDocs/Downloads/DE/BSI/Grundschutz/Download/IT-GS-Bausteine/Cloud_Speicher/Betriebshandbuch.html can be found here].

==Overview==

===System overview===
BlueSpice is a webbased client-server application. On the server side, it uses a web server (Apache, IIS, Nginx), the script language PHP, a database (MySQL or MariaDB), a JAVA application server (Tomcat or Jetty), Elasticsearch, and a NodeJS service (Parsoid). There are several binaries required on the server, such as phantomJS and Imagemagick.

BlueSpice can be run in a distributed environment. All services can be put on individual servers (web server + PHP, database, application server, Elasticsearch). A common scenario is to scale the web server and PHP horizontally.

Typically, inhouse deployments of BlueSpice consist of a production environment and a corresponding test environment. In scenarios with elevated SLAs, an additional QA environment is used as an intermediary before production.

===Owners, responsible persons and contacts===
BlueSpice is developed and maintained by

:Hallo Welt! GmbH 
:Maximilianstraße 9 
:93047 Regensburg 
:https://www.hallowelt.com

For technical questions, please contact Hallo Welt! GmbH support at [mailto:support@hallowelt.com support@hallowelt.com].

For questions about your contract, please contact the Hallo Welt! GmbH sales team at [mailto:sales@hallowelt.com sales@hallowelt.com] .

===Operating times===
Typically, BlueSpice instances run 24/7. Operations are managed by the organization's IT department or their service providers. Hallo Welt! provides support and guidance during their office hours (8am - 6pm CET/CEST).

===System and version history===
All BlueSpice versions are documented in the BlueSpice helpdesk: https://en.wiki.bluespice.com/wiki/Setup:Release_History

All changes can be retraced in our current and archived release notes: https://en.wiki.bluespice.com/wiki/Setup:Release_Notes

===Documentation===
BlueSpice maintains an online documentation which is continuously kept up to date: [https://en.wiki.bluespice.com/wiki/Setup:System_requirements https://en.wiki.bluespice.com]

There is also a user manual: https://en.wiki.bluespice.com/wiki/UserManual:User_Manual_Introduction

Administration is documented here: https://en.wiki.bluespice.com/wiki/UserManual:Admin_Manual_Introduction

In addition, there is a community forum: https://sourceforge.net/p/bluespice/_list/tickets

News about the product can be found in our blog: https://bluespice.com/category/news-know-how/

Also, BlueSpice maintains a newsletter. Sign up here: https://bluespice.com/

For more information, follow us on Twitter: https://twitter.com/BlueSpiceTweets

===Installation manual Windows/Linux (including upgrade instructions)===
BlueSpice maintains an online installation manual: https://en.wiki.bluespice.com/wiki/Setup:Installation_Guide

==System architecture and interfaces==
The following section gives an overview of the components of BlueSpice and how they interact with each other and the environment.

===System integration===
BlueSpice is a web application which can be integrated with your IT environment, most notably LDAP and email.

<bs:drawio filename="BlueSpice system architecture high level" />

===Server architecture===
Internally, BlueSpice has several components which are responsible for parts of the functionality.

<bs:drawio filename="BlueSpice system architecture server" />

===Vertically distributed architecture===
For simple scaling, some services can be externalized to other physical or virtual servers.

<bs:drawio filename="BlueSpice system architecture server distributed simple" />

===Horizontally distributed architecture===
For high traffic or high availability demands, BlueSpice can be set up to scale horizontally.

<bs:drawio filename="BlueSpice system architecture server distributed horizontally" />

===Components and responsibilities===
Servers, operating system, licenses and software infrastructure are typically managed by your organization's IT.

Hallo Welt! typically manages the application and required components.

There may be special contractual agreements.

===External interfaces (to other organizations)===
'''Technically''', BlueSpice can be set up to operate completely self-contained (contact our support if you have questions about your instance). On the server, no external sources are queried. In the standard installation, there are content modules which draw data from external sources on the client side (browser):

*'''draw.io''': The diagram tool is loaded directly from draw.io. All content remains on the BlueSpice wiki.
*'''maps''': Embedded maps are collected from Google or OpenStreetMap.
*'''widgets''': The purpose of widgets is to display content from public sources like YouTube.
*'''chemical formulas''': The formula rendering uses an external service via Wikimedia's REST API.

On the '''organizational''' side, the team of Hallo Welt! GmbH typically provides 3rd level support for subscribed BlueSpice instances. Hallo Welt! GmbH teams up with the internal IT of the organization as well as with IT infrastructure providers of our customers.

===IT internal interfaces===
A standard BlueSpice installation connects to the following services in order to be fully functional:

*'''User directory''': BlueSpice can be configured to authenticate against a company user directory (typically Active Directory). The protocols used are LDAP and SAML.
*'''Email''': BlueSpice needs to be connected to an email server in order to send notifications.

===API===
BlueSpice comes with an API interface.

*For instructions on how to handle the API, see here: https://www.mediawiki.org/wiki/API:Main_page
*For a comprehensive list of API modules, see here: https://en.wiki.bluespice.com/w/api.php

==Installation and system requirements==

===System requirements===
The current system requirements are documented here: https://en.wiki.bluespice.com/wiki/Setup:System_requirements

===Software catalogue===
All BlueSpice components are listed in the software catalogue: https://en.wiki.bluespice.com/wiki/Setup:Software_Catalogue

===Changes in configuration===
Changes in configuration can occur in minor and major releases. Please consider the upgrade information provided here: https://en.wiki.bluespice.com/wiki/Setup:Installation_Guide/Upgrade

==Start and interrupt the service==

===Startup===
In order to start up BlueSpice, all the required services need to be running. Please make sure you start the services in the order given here:

'''Database'''

*Linux: <code>service mysql start</code> OR <code>systemctl start mysql</code>
*Windows: <code>services.msc</code>

'''Application server''' (Tomcat or Jetty)

*Linux: <code>service jetty9 start</code> OR <code>systemctl start jetty9</code>
*Windows: <code>services.msc</code>

'''Elasticsearch'''

*Linux: <code>service elasticsearch start</code> OR <code>systemctl start elasticsearch</code>
*Windows: <code>services.msc</code>

'''Parsoid'''

*Linux: <code>pm2 start /opt/parsoid/bin/server.js</code> OR <code>systemctl start parsoid</code>
*Windows: <code>services.msc</code>

'''Web server'''

*Linux: <code>service apache2 start</code> OR <code>systemctl start apache2</code>
*Windows: <code>services.msc</code>

===Shutdown===
In order to shut down BlueSpice, all the required services need to be stopped. Please make sure you stop the services in the order given here:

'''Web server'''

*Linux: <code>service apache2 stop</code> OR <code>systemctl stop apache2</code>
*Windows: <code>services.msc</code>

'''Parsoid'''

*Linux: <code>pm2 stop /opt/parsoid/bin/server.js</code> OR <code>systemctl stop parsoid</code>
*Windows: <code>services.msc</code>

'''Application server''' (Tomcat or Jetty)

*Linux: <code>service jetty9 stop</code> OR <code>systemctl stop jetty9</code>
*Windows: <code>services.msc</code>

'''Elasticsearch'''

*Linux: <code>service elasticsearch stop</code> OR <code>systemctl stop elasticsearch</code>
*Windows: <code>services.msc</code>

'''Database'''

*Linux: <code>service mysql stop</code> OR <code>systemctl stop mysql</code>
*Windows: <code>services.msc</code>

===Configuration changes===
After changes to the configuration, the service with the changed configuration needs to be restarted.

'''Webserver'''

*Linux: <code>service apache2 restart</code>
*Windows: <code>[https://en.wikipedia.org/wiki/Service_Control_Manager services.mmc]</code>

'''Parsoid'''

*Linux: <code>pm2 restart /opt/parsoid/bin/server.js</code>
*Windows: <code>[https://en.wikipedia.org/wiki/Service_Control_Manager services.mmc]</code>

'''Application server''' (Tomcat or Jetty)

*Linux: <code>service jetty9 restart</code>
*Windows: <code>[https://en.wikipedia.org/wiki/Service_Control_Manager services.mmc]</code>

'''Elasticsearch'''

*Linux: <code>service elasticsearch restart</code>
*Windows: <code>[https://en.wikipedia.org/wiki/Service_Control_Manager services.mmc]</code>

'''Database'''

*Linux: <code>service mysql restart</code> OR <code>systemctl restart mysql</code>
*Windows: <code>[https://en.wikipedia.org/wiki/Service_Control_Manager services.mmc]</code>

===Unplanned server outage===
Identify which service is not running and restart this service.

==Standard operations==

===User management===

*All users are managed in the application. For details, see https://en.wiki.bluespice.com/wiki/Manual:Extension/BlueSpiceUserManager

===Recurring background tasks===
BlueSpice is set up to conduct some tasks in the background. These are

*<code>maintenance/runJobs.php</code>

For details see: https://en.wiki.bluespice.com/wiki/Setup:Installation_Manual/Optimization/Cronjobs

===Backup===
Detailed backup instructions can be found here: https://en.wiki.bluespice.com/wiki/Setup:Installation_Guide/Advanced/Backup

===Monitoring===
Apart from the common parameters to monitor (disk space, CPU load, memory usage), the following services can be monitored for availability:

*Web server: ping the login page of the wiki: <wiki_url>/Special:Login
*Database: check database connectivity with username and password authentication.
*Parsoid: check port 8000 connectivity via 127.0.0.1
*Elasticsearch: check port 9200 connectivity via 127.0.0.1

If any of those services is not available, BlueSpice is either not operational or experiencing functional restrictions.

===Diagnostics===
In case of errors, please consider the error logs. These are:

*In the web browser, open the console and check for JavaScript errors
*For the web server, check the web server's error log and php error log.

===Troubleshooting===
If one or more services are not working:

*Check the available system resources, in particular the free disk space
*Restart all services

If the problem persists, contact BlueSpice support.

==Key performance indicators==

===Server===
Standard parameters for servers apply:

*Disk space < 80% usage
*CPU load should not peak to 100% for more than 1s
*Load average should not be more than CPU core count
*Average memory usage should not exceed 90%
*For GNU/Linux systems, try to avoid high swap space usage.

For a standard server sizing (4 cores, 8 GB ram), the number of average simultaneous users is optimized for 25 per server. This means, one server can handle about 125 concurrent users.

The php error log should not report any FATAL or WARNING messages

===Client===
The reference page ''Special:Version'' should load under 4s without browser cache and under 2.5s with browser cache enabled.

==Known restrictions==

===Functional restrictions===
This is now services map onto BlueSpice functionality:

*Web server: required for BlueSpice basic operations
*Database: required for BlueSpice basic operations
*Tomcat: required for PDF and VisualDiff
*Elasticsearch: required for ExtendedSearch and various title select boxes. Will fallback to standard MediaWiki search if not available.
*PhantomJS: required for rendering article preview images.
*Parsoid: required for VisualEditor. Note: in BlueSpice 4.0 this is no longer required.

All services other than web server and database are optional. If not present, the named functionality will not be available.

===Technical restrictions===
Updates of major and minor level might require a system downtime due to database migration operations.

===Resource related restrictions===
Response times are dependent on the server resources, foremost CPU power.

The number of concurrent users a server can handle is directly related to server memory size and CPU power.

Please note: we strongly recommend having a separate testing system. This can be used for update/upgrade preparation, debugging and collecting sizing information. If no testing system is present, occasional downtimes may occur when debugging and maintenance operations are conducted.

==Archiving and deletion of data==

===Variable data (Strongly growing data)===
The following locations store variable data, which is not recoverable in case of data loss, and must be backed up regularly:

*The database stores most data of BlueSpice, including articles, users and action logs.
*The images folder stores all uploaded files.

There is some secondary data stored in Elasticsearch (for BlueSpice Social and Statistics). This data can be fully recovered from the primary data stored in the database.

===Master data (Slowly growing data)===
The following locations store master data, which requires considerable effort to recover in case of data loss and should be backed up regularly:

*Configuration:
**LocalSettings.php and LocalSettings.BlueSpice.local.php contain the basic configuration including sitename, security keys and database access.
**settings.d folder contains information about activated extensions.
**extensions/BlueSpiceFoundation/config folder holds information about namespace setup and permission configuration.
*Templates and skins
**extensions/BlueSpiceFoundation/data folder holds PDF templates.

===Log files and error files===

*Php error log: <code>/var/log/php-fpm.log</code> (Only for php-fpm service)
*Apache access log: <code>/var/log/apache2/*access.log</code>
*Apache error logs: <code>/var/log/apache2/*error.log</code> (Also includes PHP errors)
*Browser console
*Parsoid log: <code>pm2 logs</code> OR <code>/var/log/parsoid.log</code>(systemd and init.d)
*Elasticsearch: <code>/var/log/elasticsearch/</code>
*Tomcat: By default logging is turned of. Depending on system, logging can be enabled via configuration XML files.
*Windows event log: MS Windows logs are not txt format. Access is possible via [https://en.wikipedia.org/wiki/Event_Viewer Event Viewer]

==Security and compliance==

===Internet access===
For standard operations, BlueSpice does not require Internet access. BlueSpice does not make any outgoing calls. See section External interfaces for details.

In our default setup, the client will access draw.io for editing diagrams. Here, only application data is loaded from the site. No content data will be passed on to draw.io. On request, Hallo Welt! can install an on-premise version of draw.io (additional charges apply).

===Auxiliary service data access===
Tomcat, Elasticsearch and PhantomJS will receive data from BlueSpice core components. They are agnostic to access rights and do have full access to all data stored on BlueSpice. It is therefore recommended to restrict access to these services to localhost or the web server's IP address. In case Hallo Welt! performs the installation, this is the default setup. No external access to these services shall be permitted.

===Privacy===
GDPR compliancy is handled by BlueSpice Privacy Center. More information can be found here: https://en.wiki.bluespice.com/wiki/Manual:Extension/BlueSpicePrivacy

===Legal information===
For all legal information, including the Subscription contract, GDPR information and DPA, Anti Bribery Policy and Software catalogue, please refer to the BlueSpice homepage: https://bluespice.com/legal-documents-and-guidelines/

[[en:{{FULLPAGENAME}}]]
[[de:Setup:BlueSpice Betriebshandbuch]]

SocialEntity:6954

2022-01-10T09:48:23Z

Mglaser:

{
"wikipageid": 9532,
"revisionid": 28307,
"namespace": 3008,
"titletext": "BlueSpice Operating Manual",
"action": "edit",
"summary": "adding external call to chemical formulas",
"parentid": 0,
"id": 6954,
"ownerid": 10,
"type": "articlesave",
"archived": false,
"tags": [],
"resolved": false
}

How to become a BlueSpice hacker

2021-11-05T13:39:20Z

Mglaser: typo again

This article is written to help novice developers learn the skills needed to contribute to BlueSpice development.

'''Why should you contribute?''' 
When you are actively involved in a project you get the opportunity to shape its future. Changes are caused by actions. You will certainly receive a big "thank you" and you will be publicly credited related to your work. Even more, you are helping a lot of users who will thank you quietly or loudly.

==Join in==
Like in every other project there are lots of possibilities to participate. Here a few examples of what you could do in the BlueSpice project.

===Improving the code quality===

*Doc blocs: Write with us documenting blocs in the source code. This helps us to complete the code and check for discrepancies. More about the [http://meta.wikimedia.org/wiki/PhpDoc MediaWiki DocBlocks] at wikimedia.
*Coding conventions: Help to enforce coding conventions. We use the [http://www.mediawiki.org/wiki/Manual:Coding_conventions Coding Conventions of MediaWiki].
*Security: has high priority. Please help to improve it. Therefore you should have a look at [http://www.mediawiki.org/wiki/Security_for_developers Security for developers].

===Bugfixes===
Look for minor and major bugs. And if you already programmed the solution, well, all the better! 
Here you can find some help on [http://www.mediawiki.org/wiki/Manual:How_to_debug debugging in MediaWiki]

===Code Review===
Help us to review code contributions. Therefore you have to be familiar with gerrit. Find more information at "setting up a development environment" und "committing changes".

*[http://gerrit.wikimedia.org/r/#/q/status:open+project:mediawiki/extensions/BlueSpiceExtensions,n,z BlueSpice Extensions]
*[http://gerrit.wikimedia.org/r/#/q/status:open+project:mediawiki/extensions/BlueSpiceFoundation,n,z BlueSpice Fundation]
*[http://gerrit.wikimedia.org/r/#/q/status:open+project:mediawiki/skins/BlueSpiceSkins,n,z BlueSpice Skin]

===Small addition===
A lot of the existing extensions want to be developed and provide opportunities to extend the functionality. What we have in mind: 
Dashboard Widgets, Statics, Sidebar, Widgets, etc.

===Own extensions===
Of course you can develop your own BlueSpice extensions. Please follow the MediaWiki workflow. You will find a good tutorial on MediaWiki pages like this one [http://www.mediawiki.org/wiki/Manual:Developing_extensions MediaWiki developing extensions MediaWiki]. These notes should also be consulted for developing BlueSpice.
Please create a separate repository in gerrit that is named like this:

<pre>mediawiki/skins/BlueSpiceYourExtension</pre>

===Translations===
Translations are needed all the time. Please contact the community of [https://translatewiki.net translatewiki.net].

==This is how it works==
===Commit changes===
There are two possibilities to supply patches.

'''1. Mail to Hallo Welt'''!

Send an e-mail with your patch in ([https://www.kernel.org/pub/software/scm/git/docs/git-format-patch.html git format-patch]) to support@hallowelt.com. We will commit the change for you in git where it has to go through a standardized process.

'''2. Actively participating via Git'''

We follow the procedure that is also common in the MediaWiki developer community:

*Get a developer account for MediaWiki
*Install git-review
*check out the BlueSpice code
*Commit your changes
*Changes are verified in gerrit
*When everything is ok, your changes will be accepted

On MediaWiki.org you will find a [http://www.mediawiki.org/wiki/Gerrit/Getting_started short] and a [http://www.mediawiki.org/wiki/Gerrit/Tutorial extended] tutorial.

The BlueSpice code can be found in these repositories:

mediawiki/extensions/BlueSpiceFoundation.git
mediawiki/extensions/BlueSpiceExtensions.git
mediawiki/skins/BlueSpiceSkin.git

and this is how you check out:

git clone ssh://USERNAME@gerrit.wikimedia.org:29418/mediawiki/extensions/BlueSpiceFoundation.git

In the repositories of BlueSpice it is necessary to have the "+2" or "Merge" permission before you can commit code to the product by yourself. Please ask Markus Glaser if you feel you need this kind of access (glaser@hallowelt.biz).

If you want to write own extensions for BlueSpice please ask for an own repository [https://www.mediawiki.org/wiki/Gerrit/New_repositories#Step_3:_Request_space_for_your_extension here]. Please follow the naming convention.

mediawiki/extensions/BlueSpiceMyWidget.git

==See also==

*https://www.mediawiki.org/wiki/How_to_become_a_MediaWiki_hacker

[[en:{{FULLPAGENAME}}]]
[[de:Wie Werde Ich ein BlueSpice Hacker]]

How to become a BlueSpice hacker

2021-11-05T13:36:38Z

Mglaser: typo

This article is written to help novice developers learn the skills needed to contribute to BlueSpice development.

'''Why should you contribute?''' 
When you are actively involved in a project you get the opportunity to shape its future. Changes are caused by actions. You will certainly receive a big "thank you" and you will be publicly credited related to your work. Even more, you are helping a lot of users who will thank you quietly or loudly.

==Join in==
Like in every other project there are lots of possibilities to participate. Here a few examples of what you could do in the BlueSpice project.

===Improving the code quality===

*Doc blocs: Write with us documenting blocs in the source code. This helps us to complete the code and check for discrepancies. More about the [http://meta.wikimedia.org/wiki/PhpDoc MediaWiki DocBlocks] at wikimedia.
*Coding conventions: Help to enforce coding conventions. We use the [http://www.mediawiki.org/wiki/Manual:Coding_conventions Coding Conventions of MediaWiki].
*Security: has high priority. Please help to improve it. Therefore you should have a look at [http://www.mediawiki.org/wiki/Security_for_developers Security for developers].

===Bugfixes===
Look for minor and major bugs. And if you already programmed the solution, well, all the better! 
Here you can find some help on [http://www.mediawiki.org/wiki/Manual:How_to_debug debugging in MediaWiki]

===Code Review===
Help us to review code contributions. Therefore you have to be familiar with gerrit. Find more information at "setting up a development environment" und "committing changes".

*[http://gerrit.wikimedia.org/r/#/q/status:open+project:mediawiki/extensions/BlueSpiceExtensions,n,z BlueSpice Extensions]
*[http://gerrit.wikimedia.org/r/#/q/status:open+project:mediawiki/extensions/BlueSpiceFoundation,n,z BlueSpice Fundation]
*[http://gerrit.wikimedia.org/r/#/q/status:open+project:mediawiki/skins/BlueSpiceSkins,n,z BlueSpice Skin]

===Small addition===
A lot of the existing extensions want to be developed and provide opportunities to extend the functionality. What we have in mind: 
Dashboard Widgets, Statics, Sidebar, Widgets, etc.

===Own extensions===
Of course you can develop your own BlueSpice extensions. Please follow the MediaWiki workflow. You will find a good tutorial on MediaWiki pages like this one [http://www.mediawiki.org/wiki/Manual:Developing_extensions MediaWiki developing extensions MediaWiki]. These notes should also be consulted for developing BlueSpice.
Please create a separate repository in gerrit that is named like this:

<pre>mediawiki/skins/BlueSpiceYourExtension</pre>

===Translations===
Translations are needed all the time. Please contact the community of [https://translatewiki.net translatewiki.net].

==This is how it works==
===Commit changes===
There are two possibilities to supply patches.

'''1. Mail to Hallo Welt'''!

Send an e-mail with your patch in ([https://www.kernel.org/pub/software/scm/git/docs/git-format-patch.html git format-patch]) to support@hallowelt.com. We will commit the change for you in git where it has to go through a standardized process.

'''2. Actively participating via Git'''

We follow the procedure that is also common in the MediaWiki developer community:

*Get a developer account for MediaWiki
*Install git-review
*check out the BlueSpice code
*Commit your changes
*Changes are verified in gerrit
*When everything is ok, your changes will be accepted

On MediaWiki.org you will find a [http://www.mediawiki.org/wiki/Gerrit/Getting_started short] and a [http://www.mediawiki.org/wiki/Gerrit/Tutorial extended] tutorial.

The BlueSpice code can be found in these repositories:

mediawiki/extensions/BlueSpiceFoundation.git
mediawiki/extensions/BlueSpiceExtensions.git
mediawiki/skins/BlueSpiceSkin.git

and this is how you check out:

git clone ssh://gerrit.wikimedia.org:29418/mediawiki/extensions/BlueSpiceFoundation.git

In the repositories of BlueSpice it is necessary to have the "+2" or "Merge" permission before you can commit code to the product by yourself. Please ask Markus Glaser if you feel you need this kind of access (glaser@hallowelt.biz).

If you want to write own extensions for BlueSpice please ask for an own repository [https://www.mediawiki.org/wiki/Gerrit/New_repositories#Step_3:_Request_space_for_your_extension here]. Please follow the naming convention.

mediawiki/extensions/BlueSpiceMyWidget.git

==See also==

*https://www.mediawiki.org/wiki/How_to_become_a_MediaWiki_hacker

[[en:{{FULLPAGENAME}}]]
[[de:Wie Werde Ich ein BlueSpice Hacker]]

User:Mglaser

2021-06-17T11:51:10Z

Mglaser: create user page

SocialEntity:1827

2019-09-20T14:39:20Z

Mglaser:

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

Setup:Installation Guide/With Installer

2018-10-31T08:30:40Z

Mglaser: Backlink to installation manual

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

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

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

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

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

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

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

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

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

Reference:BlueSpiceReadConfirmation

2018-01-23T23:39:29Z

Mglaser: /* Where do I find ReadConfirmation */ erm:6691

{{BSExtensionInfobox
|desc=Ask for confirmation that an article was read by certain users
|status=stable
|developer=HalloWelt
|type=BlueSpice
|edition=BlueSpice pro
|active=Yes
|compatible=BlueSpice
|package=ReadConfirmation
|category=Quality Assurance
}}
The extension read confirmation allows to set wiki articles to be set as so that, a read confirmation is requested from certain readers, when they have read the article

==The benefits at a glance==
* You can create an active read confirmation for some articles
* You can assign articles to certain users or user groups
* Respective reading confirmation depends on version of the article

==Where do I find ReadConfirmation==
The process of read confirmation is set in the assignment management.

This special page is found in the left main navigation an invisible for those who do not have administrator rights

Note: ReadConfirmation has to be enabled per Namespace. This can be done in the namespace manager.

==How do I use read confirmation==
Create a read confirmation

When access is accessed, all articles of the wiki are listed. The "Assignments" column shows whether an article has already been assigned a read receipt or not.

 In order to provide an article with a reading confirmation, you will first find the desired article by scrolling through the following buttons in the displayed list

 Or the articles. The sorting and filtering functions can be found in the drop-down list of the column header "page title":

assign the users, select the appropriate item and click the "Edit" button above the list. A dialog box appears where you can use the drop-down list to assign the users and / or usergroups of the wiki to the article.

By clicking on the "Request read confirmation" button, you are now starting the process

Since the reading confirmation depends on the version of an article, you can repeatedly request the reading confirmation if the article has changed in the meantime. The process then starts from the beginning and the affected users are prompted again to issue a read receipt

 Received for read receipt

 After the read confirmation has been established, the respective users receive an email and a message in the wiki. This requires that the users have activated the notifications for the page assignments in their user settings:

 Regardless of the notifications, the assignments of certain users to articles are also visible in the article info.

==Accept ReadConfirmation==
For the user who has been assigned to a specific page, a prominent message block appears at the beginning of the page for read verification. This will appear every time the page is accessed until the confirmation has actually been made

==Check reading confirmation==
When all prompted users have confirmed the current version of the article, the circle in Access Management changes from red to green in the "Read" column. More details about the confirmation, e.g. The date of the confirmation, you will be found in the read confirmation logbook (see below).

==Delete assignments==
The assignments are removed either via the delete button above the list in the access management or in the "Actions" column. First, activate the corresponding article.

 The assignments for an article can only be deleted completely

==The logbooks of ReadConfirmation==
In the assignment manager you will find two icons in the "Actions" column, which lead to two logbooks

* The assignment logbook is a special page that lists all assignments and their deletions with date and actor
* The read-only confirmation log shows all confirmations of the assigned users..
[[Category:Extension]]

Reference:BlueSpiceExtendedSearch

2018-01-23T20:35:14Z

Mglaser: /* Search administration */ erm:6267

{{BSExtensionInfobox
|desc=Full-text search in articles and files, faceted search, fuzzy search, spellchecker and sorting as well as search-as-you-type and auto-complete functionality
|status=stable
|developer=HalloWelt
|type=BlueSpice
|edition=BlueSpice free, BlueSpice pro
|active=Yes
|compatible=BlueSpice
|category=Search and Navigation
|docu=https://www.mediawiki.org/wiki/Extension:ExtendedSearch
}}
__NOTOC__

BlueSpice has a superior, better organised search function than MediaWiki. This function is able to search for articles and attachments according to both title and content. The first hits are shown as you are typing the search term into the box. If you do not get a suitable hit straight away, the search results can be refined by using facets. On top of this, the search function can be expanded by further packages to extend its functionality (see below).

==Technical background==
In order to activate the extended search, you will need an applications server like Apache running, otherwise MediaWiki's search function will be used. The search function is based on Apache Soir/Lucene.

==Where can I find ExtendedSearch?==
ExtendedSearch is a special page. You will be redirected here when you do not find a suitable hit using the auto complete function.

You can find the search box above any article to the right. You can search for titles (use the arrow) or the full content (magnifying glass).

[[File:BlueSpice223-Autocomplete-en.png|thumb|none|400px|Screenshot: The first results start to appear as soon as you start to type in the query]]

As you can see in the screenshot, search results are suggested to you as you type, and you can select these too. If none of these results is suitable, you are automatically taken to the search form for the ExtendedSearch. Here you can sort the search results and use facets to filter them further.

You can also reach this search form by going to Special pages -> BlueSpice -> Extended Search. The "auto complete" function is deactivated here, otherwise it works just like the search box above the article.

==What can ExtendedSearch do?==
With the improved search function from BlueSpice you can:

* '''Search titles''': Search in a selection of areas only according to title. If the search term fully matches an existing article, you will be forwarded to it (this can be activated and deactivated). Search by title by using the arrow button to the right of the search box.
* '''Search the full content''': Search the complete content in a selection of areas. This is done by using the magnifying glass button to the right of the search box.

* Search '''uploaded or linked files''' (Office documents and PDFs).

* Search image data

* '''Search-as-you-type''' and '''auto-complete''': As soon as you start typing a search term into the box at the top right, the system starts searching and giving you relevant suggestions. These suggestions are shown in a drop-down menu below the entry box and you can choose individual suggestions by clicking on them. This forwards you to the article named. This function is particularly good for locating articles with long titles or subpages. If the search term is not found automatically, the menu immediately gives you the possibilities "Suggest article" and "Create article".

* Ignore '''upper and lower case''' (case-insensitive). Example: Searching for "keyboard" gives the same results as for "Keyboard".

* Search with the operators '''AND, OR, NOT'''. Example: Searching for "keyboard OR keypad" gives results which contain at least one of these two terms.

* Search with '''wildcards''':
** <nowiki>*</nowiki>(the star replaces an arbitrary number of characters). This allows you to truncate your search terms to the left or to the right. This means you can search for "User*" (trunkated to the right) or "*preferences" (truncated to the left).
** ''?'' (the question mark replaces a single letter)

* '''Search for phrases''' (filter according to author, category and namespace).

* '''Fuzzy search''': this means that imprecise search entries (for example typing mistakes) suck as ''keyboard'' will be found and a corrected version will be suggested to you.

* '''Sentence components''' which belong together will be found, like ''"computer keyboard"''

==What can I do with the search results?==
===Sorting results===
[[File:BlueSpice2-Suche-Sortierung-en.png|thumb|none|700px|Screenshot: The display of the search results showing the possibile sorting criteria.]]

The search results are initially sorted according to relevance. You can, however, sort them by title or type or chronologically. The criteria for sorting are shown in a block next to the results and can be chosen by clicking on them.

The current choice/sorting is highlighted in bold. The current sorting direction is shown with an arrow symbol behind the sort criterion and can be changed by clicking on it.

You can find links to further search results right at the bottom. These are shown in the following way: < 1 2 3 '''4''' 5 .. 66 > : the arrow to the right takes you to the next page. The current page is highlighted in bold.

===Limit the search with facets===
[[File:BlueSpice2-Suche-Facetten-en.png|thumb|left|220px|Screenshot: Filter (facet) selection in ExtendedSerach]]You can further restrict the search results by using facets (filters) which you can find on the left hand side. The following facets are available:

* '''Namespace filter''': You can restrict your search to one namespace or a selection of several. You can also select particular namespaces which should be searched or blanked our in advance in the search settings (under "Preferences"). 

* '''Category filter''': The extended search lets you search within one category or a selection of them. You can also select particular categories which should be searched or blanked our in advance in the search settings (under "Preferences"). 

* '''Type filter''': This lets you filter whether you will search for or in wiki articles (shown as a W on a white background before the hit), for or in PDF, Word, EXCEL or other documents. 

* '''Author filter''': You can give the author who, for example, you think may have written the article. 

 

==Tips for using the extended search==
* '''Configure search''': A wiki administrator can set up which filters can be chosen in the [[Preferences]], and also which search function comes as default when a user presses enter.

* '''Personal search preferences''': If you want to change the number of hits shown in a search, you can do this in your MediaWiki personal preferences. You can also change the lines per hit and the characters per line. But you can also change the standard namespaces for your searches here.

* So that your search delivers the appropriate results, the '''content must be regularly indexes''' (see below under Search administration). This normally occurs "on the fly", i.e. whenever there are new articles/files, changes to the content of articles, or an article is deleted or restored. In the indexing has not been done, searching will give no results. If the indexing is not up to date, new articles and files will not be able to be found.

* Anyone can search if they have '''read permission in the wiki'''. This means that results are only shown from namespaces in which the user has '''read''' permission. If you cannot find an article even though you know it exists, it may be that you do not have the relevant access permission. Permissions are set up via the [[PermissionManager]].

* Even though the namespace "book" is marked as not searchable, content will be found from within it. "'''Not searchable'''" means, here, that the namespace is not searched by default. These standard settings can be overwritten in the user preferences. Whether a page is displayed as a hit depends on the readability of the page and ''not'' on the [[Namespacemanager|namespace's search settings]].

==Search administration==
The following functions are available in the wiki admin area.

* The number of hits shown per page can be set up at WikiAdmin->Preference->Search->LimitResultsDefault
* Weighting of search results: Administrators can prioritize namespaces for the search results. Just go to the [[NamespaceManager|namespace manager]] and mark the checkbox at “content namespace” for the namespace you want to prioritize. Contents of this namespace will be preferred in the search results

==Further search possibilities==
* [[ServiceCenter]]: Create a preconfigured search portal with a list of the top five results

* [[WikiExplorer]]: Filter metadata from the wiki to find articles using particular criteria.

==Troubleshooting==
[http://sourceforge.net/p/bluespice/bugs/227/ Problems with the Extended Search]

[http://sourceforge.net/p/bluespice/bugs/235/ Extended Search stellt ohne Vorankündigung den Betrieb ein]

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

[[Category:Extension]]

Reference:NamespaceManager

2018-01-23T20:08:51Z

Mglaser: erm:6450

{{BSExtensionInfobox
|desc=Administration interface for adding, editing and deleting namespaces
|status=stable
|developer=HalloWelt
|type=BlueSpice
|edition=BlueSpice free, BlueSpice pro
|active=Yes
|compatible=BlueSpice
|category=Administration
|docu=https://www.mediawiki.org/wiki/Extension:NamespaceManager_(BlueSpice)
}}
__TOC__

 '''NamespaceManager''' displays information about the [https://www.mediawiki.org/wiki/Help:Namespaces namespaces] used in a table. It also lets you change the settings and create new namespaces.

==Where can I find the NamespaceManager?==
Firstly, you need to have administration permissions in order to call up NamespaceManager. If you have these permissions, you can find the link"NamespaceManager" in the left hand navigation bar under "Admin". Click on the link and you will be taken to the administration page.

::: [[File:NaSpceMnger1.jpg|500x307px]]

==Usage / Features==
The NamespaceManager is visible for users with administration permissions.

NamespaceManager alows you:

* Create namespaces.
* Edit namespaces.
* Delete namespaces .
* Turn on or off features on namespace level. The following settings can be set:
** Subpages: Activates the use of subpages, which introduce some hierarchical organization into wiki pages.
** Search by default: this automatically includes pages of a certain namespace in the standard search results. These standard settings can be overwritten in the user preferences. Please note: A page will be shown as a match of a search requests if the user has the reading rights also. The search settings in the namespace, doesn't affect restricted reading rights.
** Content namespace: Contents from this namespace will be prioritized in the search results.
** Read Confirmation: The extension ReadConfirmation can be activated for this namespace.
** Semantic MediaWiki: The extension Semantic MediaWiki can be activated for this namespace.
** CategoryCheck: Editors are asked to set a category before saving a page.
* Sort list: The special page allows to sort the table, set columns and filters.

==The functionality of NamespaceManager==
===Creating a namespace===
You can see all the existing namespaces listed in the table. This button [[File:Btn-plus.png]] lets you add a new namespace. A namespace's name can contain from 2 to 100 characters. You can choose any of the characters [A-Za-z0-9_ A-Za-z0-9_] and all the accents and umlauts in the UTF-8 character set.

::: [[File:NaSpMa2.jpg|500x288px]]
===Editing a namespace===
Choose a namespace and click on this icon to edit:

::: [[File:NaSpceMnger2.jpg|500x307px]]
The following definitions can be made for namespaces:

::: [[File:NaSpMa5.jpg|500x275px]]
:
:* '''has subpages''': Allows the use of subpages. These are pages which maintain their hierarchical relationship.
:* '''in standard search''': this automatically includes the namespace when searching. These standard settings can be overwritten in the user preferences. The question of whether a page will be shown as a match to a search depends on its readability, not on the search settings of the namespace.
:* '''content namespace''': Contents from this namespace will be prioritized in the search results.
:* '''FlaggedRevs''': This choice is only possible if the package [[Teamwork|<nowiki>[teamwork]</nowiki>]] is installed, because teamwork includes the extension [[FlaggedRevisions]]. If you tick the box, FlaggedRevisions will be activated for this namespace.

Note: it is not possible to change the name of a discussion namespace, as this is associated with the corresponding custon namespace.

===Deleting a namespace===
The button [[File:Btn-minus.png]] can be used to delete a selected namespace. System namespaces and namespaces not created in the manager can not be deleted. You will be warned that you are about to delete the Namespace for good. If there are articles already in your namespace, you can choose what happens to them:

* they are deleted
* they are moved to the mainspace
* they are moved to the mainspace with a suffix "(from )"

::: [[File:NaSpceMnger3.jpg|500x303px]]
 [[en:{{FULLPAGENAME}}]][[de:NamespaceManager]]

Note: it is not possible to separately delete a discussion namespace, as this is associated with the corresponding custon namespace.

==Try it!==
[https://en.demo.bluespice.com/wiki/Main_Page Demo BlueSpice]
[[Category:Extension]]

Archive:DataValues Interfaces

2017-12-07T12:07:00Z

Mglaser: Changed categories.

{{BSExtensionInfobox
|desc=Defines interfaces for ValueParsers, ValueFormatters and ValueValidators.
|status=stable
|developer=Jeroen De Dauw
|type=MediaWiki
|edition=BlueSpice free
|compatible=MediaWiki
|category=Editor
|docu=https://www.mediawiki.org/wiki/Extension:DataValuesInterfaces
}}
'''DataValues''' Interfaces is a small PHP library that defines a set of interfaces for parsers, formatters and validators.

==Requirements==
PHP 5.5 or later

==Installation==
You can use [http://getcomposer.org/ Composer] to download and install this package as well as its dependencies. Alternatively you can simply clone the git repository and take care of loading yourself.

==Manual==
Get the DataValues Interfaces code, either via git, or some other means. Also get all dependencies. You can find a list of the dependencies in the "require" section of the composer.json file. Load all dependencies and the load the DataValues Interfaces library by including its entry point: Interfaces.php.

==Tests==
This library comes with a set up PHPUnit tests that cover all non-trivial code. You can run these tests using the PHPUnit configuration file found in the root directory. The tests can also be run via TravisCI, as a TravisCI configuration file is also provided in the root directory.

'''Source: [https://github.com/DataValues/Interfaces/blob/master/README.md GitHub]'''
[[Category:BlueSpice pro]]

Reference:BlueSpicePermissionManager

2017-10-16T12:35:23Z

Mglaser: /* Preferences */ updated screenshot to current version

<bookshelf src="Book:Admin manual" />
__NOTOC__
PermissionManager is for managing rights or permissions at a group and namespace level. User permissions are defined via the groups in which the users are placed.

==Technical background==
In order to hide the syntax of permission management in Mediawiki and the Lockdown extension, a dialogue is created in which the permissions can be set and easily viewed. A special form of group permissions is permission templates (rolls). GroupManager, NamespaceManager and Permissions-TemplatesManager are special extensions or dialogues.

==Where can I find the function PermissionManager?==
Firstly, you will need admin rights in order to call up the permission manager. If you have the right permissions, you will find "Permission manager" in the left navigation bar under "Admin". Click on the link and you will be taken to the administration page.
[[File:BlueSpice223-PermissionManager-Navigation-en.png|thumb|none|220px|Sceenshot: Open the permission manager in the admin area]]

==The functionality of PermissionManager==
Choose one of the three work modes in the drop-down menu:

* '''Group:''' An array is displayed for a chosen user group showing the namespaces and the permissions attached.
* '''Namespace:''' An array is displayed for a chosen namespace showing the user groups and the permissions attached.
* '''Permission:''' An array is displayed for a chosen permission showing the user groups and the namespaces.

===PERMISSION MANAGER EXPLAINED===
Permission manager is used to grant or revoke permissions.
On the left side there is Groups menu that can be shown by clicking on the arrow at the top.
It shows permission groups hierarchy. The asterisk (*) group includes all users that enter wiki, regardless of whether they are logged in or not. The "user" group applies to all logged in users. This groups holds different sub-groups,
some of which are default to MediaWiki while others may be custom. Clicking on the group name shows (in the list to the right) all permissions granted to the group. You can add permissions by checking appropriate check box.

Assigning permissions
Permissions can be granted for entire wiki (by checking "Wiki" checkbox) or only for selected namespaces.
Assigning permissions follows an inheritance model. If you add permission to (*) group it will also be assigned to "user" and all sub-groups of "user". It will show like green unchecked field. When a permission is not explicitly
granted to a group but its inherited from a parent group, field will appear as green and not checked

When explicitly adding permission to one groups (for entire wiki or just for one namespace) all other groups in the same hierarchy level will lose this permission.

Templates
You can create templates for permissions. Templates represent collection of permissions to make permission management more straight-forward. Templates are added/edited in Template editor (click on "Edit templates" buttom at the bottom).
Enter name for template, description and select permissions that will be managed by this template.
When template is added it will appear at the top of the permission lists and assigning it to a group will grant all permissions defined in the template, and at the same time revoke these permissions from other groups in the same hierarchy level.

Assign the permissions as you want in the table. The permissions are colour coded. The explatation for the coding can be found in "Good to know". You can also work with permission-templates, also called '''roles'''. Such roles contain a collection of permissions.
[[File: BlueSpice223-PermissionManager-Dialog-en.png|thumb|none|700px|Screenshot: Settings in the PermissionManager]]

'''Good to know:'''

* Assigning permissions to groups and namespaces can be done either by choosing a permission-template (role) or by choosing individual permissions.
* Permission-templates are defined by using unique (descriptive) names.
* A permission-template is a freely definable collection of permissions.
* Management of permission-templates is a component of the PermissionManager (with its own dialogue).

* The first step to set permissions is to set them in the first folder - for the whole wiki (*).
* The permissions you set for a group, will be set automatically for the following folders, for the wiki and all namespaces (green coloured - not checked).
* If you want to give the groups more/different permissions - maybe in different namespaces - you can select them manually, but if you do that, the other groups, in the same hierarchy level, '''lose that permission''' for the namespace you choosen.
* Colour coding:
** no colour " border="0"

'''User permissions'''

'''Definition'''

'''User group'''

read

lets the user view pages

user

edit

allows the user to edit unprotected pages

user

createpage

allows the user to create new pages (edit permission is needed here)

sysop

createtalk

allows the user to create a new talk page (edit permission is needed here)

sysop

writeapi

controls access to the write API ($wgEnableWriteAPI must be set to true), this means commands can be given using this external interface.

sysop

upload

allows the creation of new pictures and files, i.e. pictures and files can be uploaded

sysop

files

allows the user to view files which have been uploaded (needs secure:Image), e.g. unregistered users can not see word or PDF documents.

user

rollback

lets the user roll back the article with a click, restoring a previous version from another author. If this permission is activated, you can find the rollback button under History next to "undo" by the last change.

sysop

delete

allows the user to delete pages (can be found under ''more'')

sysop

move

allows the user to change the title of unprotected pages (edit permission is needed here) via ''move'' (can be found under ''more'')

sysop

move-subpages

this moves subpages along with the main page to which they are assigned (move permission is needed here). If the user has this permission, subpages are automatically moved with main pages.

sysop

protect

allows the user to lock a page preventing it from being edited or moved (''protect'' can be found under ''more''). Editing a protected page is possible for those with this permission.

sysop

block

allows the user to block IP addresses and registered users. There are various block options including stopping a user from editing and from registering new accounts and automatic blocking of other users with the same IP address. This takes place via the special page ''Block user''.

sysop

createaccount

allows the user to create new accounts (via WikiAdmin - User manager)

sysop

bigdelete

allows the user to delete pages which are larger than the limit $wgDeleteRevisionsLimit. The variable DeleteRevisionsLimit can be set up in advance.

sysop

undelete

allows the user to restore deleted pages

sysop

editusercssjs

allows the user to create and edit their own Monobook style and scripts

user

import

allows the user to import an article from another wiki in one go ('''Transwiki''')

sysop

markbotedits

lets the user mark a rollback as a bot edit

-

suppressredirect

allows moving a page without automatically setting up a redirect. A token can be placed when the page is moved

sysop

apihighlimits

gives a user a higher limit for API queries; this ia a special permission to allow several actions to be carried out at once

sysop

browsearchive

allows the user to search for prefixes of titles of deleted pages via Special:Undelete

sysop

noratelimit

The user is not affected by rate limits

sysop

See: [http://www.mediawiki.org/wiki/Manual:User_rights#List_of_Permissions User Rights]

===BlueSpice===
'''WikiAdmin'''

{| class="contenttable" style="width: 100%;" border="0"
|-
! style="border: 1px solid #ebecec; width: 20%;"|
'''User permissions'''

! style="border: 1px solid #ebecec;"|
'''Definition'''

! style="border: 1px solid #ebecec;"|
'''user group'''

|-
| style="border: 1px solid #ebecec;"|
editadmin

| style="border: 1px solid #ebecec;"|
gives the user access to the module ''Search'' and, where appropriate ''PageTemplates'' in the WikiAdmin area

| style="border: 1px solid #ebecec;"|
sysop

|-
| style="border: 1px solid #ebecec;"|
useradmin

| style="border: 1px solid #ebecec;"|
gives the user access to the module ''User'' and if appropriate ''Groups'' in the WikiAdmin area

| style="border: 1px solid #ebecec;"|
sysop

|-
| style="border: 1px solid #ebecec;"|
wikiadmin

| style="border: 1px solid #ebecec;"|
grants the user full access to the WikiAdmin area

| style="border: 1px solid #ebecec;"|
sysop

|}

'''Responsible editor'''

{| class="contenttable" style="width: 100%;" border="0"
|-
! style="border: 1px solid #ebecec; width: 20%;"|
'''User permissions'''

! style="border: 1px solid #ebecec;"|
'''Definition'''

! style="border: 1px solid #ebecec;"|
'''User group'''

|-
| style="border-color: #ebecec; border-style: solid;"|
responsibleeditors-changeresponsibility

| style="border-color: #ebecec; border-style: solid;"|
lets the user change the responsible editors for a page.

| style="border-color: #ebecec; border-style: solid;"|
sysop

|-
| style="border-color: #ebecec; border-style: solid;"|
responsibleeditors-viewspecialpage

| style="border-color: #ebecec; border-style: solid;"|
lets the user see the overview of the responsible editors.

| style="border-color: #ebecec; border-style: solid;"|
user

|-
| style="border-color: #ebecec; border-style: solid;"|
responsibleeditors-takeresponsibility

| style="border-color: #ebecec; border-style: solid;"|
lets the user be assigned as a responsible editor for an article.

| style="border-color: #ebecec; border-style: solid;"|
user

|}

'''SecureFileStore'''

{| class="contenttable" style="width: 100%;" border="0"
|-
! style="border: 1px solid #ebecec; width: 20%;"|
'''User permissions'''

! style="border: 1px solid #ebecec;"|
'''Definition'''

! style="border: 1px solid #ebecec;"|
'''User group'''

|-
| style="border-color: #ebecec; border-style: solid;"|
viewfiles

| style="border-color: #ebecec; border-style: solid;"|
lets the user download and/or view files which have been uploaded.

| style="border-color: #ebecec; border-style: solid;"|user
|}

'''ExtendedSearch'''

{| class="contenttable" style="width: 100%;" border="0"
|-
! style="border: 1px solid #ebecec; width: 20%;"|
'''User permissions'''

! style="border: 1px solid #ebecec;"|
'''Definition'''

! style="border: 1px solid #ebecec;"|
'''User group'''

|-
| style="border: 1px solid #ebecec;"|
searchfiles

| style="border: 1px solid #ebecec;"|
allows the user to search for files. Lets the user tick the extended search option ''Search files''.

| style="border: 1px solid #ebecec;"|user
|}

'''Review'''

{| class="contenttable" style="width: 100%;" border="0"
|-
! style="width: 20%; border: 1px solid #ebecec;"|
'''User permissions'''

! style="border-color: #ebecec; border-style: solid;"|
'''Definition'''

! style="border-color: #ebecec; border-style: solid;"|
'''User group'''

|-
| style="border-color: #ebecec; border-style: solid;"|
workflowview

| style="border-color: #ebecec; border-style: solid;"|
lets the user view work flows

| style="border-color: #ebecec; border-style: solid;"|user
|-
| style="border-color: #ebecec; border-style: solid;"|
workflowedit

| style="border-color: #ebecec; border-style: solid;"|
lets the user create, edit, change and delete work flows

| style="border-color: #ebecec; border-style: solid;"|sysop
|}

'''SecureFileStore'''

{| class="contenttable" style="width: 100%;" border="0"
|-
! style="border: 1px solid #ebecec; width: 20%;"|
'''User permissions'''

! style="border: 1px solid #ebecec;"|
'''Definition'''

! style="border: 1px solid #ebecec;"|
'''user group'''

|-
| style="border-color: #ebecec; border-style: solid;"|
viewfiles

| style="border-color: #ebecec; border-style: solid;"|
lets the user download and/or view files which have been uploaded.

| style="border-color: #ebecec; border-style: solid;"|user
|}

'''Shoutbox'''

{| class="contenttable" style="width: 100%;" border="0"
|-
! style="border: 1px solid #ebecec; width: 20%;"|
'''User permissions'''

! style="border: 1px solid #ebecec;"|
'''Definition'''

! style="border: 1px solid #ebecec;"|
'''user group'''

|-
| style="border-color: #ebecec; border-style: solid;"|
readshoutbox

| style="border-color: #ebecec; border-style: solid;"|
lets the user read commentaries made using the Shoutbox.

| style="border-color: #ebecec; border-style: solid;"|user
|-
| style="border-color: #ebecec; border-style: solid;"|
writeshoutbox

| style="border-color: #ebecec; border-style: solid;"|
lets the user add comments to the Shoutbox

| style="border-color: #ebecec; border-style: solid;"|sysop
|}

'''Universal Export'''

{| class="contenttable" style="width: 100%;" border="0"
|-
! style="border: 1px solid #ebecec; width: 20%;"|
'''User permissions'''

! style="border: 1px solid #ebecec;"|
'''Definition'''

! style="border: 1px solid #ebecec;"|
'''user group'''

|-
| style="border-color: #ebecec; border-style: solid;"|
universalexport-export

| style="border-color: #ebecec; border-style: solid;"|
allows the user to create PDF files.

| style="border-color: #ebecec; border-style: solid;"|user
|-
| style="border-color: #ebecec; border-style: solid;"|
universalexport-export-with-attachments

| style="border-color: #ebecec; border-style: solid;"|
allows the user to create PDF files with file attachments.

| style="border-color: #ebecec; border-style: solid;"|user
|}

===MediaWiki Erweiterungen===
'''Flagged Revisions'''

{| class="contenttable" style="width: 100%;" border="0"
|-
! style="border-image: initial; width: 20%; border: 1px solid #ebecec;"|
'''User permissions'''

! style="border: 1px solid #ebecec;"|
'''Definition'''

! style="border: 1px solid #ebecec;"|
'''user group'''

|-
| style="border: 1px solid #ebecec;"|
review

| style="border: 1px solid #ebecec;"|
lets the user review changes.

| style="border: 1px solid #ebecec;"|sysop
|-
| style="border: 1px solid #ebecec;"|
validate

| style="border: 1px solid #ebecec;"|
lets the user validate changes.

| style="border: 1px solid #ebecec;"|-
|-
| style="border: 1px solid #ebecec;"|
autoreview

| style="border: 1px solid #ebecec;"|
automatically marks those edits which a user has made themselves as reviewed

| style="border: 1px solid #ebecec;"|sysop
|-
| style="border: 1px solid #ebecec;"|
unreviewedpages

| style="border: 1px solid #ebecec;"|
lets the user see the page ''Special:Unreviewed pages''.

| style="border: 1px solid #ebecec;"|sysop
|}

'''Nuke'''

{| class="contenttable" style="width: 100%;" border="0"
|-
! style="border-image: initial; width: 20%; border: 1px solid #ebecec;"|
'''User permissions'''

! style="border: 1px solid #ebecec;"|
'''Definition'''

! style="border: 1px solid #ebecec;"|
'''user group'''

|-
| style="border: 1px solid #ebecec;"|
nuke

| style="border: 1px solid #ebecec;"|
allows the user to delete articles on mass.

| style="border: 1px solid #ebecec;"|sysop
|}


==Permission-templates==
PermissonManager lets you make regularly recurring assignments easily by using permission templates, or roles. For example, when you need to supply a new namespace with the relevant group permissions.

===Create templates===
To create a new role, click on "Admin" in the left hand navigation bar. Then choose "Permission manager". And click on "Edit templates".

===Add template===
To add a new role, you can simply click the "New" button. Existing templates can be selected and then edited. The description is only for internal use for wiki admins. All permissions known to the wiki are listed here and can be selected and deselected.

[[File:BlueSpice223-PermissionManager-Template-en.png|thumb|none|700px|Screenshot: Template editor of the permission managers]]

===Assign group permissions===
After saving, the groups will be chosen which should be assigned the permissions of the role. A simple click on the desired namespace is enough to validate the role.

==Preferences==
Have a look at the [[Preferences|admin preferences]] to define the PermissionManager.
[[File:BlueSpice227-PermissionManager-AdminEinstellungen-en.png|thumb|none|400px|Screenshots: Admin preferences]]

{{Box_Links-en | Thema1 =[[UserManager|User Manager]] | Thema2 =[[GroupManager|Group Manager]] | Thema3 = | Thema4 = }}

[[Category:Extension]]
[[Category:BlueSpice free]]
[[en:{{FULLPAGENAME}}]][[de:PermissionManager]]

File:BlueSpice227-PermissionManager-AdminEinstellungen-en.png

2017-10-16T12:35:02Z

Mglaser:

Archive:Preferences

2017-10-16T12:32:52Z

Mglaser: /* BlueSpice - preferences */ -lockmode

__TOC__

'''Preferences''' is an extension allowing wiki administrators to change key settings of the wiki, without resorting to scripts and manual settings in LocalSetting.php file. These settings are wiki-wide, although some of them can be overriden on user level through [[UserPreferences]].

==Technical background==
Preferences lets you control and set various aspects of BlueSpice extensions.

==Where can I find the Preferences function?==
Firstly, you need to have administration permissions in order to call up Preferences. If you have the correct permissions, you will be able to see the link "Preferences" in the "Global settings" and then on "Preferences" as you see on the image below. Click on the link and you will be taken to the administration page.

::: [[File:PreferencesHD1.jpg|500x309px]]
::: [[File:PreferencesHD2.jpg|500x301px]]
==The functionality of Preferences==
The display shows different areas for the individual extensions.

::: [[File:PreferencesHD3.jpg|500x308px]]
Preferences page contains many sections that are represented by expandable tabs. By default all tabs are collapsed. More information on individual settings of each of these extensions you can find on those extension's pages.

For example:

::: [[File:PreferencesHD4.jpg|500x303px]]
::: [[File:PreferencesHD5.jpg|500x309px]]

===BlueSpice - preferences===
{| class="wikitable" border="0"
|-
! style="width: 200px; height: 40px;"|Setting
! style="width: 1100px; height: 40px;"|Description
|-
| style="width: 200px; height: 40px;"|
||
|-
| style="width: 200px; height: 40px;"|'''[https://en.help.bluespice.com/wiki/Authors Authors]'''
||Preferences for profile pictures.
|-
| style="width: 200px; height: 40px;"|'''[https://en.help.bluespice.com/wiki/Avatars Avatars]'''
||Size and defaults
|-
| style="width: 200px; height: 40px;"|'''[https://en.help.bluespice.com/wiki/Blog Blog]'''
||Display of blog entries
|-
| style="width: 200px; height: 40px;"|BlueSpice
||Special preferences for BlueSpice. You can also set which data formats allowed here (by default: png, gif, jpg, jpeg, doc, docx, pdf, xls).
|-
| style="width: 200px; height: 40px;"|'''[https://en.help.bluespice.com/wiki/Bookshelf Bookshelf]'''
||
|-
| style="width: 200px; height: 40px;"|'''[https://en.help.bluespice.com/wiki/ContextMenu ContextMenu]'''
||
|-
| style="width: 200px; height: 40px;"|'''[https://en.help.bluespice.com/wiki/DashBoards DashBoards]'''
||Link the site logo to the dashboards
|-
| style="width: 200px; height: 40px;"|'''[https://en.help.bluespice.com/wiki/ExtendedSearch ExtendedSearch]'''
||
|-
| style="width: 200px; height: 40px;"|'''[https://en.help.bluespice.com/wiki/ExtendedStatistics ExtendedStatistics]'''
||Settings for BlueSpice statistics e.g. exclude certain users
|-
| style="width: 200px; height: 40px;"|'''[https://en.help.bluespice.com/wiki/FlaggedRevsConnector FlaggedRevsConnector]'''
||
|-
| style="width: 200px; height: 40px;"|'''[https://en.help.bluespice.com/wiki/InsertCategory InsertCategory]'''
||Insert categories include its parents
|-
| style="width: 200px; height: 40px;"|Insert link
||Enable links to local files
|-
| style="width: 200px; height: 40px;"|Latex Renderer
||
|-
| style="width: 200px; height: 40px;"|Menu customizer
||
|-
| style="width: 200px; height: 40px;"|'''[https://en.help.bluespice.com/wiki/PageAssignments PageAssignments]'''
||
|-
| style="width: 200px; height: 40px;"|Page information
||
|-
| style="width: 200px; height: 40px;"|'''[https://en.help.bluespice.com/wiki/PageTemplates PageTemplates]'''
||Above all for combining page templates with namespaces.
|-
| style="width: 200px; height: 40px;"|Pages visited
||Limit of entries, namespaces, ...
|-
| style="width: 200px; height: 40px;"|PasteImage
||
|-
| style="width: 200px; height: 40px;"|Permission manager
||Settings for backup of rights configuration
|-
| style="width: 200px; height: 40px;"|PiwikConnector
||
|-
| style="width: 200px; height: 40px;"|Rated comments
||
|-
| style="width: 200px; height: 40px;"|Rating
||
|-
| style="width: 200px; height: 40px;"|Readers
||
|-
| style="width: 200px; height: 40px;"|Reminder
||
|-
| style="width: 200px; height: 40px;"|Review
||
|-
| style="width: 200px; height: 40px;"|'''[https://en.help.bluespice.com/wiki/SaferEdit SaferEdit]'''
||Organise autosaving while editing.
|-
| style="width: 200px; height: 40px;"|'''[https://en.help.bluespice.com/wiki/Shoutbox Shoutbox]'''
||Setings for the comment box.
|-
| style="width: 200px; height: 40px;"|'''[https://en.help.bluespice.com/wiki/Showtime Showtime]'''
||
|-
| style="width: 200px; height: 40px;"|'''[https://en.help.bluespice.com/wiki/FlexiSkin Skin]'''
||
|-
| style="width: 200px; height: 40px;"|'''[https://en.help.bluespice.com/wiki/SmartList SmartList]'''
||Configure the latest changes function (previously called "Infobox")
|-
| style="width: 200px; height: 40px;"|Status bar
||Display statbar and shows the order.
|-
| style="width: 200px; height: 40px;"|Syntax highlighter
||e.g. link URLs
|-
||'''[https://en.help.bluespice.com/wiki/UniversalExport UniversalExport]'''
||
|-
| style="width: 200px; height: 40px;"|Universal export PDF module
||
|-
| style="width: 200px; height: 40px;"|UniversalExport Book PDF Module
||
|-
| style="width: 200px; height: 40px;"|UniversalExport HTML Module
||
|-
| style="width: 200px; height: 40px;"|'''[https://en.help.bluespice.com/wiki/VisualDiff VisualDiff]'''
||
|-
| style="width: 200px; height: 40px;"|'''[https://en.help.bluespice.com/wiki/VisualEditor VisualEditor]'''
||Settings for the WYSIWYG editor.
|-
| style="width: 200px; height: 40px;"|'''[https://en.help.bluespice.com/wiki/WatchList WatchList]'''
||
|-
| style="width: 200px; height: 40px;"|Who is online?
||
|}

{{Box_Links-en | Thema1 =[[UserPreferences|User Preferences]] | Thema2 =[[ExtensionInfo|Information on installed extensions]] | Thema3 =[[Special_pages|Special Pages]] | Thema4 = }}

[[Category:Extension]]
[[Category:BlueSpice free]]
[[en:{{FULLPAGENAME}}]][[de:Einstellungen]]

==Try it!==
[https://en.demo.bluespice.com/wiki/Main_Page BlueSpiceDemo]

Reference:BlueSpiceExtendedSearch

2017-09-12T13:59:32Z

Mglaser: /* Case study */

__NOTOC__

BlueSpice has a superior, better organised search function than MediaWiki. This function is able to search for articles and attachments according to both title and content. The first hits are shown as you are typing the search term into the box. If you do not get a suitable hit straight away, the search results can be refined by using facets. On top of this, the search function can be expanded by further packages to extend its functionality (see below).

==Technical background==
In order to activate the extended search, you will need an applications server like Apache running, otherwise MediaWiki's search function will be used. The search function is based on Apache Soir/Lucene.

==Where can I find ExtendedSearch?==
ExtendedSearch is a special page. You will be redirected here when you do not find a suitable hit using the auto complete function.

You can find the search box above any article to the right. You can search for titles (use the arrow) or the full content (magnifying glass).

[[File:BlueSpice223-Autocomplete-en.png|thumb|none|400px|Screenshot: The first results start to appear as soon as you start to type in the query]]

As you can see in the screenshot, search results are suggested to you as you type, and you can select these too. If none of these results is suitable, you are automatically taken to the search form for the ExtendedSearch. Here you can sort the search results and use facets to filter them further.

You can also reach this search form by going to Special pages -> BlueSpice -> Extended Search. The "auto complete" function is deactivated here, otherwise it works just like the search box above the article.

==What can ExtendedSearch do?==
With the improved search function from BlueSpice you can:

* '''Search titles''': Search in a selection of areas only according to title. If the search term fully matches an existing article, you will be forwarded to it (this can be activated and deactivated). Search by title by using the arrow button to the right of the search box.
* '''Search the full content''': Search the complete content in a selection of areas. This is done by using the magnifying glass button to the right of the search box.

* Search '''uploaded or linked files''' (Office documents and PDFs).

* Search image data

* '''Search-as-you-type''' and '''auto-complete''': As soon as you start typing a search term into the box at the top right, the system starts searching and giving you relevant suggestions. These suggestions are shown in a drop-down menu below the entry box and you can choose individual suggestions by clicking on them. This forwards you to the article named. This function is particularly good for locating articles with long titles or subpages. If the search term is not found automatically, the menu immediately gives you the possibilities "Suggest article" and "Create article".

* Ignore '''upper and lower case''' (case-insensitive). Example: Searching for "keyboard" gives the same results as for "Keyboard".

* Search with the operators '''AND, OR, NOT'''. Example: Searching for "keyboard OR keypad" gives results which contain at least one of these two terms.

* Search with '''wildcards''':
** <nowiki>*</nowiki>(the star replaces an arbitrary number of characters). This allows you to truncate your search terms to the left or to the right. This means you can search for "User*" (trunkated to the right) or "*preferences" (truncated to the left).
** ''?'' (the question mark replaces a single letter)

* '''Search for phrases''' (filter according to author, category and namespace).

* '''Fuzzy search''': this means that imprecise search entries (for example typing mistakes) suck as ''keyboard'' will be found and a corrected version will be suggested to you.

* '''Sentence components''' which belong together will be found, like ''"computer keyboard"''

==What can I do with the search results?==
===Sorting results===
[[File:BlueSpice2-Suche-Sortierung-en.png|thumb|none|700px|Screenshot: The display of the search results showing the possibile sorting criteria.]]

The search results are initially sorted according to relevance. You can, however, sort them by title or type or chronologically. The criteria for sorting are shown in a block next to the results and can be chosen by clicking on them.

The current choice/sorting is highlighted in bold. The current sorting direction is shown with an arrow symbol behind the sort criterion and can be changed by clicking on it.

You can find links to further search results right at the bottom. These are shown in the following way: < 1 2 3 '''4''' 5 .. 66 > : the arrow to the right takes you to the next page. The current page is highlighted in bold.

===Limit the search with facets===
[[File:BlueSpice2-Suche-Facetten-en.png|thumb|left|220px|Screenshot: Filter (facet) selection in ExtendedSerach]]You can further restrict the search results by using facets (filters) which you can find on the left hand side. The following facets are available:

* '''Namespace filter''': You can restrict your search to one namespace or a selection of several. You can also select particular namespaces which should be searched or blanked our in advance in the search settings (under "Preferences"). 

* '''Category filter''': The extended search lets you search within one category or a selection of them. You can also select particular categories which should be searched or blanked our in advance in the search settings (under "Preferences"). 

* '''Type filter''': This lets you filter whether you will search for or in wiki articles (shown as a W on a white background before the hit), for or in PDF, Word, EXCEL or other documents. 

* '''Author filter''': You can give the author who, for example, you think may have written the article. 

 

==Tips for using the extended search==
* '''Configure search''': A wiki administrator can set up which filters can be chosen in the [[Preferences]], and also which search function comes as default when a user presses enter.

* '''Personal search preferences''': If you want to change the number of hits shown in a search, you can do this in your MediaWiki personal preferences. You can also change the lines per hit and the characters per line. But you can also change the standard namespaces for your searches here.

* So that your search delivers the appropriate results, the '''content must be regularly indexes''' (see below under Search administration). This normally occurs "on the fly", i.e. whenever there are new articles/files, changes to the content of articles, or an article is deleted or restored. In the indexing has not been done, searching will give no results. If the indexing is not up to date, new articles and files will not be able to be found.

* Anyone can search if they have '''read permission in the wiki'''. This means that results are only shown from namespaces in which the user has '''read''' permission. If you cannot find an article even though you know it exists, it may be that you do not have the relevant access permission. Permissions are set up via the [[PermissionManager]].

* Even though the namespace "book" is marked as not searchable, content will be found from within it. "'''Not searchable'''" means, here, that the namespace is not searched by default. These standard settings can be overwritten in the user preferences. Whether a page is displayed as a hit depends on the readability of the page and ''not'' on the [[Namespacemanager|namespace's search settings]].

==Search administration==
The following functions are available in the wiki admin area.

* [[SearchOptions|Search indexing]]
** Create new index: deletes the index and regenerates completely from now
** Overwrite index: generates a new index without deleting the old one
** Delete index

* Link to the statistics (statistics on search queries in the wiki). If you want statistics about search queries, then those queries made with the auto complete feature in the search box are not included.

* The number of hits shown per page can be set up at WikiAdmin->Preference->Search->LimitResultsDefault
* Weighting of search results: Administrators can prioritize namespaces for the search results. Just go to the [[NamespaceManager|namespace manager]] and mark the checkbox at “content namespace” for the namespace you want to prioritize. Contents of this namespace will be preferred in the search results

==Further search possibilities==
* [[ServiceCenter]]: Create a preconfigured search portal with a list of the top five results

* [[WikiExplorer]]: Filter metadata from the wiki to find articles using particular criteria.

==Troubleshooting==
[http://sourceforge.net/p/bluespice/bugs/227/ Problems with the Extended Search]

[http://sourceforge.net/p/bluespice/bugs/235/ Extended Search stellt ohne Vorankündigung den Betrieb ein]

[[en:{{FULLPAGENAME}}]][[de:ExtendedSearch]]
[[Category:Extension]]
[[Category:BlueSpice free]]
[[Category:BlueSpice pro]]

Main Page

2017-04-07T09:55:23Z

Mglaser:

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

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

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

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

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

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

Admin manual (coming soon)

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

The right BlueSpice for everyone

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

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

News

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

<bs:smartlist/>

|}

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

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

Main Page

2017-04-07T09:52:01Z

Mglaser: