BlueSpice Helpdesk - User contributions [en]

How to debug

2024-04-26T10:40:50Z

Hslater: Remove obsolete debugging settings

==Help others to help you==
Sometimes things go wrong. In many cases the user is then confronted with cryptic or no error messages at all. This page provides help about getting more information about what exactly went wrong, so it can be fixed quickly. This is especially important when asking for help on locations like [https://community.bluespice.com community.bluespice.com].

Additional information can also be found at [[mediawikiwiki:Manual:How_to_debug|"Manual:How to debug" on MediaWiki.org]].

{{Textbox|boxtype=warning|header=Check for sensitive information|text=Most of the techniques described here will output very detailed information about the error, but also about the system and the context. The output may contain sensitive information like usernames, passwords, pathes, access-keys and many more. Before posting any information retrieved by this kind of debugging on a public location (like [https://community.bluespice.com community.bluespice.com]), make sure to redact all potential sensitive information!|icon=yes}}

== Generic information ==
In general it is a good idea to provide additional context information about the error. Usually this information is easily to access/gather by the one who reports an error and very valueable to anyone trying to help.

Such information can be
* Browser used (Firefox, Chrome, Edge, ...), ideally with the version
* URLs (which page the error occurs on, additional parameters that may play into the error)
* User permission level or role (admin, reader, editor, reviewer, ...)

Again: Be careful if the shared information contains sensible data and redact it if required.

== Server side debugging ==
There are various ways to get more information about errors by changing some configuration on the server side.

=== Wiki application ===

==== Enable detailed error reporting ====
Within you <code>LocalSettings.php</code> file, please add the following lines:<syntaxhighlight lang="php">
$GLOBALS['wgDebugDumpSql'] = true;
$GLOBALS['wgShowExceptionDetails'] = true;

</syntaxhighlight>This will turn error messages like <code>internal_api_error_DBQueryError</code> into a more detailed stack of program calls, including database queries and responses.

==== General debug log ====
Sometimes it can be useful to see all debugging information the application produces. To enable this general debug log please add the following lines within you <code>LocalSettings.php</code> file:<syntaxhighlight lang="php">
if ( isset( $_GET['dodebuglog'] ) ) {
$GLOBALS['wgDebugLogFile'] = "$IP/cache/debug.log";
}

</syntaxhighlight>Be aware that this configuration is set conditionally. It will only be used if the URL accessed in the browser contains some query string like <code>dodebuglog=1</code>. This is to allow a more isolated debug log file. Otherwise other requests (like calls to the <code>load.php</code> entrypoint for CSS and JS content) may also add into this file, which makes analysis more difficult.

===== Important log channels =====
{{Textbox|boxtype=important|header=Channel names must be ''exactly'' like listed here! Watch out for casing and spaces!|text=|icon=yes}}
{| class="wikitable"
!Source (Extension)
!Channel name(s)
!Use case
|-
|MW CORE
|<code>http</code>, <code>HttpError</code>
<code>JobExecutor</code>

<code>LocalFile</code>

<code>exception</code>

<code>DeferredUpdates</code>

<code>Parsoid</code>

<code>resourceloader</code>

<code>runJobs</code>

<code>session</code>, <code>login</code>

...
|
|-
|MWSTAKE COMPONENTS
|<code>ContentProvisioner</code>
<code>runjobs-trigger-runner</code>
|
|-
|Math
|<code>Math</code>
|Math
|-
|PluggableAuth
|<code>PluggableAuth</code>
|LDAP, SAML, OpenIDConnect
|-
|LDAPProvider
|<code>LDAP</code>
<code>MediaWiki\\Extension\\LDAPProvider\\Client</code>
|LDAP
|-
|LDAPAuthentication2
|<code>LDAPAuthentication2</code>
|LDAP
|-
|LDAPGroups
|<code>LDAPGroups</code>
|LDAP
|-
|LDAPUserInfo
|<code>LDAPUserInfo</code>
|LDAP
|-
|LDAPSyncAll
|<code>LDAPSyncAll</code>
|LDAP
|-
|LDAPAuthorization
|<code>LDAPAuthorization</code>
|LDAP
|-
|Auth_remoteuser
|<code>session</code>
|LDAP (SSO/Kerberos)
|-
|SimpleSAMLphp
|<code>SimpleSAMLphp</code>
|SAML
|-
|OpenIDConnect
|<code>OpenID Connect</code>
|OpenIDConnect
|-
|ImportOfficeFiles
|<code>ImportOfficeFiles</code>
<code>ImportOfficeFiles_RemoveOrphanedDirectories</code>

<code>ImportOfficeFiles_UI</code>
|
|-
|Workflows
|<code>workflows</code>
|
|-
|BlueSpiceArticlePreviewCapture
|<code>ArticlePreviewCapture</code>
|
|-
|OAuth
|<code>OAuth</code>
|
|-
|BlueSpiceUEModulePDF, BlueSpiceUEModuleBookPDF
|<code>BS::UEModulePDF</code>
|PDF
|-
|BlueSpiceExtendedSearch
|<code>BSExtendedSearch</code>
|Search
|-
|BlueSpiceWikiFarm
|<code>SimpleFarmerAPI</code>
|Farm operations
|}

=== Clientside output of serverside logs ===
Can be enabled using [[mediawikiwiki:Manual:$wgDebugToolbar|$wgDebugToolbar]]

Example:<syntaxhighlight lang="php">
$GLOBALS['wgDebugToolbar'] = isset( $_GET['dodebuglog'] )

</syntaxhighlight>

== Client side debugging ==
Many errors occur only on the client and server side debugging will not help. In such cases the webbrowser can be used to retrieve more information.

=== Browser development tools ===
Most modern browsers have sophisticated development tools. Usually they can be accessed by pressing the <code>F12</code> key on the keyboard.

==== JavaScript console ====
When some interface element (button, dialog, ...) does not behave like it should, it is usually worth checking the browsers JavaScript console.

{{Textbox|boxtype=tip|header=Nothing listed?|text=Sometimes it may be required to re-do the action that lead to the error with ''open console'' rather than opening it later.}}

'''Example:'''

[[File:How_to_debug_JS_console_01.png|center|frame]]

One can click the link on the right side of the line to see the location of where the error has emerged from.

'''Example:'''

[[File:How_to_debug_JS_console_02.png|center|frame]]

====Network panel====
Sometimes network communication in the background of the application fails. In such cases, the "Network" panel of the browsers developer tools may reveal more information.

The error is also shown in the "Console" tab.

'''Example:'''

[[File:How_to_debug_Network_panel_01.png|center|frame]]

When in the "Network" panel, one can select the faulty request from the list to get more information.

'''Example:'''

[[File:How_to_debug_Network_panel_02.png|center|frame]]

The various tabs "Header", "Payload", "Response", etc. can provide useful information. When reporting such an issue, you can just "copy" the information using the context menu.

'''Example:'''

[[File:How_to_debug_Network_panel_03.png|center|frame]]

Reference:BlueSpicePlayer

2023-12-11T06:39:51Z

Hslater: Add ogg format

{{BSExtensionInfo
|status=stable
|developer=HalloWelt
|type=BlueSpice
|edition=BlueSpice pro, BlueSpice Farm, BlueSpice Cloud
|compatible=BlueSpice
|category=Rich Articles
|license=GPL v2+
|features=BlueSpice '''Player''' is a video player that enables you to play all the usual HTML5 video formats in your wiki.

*Activated with the <code><nowiki><showtime>Video.mp4</showtime></nowiki></code> tag
*Settings:
**change the size
**start the video immediately (autoplay)
**play the video in a loop
*Supported formats: mp4, ogv, ogg, flv and webm
*It is possible to include multiple videos on one page
*In IE and flv, the HTML5 player falls back to a Flash version (default in VideoJS)
*For compatibility reasons, ''bs: jwplayer'' is also supported as a tag

In the user settings (<code>Special:Preferences</code>) under ''Appearance,'' users can set if the videos should start automatically.
|desc=Integrates an HTML video player for uploaded videos
}}
{{wcagCheck
|wcagStatus=2-testing complete
|wcagCheckedfor=Web, Authoring tool
|wcagTestdate=2022-08-09
|wcagLevel=AA
|wcagSupport=partially supports
|wcagWorkaround=yes
|wcagComments=Authoring tool: insert tag in source editing mode

Web: Player controls are keyboard and screenreader accessible

No subtitles can be added. Workaround: Use extension '''EmbedVideo''' and link to external captioned or subtitled videos.
|extensionType=extended
|extensionFocus=reader
}}

Reference:BlueSpicePlayer

2023-12-11T05:30:32Z

Hslater: Spelling Perferences

{{BSExtensionInfo
|status=stable
|developer=HalloWelt
|type=BlueSpice
|edition=BlueSpice pro, BlueSpice Farm, BlueSpice Cloud
|compatible=BlueSpice
|category=Rich Articles
|license=GPL v2+
|features=BlueSpice '''Player''' is a video player that enables you to play all the usual HTML5 video formats in your wiki.

*Activated with the <code><nowiki><showtime>Video.mp4</showtime></nowiki></code> tag
*Settings:
**change the size
**start the video immediately (autoplay)
**play the video in a loop
*Supported formats: mp4, ogv, flv and webm
*It is possible to include multiple videos on one page
*In IE and flv, the HTML5 player falls back to a Flash version (default in VideoJS)
*For compatibility reasons, ''bs: jwplayer'' is also supported as a tag

In the user settings (<code>Special:Preferences</code>) under ''Appearance,'' users can set if the videos should start automatically.
|desc=Integrates an HTML video player for uploaded videos
}}
{{wcagCheck
|wcagStatus=2-testing complete
|wcagCheckedfor=Web, Authoring tool
|wcagTestdate=2022-08-09
|wcagLevel=AA
|wcagSupport=partially supports
|wcagWorkaround=yes
|wcagComments=Authoring tool: insert tag in source editing mode

Web: Player controls are keyboard and screenreader accessible

No subtitles can be added. Workaround: Use extension '''EmbedVideo''' and link to external captioned or subtitled videos.
|extensionType=extended
|extensionFocus=reader
}}

Reference:BlueSpicePlayer

2023-12-11T05:23:16Z

Hslater: Fix tag

{{BSExtensionInfo
|status=stable
|developer=HalloWelt
|type=BlueSpice
|edition=BlueSpice pro, BlueSpice Farm, BlueSpice Cloud
|compatible=BlueSpice
|category=Rich Articles
|license=GPL v2+
|features=BlueSpice '''Player''' is a video player that enables you to play all the usual HTML5 video formats in your wiki.

*Activated with the <code><nowiki><showtime>Video.mp4</showtime></nowiki></code> tag
*Settings:
**change the size
**start the video immediately (autoplay)
**play the video in a loop
*Supported formats: mp4, ogv, flv and webm
*It is possible to include multiple videos on one page
*In IE and flv, the HTML5 player falls back to a Flash version (default in VideoJS)
*For compatibility reasons, ''bs: jwplayer'' is also supported as a tag

In the user settings (<code>Special:Perferences</code>) under ''Appearance,'' users can set if the videos should start automatically.
|desc=Integrates an HTML video player for uploaded videos
}}
{{wcagCheck
|wcagStatus=2-testing complete
|wcagCheckedfor=Web, Authoring tool
|wcagTestdate=2022-08-09
|wcagLevel=AA
|wcagSupport=partially supports
|wcagWorkaround=yes
|wcagComments=Authoring tool: insert tag in source editing mode

Web: Player controls are keyboard and screenreader accessible

No subtitles can be added. Workaround: Use extension '''EmbedVideo''' and link to external captioned or subtitled videos.
|extensionType=extended
|extensionFocus=reader
}}

Reference:BlueSpicePlayer

2023-12-11T05:00:54Z

Hslater: Fix tag

{{BSExtensionInfo
|status=stable
|developer=HalloWelt
|type=BlueSpice
|edition=BlueSpice pro, BlueSpice Farm, BlueSpice Cloud
|compatible=BlueSpice
|category=Rich Articles
|license=GPL v2+
|features=BlueSpice '''Player''' is a video player that enables you to play all the usual HTML5 video formats in your wiki.

*Activated with the <code><nowiki><showtime> Video.mp4 </showtime></nowiki></code> tag
*Settings:
**change the size
**start the video immediately (autoplay)
**play the video in a loop
*Supported formats: mp4, ogv, flv and webm
*It is possible to include multiple videos on one page
*In IE and flv, the HTML5 player falls back to a Flash version (default in VideoJS)
*For compatibility reasons, ''bs: jwplayer'' is also supported as a tag

In the user settings (<code>Special:Perferences</code>) under ''Appearance,'' users can set if the videos should start automatically.
|desc=Integrates an HTML video player for uploaded videos
}}
{{wcagCheck
|wcagStatus=2-testing complete
|wcagCheckedfor=Web, Authoring tool
|wcagTestdate=2022-08-09
|wcagLevel=AA
|wcagSupport=partially supports
|wcagWorkaround=yes
|wcagComments=Authoring tool: insert tag in source editing mode

Web: Player controls are keyboard and screenreader accessible

No subtitles can be added. Workaround: Use extension '''EmbedVideo''' and link to external captioned or subtitled videos.
|extensionType=extended
|extensionFocus=reader
}}

Manual:Extension/BlueSpiceBookshelf/4-4

2022-07-07T07:59:42Z

Hslater: Changed 'Art' to 'Type'. Changed 'Beschreibung' to 'Description'. Changed 'Kapitelnavigation' to 'Chapter navigation'. Changed 'ja' and 'nein' to 'Yes' and 'No'. (English manual).

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

In BlueSpice pro, several wiki pages can be displayed for a structured book with chapter navigation. The book can also be printed as a PDF file with a cover sheet.

==Characteristics of books==
By default, books are created as a "general book". General books have the following characteristics:

*They povide a chapter navigation.
*On book pages, the book navigation is displayed instead of the main navigation.
*A wiki page that belongs to a general book is identified by a <code><nowiki><bookshelf /></nowiki></code> tag in the source code.
*Each page can only be included '''in one''' general book.
*Books can be printed completely or partially as a PDF with a cover sheet.
*They are listed alphabetically on the bookshelf. It is not possible to hide individual books.
*The bookshelf can be reached via the main navigation.

==Creating a book==
Books are created from the page ''Special:BookshelfBookManager''. This page can be reached from the ''[[Manual:Extension/BlueSpiceDiscovery|Global actions]]'' menu under ''Management > Books''.
[[File:Manual:book-manager.png|alt=Book manager|center|thumb|650x650px|Book manager]]

'''To create a book:'''
#'''Click''' the <code>+</code>-button.
#'''Enter''' a ''Book title.''
#'''Select''' "General books" as type of the book.[[File:Manual:create-book.png|alt=Create a book|center|thumb|550x550px|Create a book]]
#'''Click''' ''Done''. The book editor loads next.
{{Messagebox|boxtype=important|icon=|Note text=The book is only created in the wiki when at least one page has been saved in the book.|bgcolor=}}

===Adding pages===
You are now in the book editing mode.
[[File:Manual:bookshelf-schaltflächen.png|alt=Book edit buttons|center|thumb|220x220px|Book edit buttons]]

#'''Click''' the ''Plus'' button (1). A dialog window opens.
#'''Search''' for a page in the wiki and select it. Soll in der Buchnavigation ein anderer Name angezeigt werden so können Sie ienen Anzeigetitle angeben (optional).
#'''Click''' ''Done''.
#'''Add''' additional pages.

#'''Click''' the arrow of the ''Save'' button and select ''Save and add chapter navigation.'' This process inserts the <code><nowiki><bookshelf /></nowiki></code> tag into the source code of all wiki pages in the book. This causes a revision of the pages.[[File:Manual:save chapternavigation.png|alt=Add chapter navigation|center|thumb|350x350px|Add chapter navigation]]
{{Messagebox|boxtype=tip|icon=|Note text=You can click a page title of a book page before adding a new book page. This is then inserted as a sub-chapter. You can move pages to the desired position later using drag & drop with the mouse.|bgcolor=}}
The book is now displayed on the wiki bookshelf. The bookshelf can be reached via the entry links in the main navigation.

{{Messagebox|boxtype=note|icon=|Note text=There is no option to go directly from the bookshelf to the book manager.|bgcolor=}}

===Mass-adding of pages===
After clicking "Mass add", a dialog is opened. It contains different criteria for page selection:

* All pages of a category
* All subpages of a certain page
* From a page collection - page collections are lists of pages located in the MediaWiki namespace. They are usually created from [https://en.wiki.bluespice.com/wiki/Manual:Extension/BlueSpiceExtendedSearch#Export search results].
* By a semantic property - pages can be selected based on the value of a certain semantic property.

After adding your book pages click S''ave'' at the bottom of the page. Now you have created a page in the namespace ''Book''. It simply contains the list of pages that have been added to the book.

==Adding metadata==
While editing a book (adding or removing pages), meta-data for the book can be added. References to these metadata can be included in the PDF template. To edit metadata, select the top-most node of the book (first page) and click the wrench icon. A dialog will be opened where various meta-data can be added or removed:

* Title
* Subtitle
* Author 1 and 2
* Document-ID
* Document type
* Department
* Version
* Template (PDF): If you maintain multiple PDF templates for books, you can select one of them here.
* Table of Contents (Only article titles, or Embed article TOCs)

==Adding a cover image==
To add a cover photo for the book, add a metadata item ''Bookshelf image''. Select this option from the dropdown and click ''Add''. Once the meta data is added enter the name of the image in the value field. Any image currently uploaded to the wiki can be used. Type the name without the "File:" prefix (enter the image name and file extension).

==Types of books==
{| class="wikitable"
!Type
!Description
!Chapter navigation
|-
|'''General books'''
|Visible to all users. Only general books can have a chapter navigation. In almost all cases a book is set up as a "general book".
|Yes
|-
|'''Own books'''
|An own book is only visible in the bookshelf to the user who created the book. Such a book does not have a chapter navigation. Own books are usually created to export wiki pages as a PDF with a cover sheet.
|No
|-
|'''Temporary books'''
|This selection is also available to wiki users who are not logged into the wiki and is therefore mainly useful for public wikis. These books are only temporarily stored in the user's browser and not in the wiki itself. If the browser cache is deleted or the user switches to another browser, the book is no longer available. The main aim of temporary books is so that users can collectively print out wiki pages as PDFs.
|No
|}

==Exporting a book==
Books, individual chapters or even individual book pages can be exported as PDF files:

# '''Open''' the book in the book manager.
# '''Select''' each of the pages or chapters to export by clicking the appropriate check boxes. Sub-chapters are selected automatically.
# '''Click''' the Export Selections drop-down menu to open a list of the available formats. 

==Actions in the book manager==
Der Link Verwaltung > Bücher im Menü ''Globale Aktionen'' lädt die Seite ''Spezial:Bücherverwaltung''. Hier können Sie Ihre Bücher bearbeiten.
[[File:Manual:book-manager-actions-EN.png|alt=Book manager actions|center|thumb|650x650px|Book manager actions]]
* '''Edit''' (1): Links to the Book editor where you can edit the book contents and metadata.
* '''Delete''' (2): Deletes the book page in the namespace ''Book'' '''without''' deleting the wiki pages.
* '''Duplicate''' (3): Duplicates this book, including '''all the pages''' of the book to a different namespace.
* '''Export''' (4): Exports all wiki pages in this book to PDF.
* '''Assign''' (5): Assigns the book to designated users. These users are the responsible editors of the book.

==Configuration==
===Display options===
{{#dpl:title=Manual:Extension/BlueSpiceConfigManager|include=#BlueSpiceBookShelf}}

===Export===
Wiki-Administratoren können folgende Anpassungen für den Buchexport vornehmen:
{{#dpl:title=Manual:Extension/BlueSpiceConfigManager|include=#Export}}

===Configuring the file size limits (server)===
By default, the book export is limited to 50MB in file size. To adjust this value, complete the following steps:

#In Apache Tomcat, open the file ''web.xml'': <syntaxhighlight lang="c">
sudo -s
nano /opt/tomcat/webapps/manager/WEB-INF/web.xml
</syntaxhighlight>
#Look for the following lines and adjust the value (e.g. for 250MB=26214400) <syntaxhighlight lang="c">
<max-file-size>262144000</max-file-size>
<max-request-size>262144000</max-request-size>
</syntaxhighlight>
#The web app BShtml2PDF also has a setting that needs to be adjusted: <syntaxhighlight lang="c">
nano /opt/tomcat/webapps/BShtml2PDF/WEB-INF
</syntaxhighlight>
#Enter your values in the following lines: <syntaxhighlight lang="c">
<param-name>maxMemSize</param-name> <param-value>26214400</param-value>
<param-name>maxFileize</param-name> <param-value>26214400</param-value>
</syntaxhighlight>
#Apache Tomcat neu starten <syntaxhighlight lang="c">
service tomcat restart
</syntaxhighlight>
==Deleting a book==

Wenn Sie ein Buch löschen, entfernen Sie nur die Buchseite des Buches (also das Inhaltsverzeichnis). Die Wiki-Seiten im Buch werden jedoch nicht gelöscht. Bevor Sie das Buch löschen, werden Sie in einem Popup-Menü darüber informiert, dass das ''bookshelf''-Tag nicht automatisch von den Seiten entfernt wird.

Die ''bookshelf''-Tags haben nach dem Löschen des Buches keine Auswirkung auf die Wiki-Seiten. Wenn Sie sie manuell entfernen möchten, können Sie zur Seite ''Spezial:Text ersetzen'' gehen und ein "Suchen und Ersetzen" durchführen.

==Duplicating a book ==
You can create an entire copy of the book by duplicating it:

'''To duplicate a book:'''

#'''Enter''' a ''target name'': The default vlaue is the book name with the suffix ''(copy)''. Change this to create a different book title.
#'''Select''' a ''namespace'': Choose a namespace that is different from the original namespace.

If you are not careful, you might experience some unintended consequences. By creating a new book, you also create copies of all the wiki pages in the original book. Since a namespace cannot contain the same page twice, you have to copy the files to a different namespace.

'''About the duplicated files:'''

*'''Book page:''' A new page in the namespace book. If you don't enter a new title, the book will be created with the same title and the suffix ''(Copy). E.g. Employee Manual (Copy).'' This file includes a copy of the structure of your original book with the corresponding links to the duplicated pages in the new copy.
*'''Wiki pages''': All pages contained in the original book are duplicated. The following scenarios are possible:
**'''Same namespace:''' If you duplicate a book in the same namespace, no actual duplicates of the actual wiki are created. Instead, the bookshelf tag is updated to point to the copy of the book. For example, if your original book contains the page ''HR:Quality assurance'' (the book is in the namespace HR), the ''Quality assurance'' page now contains the bookshelf tag <code><nowiki></nowiki></code>.
**'''Different namespace''': If you create the book copy in a different namespace, the bookshelf tag in the original files remains unchanged. The new pages in the different namespace are created with a bookshelf tag for the new book copy. This is most likely the scenario you want.
==Permissions==
To create and edit books, users need ''edit'' rights in Book namespace. Additionally, a user can only add pages to the book that that user can read. If a user tries to export a book to PDF that contains pages for which the user does not have permissions, the user will get an error message.
==Tips for working with books ==

*Use a competent team to decide on the content that should be transferred into an online book.
*Decide on how to handle existing numerations or references.
*Seize the opportunity: Get rid of unnecessary content (or don't include it in your book).
*Decide on standards for documents: When does it make sense to link documents in the wiki? When is is sensible to include the document's content into a wiki article?
*Decide on a fitting course of action: Do you want to create the articles in the wiki first, and compile them in a book structure afterwards, or do you want to create the book structure first, and create and edit the articles contained gradually?
{{Box Links-en
|Topic1=[[Reference:BlueSpiceBookshelf]]
|Topic2=
|Topic3=[[Manual:Extension/BlueSpiceBookshelf/Customized_PDF_Output|Customizing page breaks]]}}
{{Translation}}

[[Category:Organization]]

Manual:Extension/BlueSpiceBookshelf/4-4

2022-07-07T07:34:46Z

Hslater: Removed 'Sie als Art des Buches' from 'Select Sie als Art des Buches "General books" as type of the book.' (English manual).

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

In BlueSpice pro, several wiki pages can be displayed for a structured book with chapter navigation. The book can also be printed as a PDF file with a cover sheet.

==Characteristics of books==
By default, books are created as a "general book". General books have the following characteristics:

*They povide a chapter navigation.
*On book pages, the book navigation is displayed instead of the main navigation.
*A wiki page that belongs to a general book is identified by a <code><nowiki><bookshelf /></nowiki></code> tag in the source code.
*Each page can only be included '''in one''' general book.
*Books can be printed completely or partially as a PDF with a cover sheet.
*They are listed alphabetically on the bookshelf. It is not possible to hide individual books.
*The bookshelf can be reached via the main navigation.

==Creating a book==
Books are created from the page ''Special:BookshelfBookManager''. This page can be reached from the ''[[Manual:Extension/BlueSpiceDiscovery|Global actions]]'' menu under ''Management > Books''.
[[File:Manual:book-manager.png|alt=Book manager|center|thumb|650x650px|Book manager]]

'''To create a book:'''
#'''Click''' the <code>+</code>-button.
#'''Enter''' a ''Book title.''
#'''Select''' "General books" as type of the book.[[File:Manual:create-book.png|alt=Create a book|center|thumb|550x550px|Create a book]]
#'''Click''' ''Done''. The book editor loads next.
{{Messagebox|boxtype=important|icon=|Note text=The book is only created in the wiki when at least one page has been saved in the book.|bgcolor=}}

===Adding pages===
You are now in the book editing mode.
[[File:Manual:bookshelf-schaltflächen.png|alt=Book edit buttons|center|thumb|220x220px|Book edit buttons]]

#'''Click''' the ''Plus'' button (1). A dialog window opens.
#'''Search''' for a page in the wiki and select it. Soll in der Buchnavigation ein anderer Name angezeigt werden so können Sie ienen Anzeigetitle angeben (optional).
#'''Click''' ''Done''.
#'''Add''' additional pages.

#'''Click''' the arrow of the ''Save'' button and select ''Save and add chapter navigation.'' This process inserts the <code><nowiki><bookshelf /></nowiki></code> tag into the source code of all wiki pages in the book. This causes a revision of the pages.[[File:Manual:save chapternavigation.png|alt=Add chapter navigation|center|thumb|350x350px|Add chapter navigation]]
{{Messagebox|boxtype=tip|icon=|Note text=You can click a page title of a book page before adding a new book page. This is then inserted as a sub-chapter. You can move pages to the desired position later using drag & drop with the mouse.|bgcolor=}}
The book is now displayed on the wiki bookshelf. The bookshelf can be reached via the entry links in the main navigation.

{{Messagebox|boxtype=note|icon=|Note text=There is no option to go directly from the bookshelf to the book manager.|bgcolor=}}

===Mass-adding of pages===
After clicking "Mass add", a dialog is opened. It contains different criteria for page selection:

* All pages of a category
* All subpages of a certain page
* From a page collection - page collections are lists of pages located in the MediaWiki namespace. They are usually created from [https://en.wiki.bluespice.com/wiki/Manual:Extension/BlueSpiceExtendedSearch#Export search results].
* By a semantic property - pages can be selected based on the value of a certain semantic property.

After adding your book pages click S''ave'' at the bottom of the page. Now you have created a page in the namespace ''Book''. It simply contains the list of pages that have been added to the book.

==Adding metadata==
While editing a book (adding or removing pages), meta-data for the book can be added. References to these metadata can be included in the PDF template. To edit metadata, select the top-most node of the book (first page) and click the wrench icon. A dialog will be opened where various meta-data can be added or removed:

* Title
* Subtitle
* Author 1 and 2
* Document-ID
* Document type
* Department
* Version
* Template (PDF): If you maintain multiple PDF templates for books, you can select one of them here.
* Table of Contents (Only article titles, or Embed article TOCs)

==Adding a cover image==
To add a cover photo for the book, add a metadata item ''Bookshelf image''. Select this option from the dropdown and click ''Add''. Once the meta data is added enter the name of the image in the value field. Any image currently uploaded to the wiki can be used. Type the name without the "File:" prefix (enter the image name and file extension).

==Types of books==
{| class="wikitable"
!Art
!Beschreibung
!Kapitelnavigation
|-
|'''General books'''
|Visible to all users. Only general books can have a chapter navigation. In almost all cases a book is set up as a "general book".
|ja
|-
|'''Own books'''
|An own book is only visible in the bookshelf to the user who created the book. Such a book does not have a chapter navigation. Own books are usually created to export wiki pages as a PDF with a cover sheet.
|nein
|-
|'''Temporary books'''
|This selection is also available to wiki users who are not logged into the wiki and is therefore mainly useful for public wikis. These books are only temporarily stored in the user's browser and not in the wiki itself. If the browser cache is deleted or the user switches to another browser, the book is no longer available. The main aim of temporary books is so that users can collectively print out wiki pages as PDFs.
|nein
|}

==Exporting a book==
Books, individual chapters or even individual book pages can be exported as PDF files:

# '''Open''' the book in the book manager.
# '''Select''' each of the pages or chapters to export by clicking the appropriate check boxes. Sub-chapters are selected automatically.
# '''Click''' the Export Selections drop-down menu to open a list of the available formats. 

==Actions in the book manager==
Der Link Verwaltung > Bücher im Menü ''Globale Aktionen'' lädt die Seite ''Spezial:Bücherverwaltung''. Hier können Sie Ihre Bücher bearbeiten.
[[File:Manual:book-manager-actions-EN.png|alt=Book manager actions|center|thumb|650x650px|Book manager actions]]
* '''Edit''' (1): Links to the Book editor where you can edit the book contents and metadata.
* '''Delete''' (2): Deletes the book page in the namespace ''Book'' '''without''' deleting the wiki pages.
* '''Duplicate''' (3): Duplicates this book, including '''all the pages''' of the book to a different namespace.
* '''Export''' (4): Exports all wiki pages in this book to PDF.
* '''Assign''' (5): Assigns the book to designated users. These users are the responsible editors of the book.

==Configuration==
===Display options===
{{#dpl:title=Manual:Extension/BlueSpiceConfigManager|include=#BlueSpiceBookShelf}}

===Export===
Wiki-Administratoren können folgende Anpassungen für den Buchexport vornehmen:
{{#dpl:title=Manual:Extension/BlueSpiceConfigManager|include=#Export}}

===Configuring the file size limits (server)===
By default, the book export is limited to 50MB in file size. To adjust this value, complete the following steps:

#In Apache Tomcat, open the file ''web.xml'': <syntaxhighlight lang="c">
sudo -s
nano /opt/tomcat/webapps/manager/WEB-INF/web.xml
</syntaxhighlight>
#Look for the following lines and adjust the value (e.g. for 250MB=26214400) <syntaxhighlight lang="c">
<max-file-size>262144000</max-file-size>
<max-request-size>262144000</max-request-size>
</syntaxhighlight>
#The web app BShtml2PDF also has a setting that needs to be adjusted: <syntaxhighlight lang="c">
nano /opt/tomcat/webapps/BShtml2PDF/WEB-INF
</syntaxhighlight>
#Enter your values in the following lines: <syntaxhighlight lang="c">
<param-name>maxMemSize</param-name> <param-value>26214400</param-value>
<param-name>maxFileize</param-name> <param-value>26214400</param-value>
</syntaxhighlight>
#Apache Tomcat neu starten <syntaxhighlight lang="c">
service tomcat restart
</syntaxhighlight>
==Deleting a book==

Wenn Sie ein Buch löschen, entfernen Sie nur die Buchseite des Buches (also das Inhaltsverzeichnis). Die Wiki-Seiten im Buch werden jedoch nicht gelöscht. Bevor Sie das Buch löschen, werden Sie in einem Popup-Menü darüber informiert, dass das ''bookshelf''-Tag nicht automatisch von den Seiten entfernt wird.

Die ''bookshelf''-Tags haben nach dem Löschen des Buches keine Auswirkung auf die Wiki-Seiten. Wenn Sie sie manuell entfernen möchten, können Sie zur Seite ''Spezial:Text ersetzen'' gehen und ein "Suchen und Ersetzen" durchführen.

==Duplicating a book ==
You can create an entire copy of the book by duplicating it:

'''To duplicate a book:'''

#'''Enter''' a ''target name'': The default vlaue is the book name with the suffix ''(copy)''. Change this to create a different book title.
#'''Select''' a ''namespace'': Choose a namespace that is different from the original namespace.

If you are not careful, you might experience some unintended consequences. By creating a new book, you also create copies of all the wiki pages in the original book. Since a namespace cannot contain the same page twice, you have to copy the files to a different namespace.

'''About the duplicated files:'''

*'''Book page:''' A new page in the namespace book. If you don't enter a new title, the book will be created with the same title and the suffix ''(Copy). E.g. Employee Manual (Copy).'' This file includes a copy of the structure of your original book with the corresponding links to the duplicated pages in the new copy.
*'''Wiki pages''': All pages contained in the original book are duplicated. The following scenarios are possible:
**'''Same namespace:''' If you duplicate a book in the same namespace, no actual duplicates of the actual wiki are created. Instead, the bookshelf tag is updated to point to the copy of the book. For example, if your original book contains the page ''HR:Quality assurance'' (the book is in the namespace HR), the ''Quality assurance'' page now contains the bookshelf tag <code><nowiki></nowiki></code>.
**'''Different namespace''': If you create the book copy in a different namespace, the bookshelf tag in the original files remains unchanged. The new pages in the different namespace are created with a bookshelf tag for the new book copy. This is most likely the scenario you want.
==Permissions==
To create and edit books, users need ''edit'' rights in Book namespace. Additionally, a user can only add pages to the book that that user can read. If a user tries to export a book to PDF that contains pages for which the user does not have permissions, the user will get an error message.
==Tips for working with books ==

*Use a competent team to decide on the content that should be transferred into an online book.
*Decide on how to handle existing numerations or references.
*Seize the opportunity: Get rid of unnecessary content (or don't include it in your book).
*Decide on standards for documents: When does it make sense to link documents in the wiki? When is is sensible to include the document's content into a wiki article?
*Decide on a fitting course of action: Do you want to create the articles in the wiki first, and compile them in a book structure afterwards, or do you want to create the book structure first, and create and edit the articles contained gradually?
{{Box Links-en
|Topic1=[[Reference:BlueSpiceBookshelf]]
|Topic2=
|Topic3=[[Manual:Extension/BlueSpiceBookshelf/Customized_PDF_Output|Customizing page breaks]]}}
{{Translation}}

[[Category:Organization]]

File:Seite verschieben.drawio.png

2022-06-30T13:04:41Z

Hslater: (username removed) (log details removed)

File:Seite verschieben.drawio.png

2022-06-30T13:03:21Z

Hslater: (username removed) (log details removed)

Manual:Extension/BlueSpiceReadConfirmation

2022-06-30T12:56:17Z

Hslater: Spelling error : confirmaation > confirmation

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

The extension '''ReadConfirmation''' allows to request read confirmations from users. If a user is assigned to a page, a mandatory read confirmation can be added to the page.
==Enabling read confirmations==
An administrator must enable read confirmations in the [[Manual:Extension/BlueSpiceNamespaceManager|namespace manager]]:
 
[[File:Manual:ReadConfirmation2.png|alt=Namespace manager|center|thumb|650x650px|Namespace manager]]

==Confirmation requests==
[[File:Manual:ReadConfirmation1.png|alt=Read confirmation|center|thumb|650x650px|Read confirmation]]
When read confirmations are active in a namespace, assigned users see a confirmation prompt when the page content has changed. After checking the checkbox ''Yes, I have completely read this article'' and then ''Confirm,'' the page version will be marked as read by that user.

== Administration of read confirmations ==
Wiki admins can see an overview of all read confirmations by navigating to ''Global actions > Management > Assignments.'' Read confirmation information is shown in the column ''Read?''. A page can have multiple states:

*''Read confirmation not enabled:'' BlueSpiceReadConfirmation is not enabled for the namespace to which the page belongs.
*''Not read:'' BlueSpiceReadConfirmation is enabled, but the assigned users have not yet read the page.
*''Actions:'' In the columns for actions, there are two items related to read confirmations.
**''Read confirmation log:'' Link to the read confirmation log for the page.
**''Request read confirmation:'' Users get a reminder for their read confirmation.
[[File:Manual:zuweisungen-verwaltung-en.png|alt=Assignments manager with read confirmation info|center|thumb|750x750px|Assignments manager with read confirmation info]]
 

==Read confirmations and page approvals==
If the approval feature is activated in a namespace at the same time, the read confirmation is triggered when a new draft is created. This [[Reference:BlueSpiceReadConfirmation|can be changed via server configuration]] so that the read confirmation is required after the draft page has been approved.{{Box Links-en|Topic1=[[Reference:BlueSpiceReadConfirmation]]|Topic2=[[Manual:Extension/BlueSpicePageAssignments|Page assignments]]}}
 

{{translation}}
[[Category:Quality]]

Manual:Extension/BlueSpicePageAssignments

2022-06-30T12:55:36Z

Hslater: Spelling error : assignedto > assigned to

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

With the extension '''PageAssignments,''' users can be assigned to a page. Assigned users can serve as contacts for a page. In addition, assignments can be used to collect [[Manual:Extension/BlueSpiceReadConfirmation|read confirmations]]. If the optional "Secured page assignments" function is activated in a namespace , only assigned users can edit a page.

==What are page assignments?==
{{#dpl:title=Manual:Quality_management|include=pageassign}}

==Assigning a page==

To assign pages to other users, you need the appropriate rights. These are provided via the roles ''reviewer, admin'' and ''maintenanceadmin''. Assigned users need to have the role ''editor'' to be able to edit the page they are assigned to. Although users with ''read'' permissions can be assigned to a page, they cannot make changes to the page.

'''To assign a user or a group to a page:'''

#'''Click''' on ''Set page assignments'' in the page tools.
#'''Type''' a user or group name in the assignments text box ''Add assignments...''
#'''Click''' the ''Done'' button.
#'''Add''' more users or groups (optional).[[File:Manual:zuweisung-benutzer-en.png|alt=Assignments dialog window|center|thumb|Assignments dialog window]] 
==Assignments management==
Users in the ''reviewer'' role can see a list of all pages that have assignments. This page (''Special:ManagePageAssignments'') can be loaded from the navigation menu under ''[[Manual:Extension/BlueSpiceDiscovery|Global actions]] >Management > Assignments.'' 
[[File:Manual:zuweisungen-verwaltung-en.png|alt=Assignments manager|center|thumb|650x650px|Assignments manager]]

=== Possible actions ===
The following actions are available on this page:

(1) Change assignments

(2) Delete assignments

(3) View assignements log or read confirmations log (if activated)

(4)Request read confirmation (if activated)

== Secured page assignments ==
In the [[Manual:Extension/BlueSpiceNamespaceManager|namespace manager]] you can configure that page assignments are secured. If a page is created in such a namespace, the page is only editable for users that are assigned to this page. This means that every new page should be created by a user with r''eviewer'' or admin ''rights'', because only these roles have the necessary rights to make the assignment. If a page is created in this namespace by a user with ''edit'' rights, this page cannot be edited further by this user, unless he/she is assigned by a user with the necessary permissions.

==My assignments==
Users can view their own page assignments by clicking on "Assignments" in their personal menu.
[[File:Manual:zuweisung-usermenu-en.png|alt=My assignments|center|thumb|650x650px|My assignments]]

{{Box Links-en
|Topic1=[[Reference:BlueSpicePageAssignments]]|Topic2=[[Manual:Extension/BlueSpiceReadConfirmation|Request read confirmations from assigned users]]}}

{{Translation}}
[[Category:Quality]]

Manual:Creating and using categories

2022-06-30T12:54:32Z

Hslater: Spelling error : >categoriesto > categories to

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

Categories are a feature of MediaWiki. An index page is automatically created for categories.

Pages can be categorized by adding category tags to the content. These tags generate links at the bottom of the page that lead to an overview of all pages in the same category. This allows for easy browsing of related pages.

==How do I use categories?==
In addition to namespaces, categories are an important organizational principle in the wiki. They allow pages to be grouped and automatically linked to the associated category pages. Categories are usually created by users. In special cases, however, MediaWiki also assigns automatically generated categories (e.g., ''Pages with broken links'').

==Features==
*'''Category tree:''' Categories can be organized as subcategories of main categories.
*'''Tagging''': Categories can be used to spontaneously "tag" pages.
*'''Category manager:''' Categories can be systematically created and used by all users via the category manager.
*'''Multiple categories per page''': A page can be assigned to several categories.
*'''Independent of namespaces''': Categories are available throughout the wiki and cannot be limited to individual namespaces.
*'''Page queries: '''Categories are useful for extensions like [[Manual:Extension/BlueSpiceSmartList|Smartlist]] or Semantic Mediawiki as they are available as query arguments.

==Assigning categories to a page==
<div class="training user">There are different ways to assign a page to categories:

#In the [[Manual:Extension/BlueSpiceDiscovery#Supplementary area|Supplementary area]] at the end of the page
#From the options menu of [[Manual:Extension/VisualEditor|VisualEditor]] (Visual Editing)
#Via manual input as [[Manual:Wikitext|wikitext]] (source code editing)
#Using the link ''[[Manual:Extension/BlueSpiceDiscovery#Page tools|Page tools > ...all actions > Insert category]]''</div><gallery widths="200" heights="200">
File:Manual:Category - footer.png|alt=Supplemental area|Supplemental area
File:Manual:Category - VE.PNG|alt=Visual editor|Visual editor
File:Manual:Category - wikitext.png|alt=Wikitext|Wikitext
File:Manual:Category - all actions.png|alt=Link "...all actions"|Link "...all actions"
</gallery>

===In the supplementary area at the bottom of the page===
The supplement area contains a field for category assignment. Any user with edit rights can click the edit link to add or remove categories from the page. To view all existing categories with subcategories, you can click on the tree icon. Once done, the categories will be confirmed with the tick.
 
===In the visual editor (VisualEditor)===
In the page options menu of [[Manual:Extension/VisualEditor|VisualEditor]] there is a menu item Categories. Here you can update category assignments to the page in edit mode, as well as add a sort key to the category.
 
[[File:Manual:Category - VE.PNG|alt=Options menu in the visual editor|center|thumb|Options menu in the visual editor]]

===In wikitext===
Open an article that you want to assign to a category in edit mode. Now enter the following anywhere in the wiki code (usually at the end of the page though):
<syntaxhighlight lang="text">
[[Category:Production]]
or
[[Category:Production]]
</syntaxhighlight>

{{Messagebox|boxtype=note|icon=|Note text=On category pages, umlauts are listed at the end of the list, e.g. "Märchen" after "Muh". You can use the <nowiki>{{DEFAULTSORT:sortkey}}</nowiki> variable to create an alternative title for the sort (e.g. <nowiki>{{DEFAULTSORT:Maerchen}}</nowiki>).|bgcolor=}}

It is true that:

:*categories can be created in any number and by any user. So before you just get started, it's always best to check which categories already exist to avoid unnecessary duplication of similar categories.
:*a page can be assigned to several categories.
:*the place in the source code where the category link is inserted is technically irrelevant. However, the convention is to include categories '''at the end of an article.'''

==Links to category pages==
For links directly to a category page, a colon is required before the namespace.

Example: <code><nowiki>[[:Category: new_page]]</nowiki></code>

If the colon is missing, the link will not be created, but the page will be tagged with the category instead.
==Category pages==
When users click a category link, the ''Category:<Category_Name>'' page loads. All pages and media that are assigned to a specific category are automatically listed there.

If you click on a category page that has not yet been created - linked in red - you have the option of creating the category page.
==Show all category pages ==
On the special page <code>Special:Categories</code> you can view a list of all existing categories in the wiki. Click on a category to go to the corresponding category page. If a page in the listing has a red background, the category is in use in the wiki, but the associated category page has not yet been created.
==Category manager==
The easiest way to manage categories and subcategories is through the ''Special:Category manager'' page. The [[Manual:Extension/BlueSpiceCategoryManager|Category manager]] can be reached via the menu item ''Global Actions > Management > Categories''.

{{Box_Links-en | Topic1 = [[Manual:Extension/BlueSpiceCategoryManager|Category manager]] |
Topic2 =[https://www.mediawiki.org/wiki/Help:Categories https://www.mediawiki.org/wiki/Help:Categories]}}

[[en:{{FULLPAGENAME}}]]
[[de:Handbuch:Kategorien erstellen und nutzen]]

[[Category:Concept]]
[[Category:Organization]]

Manual:The concept of namespaces

2022-06-30T12:53:22Z

Hslater: Spelling error : mainenanceadmin > maintenanceadmin

<bookshelf src="Book:User manual" />
==What is a namespace?==
[[File:Manual:Namespace-ev.png|300x300px|link=https://youtu.be/CITmttQcsjg|Explainer video on Youtube: Namespaces (Length: 4:33 nin.)|thumb|alt=explainer video intro screen]]A '''namespace''' defines an area in a wiki. You can recognize a namespace by the namespace prefix in the page title:

<code><namespace>:Page title</code>

We sometimes use shelves and closets as an example to make the principle of namespaces clear. There are shelves that everyone can access. Then there are glass cabinets with locks that everyone can look into, but not everyone can edit everything. There are also closed wooden cabinets with a lock, so only selected people can look into that space and work. And every closet can look different.

In a wiki, you will find predefined namespaces. In addition, wiki administrators can create custom namespaces as needed.

There are certain aspects of namespaces that are important to consider before creating a namespace. It is therefore important to understand the characteristics of namespaces and the reasons for using a custom namespace.
===Characteristics of a namespace===

*'''Rights management''': Each namespace can contain its own user rights/roles assignments. However, we recommend flat user hierarchies for wikis.
*'''Activation of features:''' Different functions can be activated in each namespace (e.g., page approvals or read confirmations).
*'''Search function''': Search can be limited to individual namespaces (namespace filter).
*'''One namespace per page''': The same page name in a different namespace creates a new page.
*'''Flat structure''':Namespaces cannot contain other namespaces.
*'''File associations:''' Uploaded files can be assigned to a namespace to apply namespace permissions to files.
*'''Design''': Namespaces can be styled differently.
==BlueSpice standard namespaces==
BlueSpice uses, among others, the 15 standard and the two so-called pseudo namespaces from MediaWiki:

{| class="wikitable tablefullwidth"
|-
!ID
!|'''Namespace'''
! |'''Function'''
|-
|
||Media
||Pseudo-namespace for uploaded images and files. Will be replaced by path of the files.
|-
|
||special
||Pseudo-namespace for special pages.
|-
|0
||(pages)
||These are given without a prefix.
|-
|1
||Talk
||talk page. Is created in addition to each article (also in the following namespaces) to speak about its contents. Additional tab (+).
|-
|2
||User
||User page. Will be created for every logged in user.
|-
|3
||User talk
||Cf. talk
|-
|4
||[Wiki-Name]
||Information about the wiki or the current project. Here: BlueSpice.
|-
|5
||[Wiki-Name]_Talk
||Cf. talk
|-
|6
||Image
||Description of a picture and other files. Is automatically supplemented with version information and information about the occurrence of the file
|-
|7
||File_Talk
||Cf. talk
|-
|8
||MediaWiki
||system messages. A complete list can be found under Special: AllMessages. Can only be changed by registered users.
|-
|9
||MediaWiki_Talk
||Cf. talk
|-
|10
||Template
||Templates can be integrated into other pages.
|-
|11
||Template_talk
||Cf. talk
|-
|12
||Help
||Help pages describe how to perform actions in the wiki. No clear separation from the [wiki name] namespace.
|-
|13
||Help_talk
||Cf. talk
|-
|14
||Category
||Pages can be assigned to categories, which are then accessible in this namespace.
|-
|15
||Category_talk
||Cf. talk
|}

'''Standard namespace:''' A page is assigned to the "Main" namespace, as long as no other namespace is specified.

'''Pseudo namespaces:''' The two pseudo namespaces (Media, Special) are used like normal namespaces, but you cannot edit them or add pages to them.

Most pages in the namespaces are created automatically:
*Special pages are generated by the system during installation.
*Media and image pages are created during file uplad.
*User pages are created whenever a user acts on the wiki.
*Discussion pages are also created with the corresponding pages.
This leaves only the default namespaces ''(Main)'', ''[wiki name]'', ''Template'', ''Help'' and ''Category'' namespaces where pages can be freely created.

== Creating a new namespace ==
You can create additional namespaces by using the Namespace manager under Global actions > Management > [[Manual:Extension/BlueSpiceNamespaceManager|Namespace manager]]. The menu item "Category manager" loads the page <code>Special:NamespaceManager</code>.

== Namespace "MediaWiki" ==
Pages in the MediaWiki namespace can be created and edited by users with "editinterface" permission. By default, these are users whose group is assigned the ''structuremanager, admin,'' or ''maintenanceadmin'' role.

Important uses are:

* '''System Messages:''' Each message has a wiki page with the message key as the name of the page. A list of all announcement pages can be found on Special:AllAnnouncements.
* '''Localizations via ''<nowiki>{{int:messagname}}</nowiki>'':''' An element of the user interface or within a wiki page can be translated into the user language via . Syntax: ''Mediawiki:message name/ISO language code''.
* '''MediaWiki:Common.js''': Contains JavaScript that is loaded for all pages and users.
* '''MediaWiki:Common.css''': Stylesheet that is loaded after the stylesheet of the active skin in the wiki. It applies to all wiki pages.

==Accessing pages in a namespace==
To access or create a page in a specific namespace, its name is simply placed in front of the page title and separated by a colon:

<code><nowiki>[[Setup:Installation|]]</nowiki></code>

In the example, the pipe symbol (straight line) was also added. It has the effect that the namespace won't be displayed for the link label.

If you provide a namespace that is not known to the wiki, the page is created in the standard namespace Main. The portion of the reference specified as the namespace is then added to the title of the item instead and is not recognized as a namespace label.

==Organizing content without namespaces==
If you simply want to group pages in your wiki without the need for controlling access rights, you can use the syntax of the namespaces to '''simulate a namespace in the namespace Main'''. Simply prefix the pages that belong to a group with a name and a colon. If no namespace with this name exists, the prefix simply becomes part of the page name.

That way, it is possible to use pages with the same name in the main namespace and thus let different groups work on content "sets". Since these own "namespace" prefixes are part of the page name, you can now display all pages in a simulated namespace by searching for the prefix in the search field.

Since you can also organize pages with categories and subpages, you should start by planning how you would like to organize the content in your wiki.

After installing your wiki, you can visualize this with the BlueSpice draw.io Plugin directly in your wiki and discuss it with your team.
==Viewing all pages of a namespace==
You can view all pages in a namespace:
#'''Go''' to the Special page "All Pages"
#'''Leave''' the input field empty
#'''Select''' a namespace from the Namespace drop-down menu
#'''Click''' ''Go''
{{Box_Links-en
|Topic1 =[[Manual:Extension/BlueSpiceNamespaceCSS|Namespace CSS manager]]
|Topic2 =[[Manual:Extension/BlueSpiceNamespaceManager|Namespace manager]]}}

User:Hslater

2022-06-28T13:03:01Z

Hslater: create user page