BlueSpice - Recent changes [en]

User:Bmananika

Bmananika — Fri, 10 Apr 2026 13:39:12 GMT

create user page

New page

User blog:Bmananika

Bmananika — Fri, 10 Apr 2026 13:39:12 GMT

Root blog page created

New page

Manual:Extension/VisualEditor/Insert tables

Margit.link-rodrigue — Fri, 10 Apr 2026 13:03:20 GMT

← Older revision		Revision as of 13:03, 10 April 2026
Line 144:		Line 144:
	* integer		* integer
	* number		* number
	* date~~<div class="training anwender">~~		* date
	== Using existing tables ==		== Using existing tables ==
	* Tables can also be inserted as a ~~csv~~ file ~~on a page~~ (~~just~~ drag the CSV file onto the page in edit mode)
	* ~~Complex tables~~ can ~~alternatively~~ be ~~attached to~~ the ~~page as an xlsx file~~.
			The visual editor makes it easy to format content as a table.

			The following alternatives are available:<span><br /></span>

			*CSV file (Chrome, Edge only): Tables can also be inserted onto a page as a CSV file (simply drag the CSV file onto the page in edit mode).

			*XLSX file (Firefox only): Cells can be selected and then dragged into the wiki while holding down the <code>Ctrl</code> key.

	{{Box Links-en\|Topic1=[[Manual:Extension/BlueSpiceFilterableTables\|Filterable tables]]}}</div><section end="training-tabellen" />		{{Box Links-en\|Topic1=[[Manual:Extension/BlueSpiceFilterableTables\|Filterable tables]]}}</div><section end="training-tabellen" />

Setup:Installation Guide/Docker

Hjing — Wed, 08 Apr 2026 11:14:23 GMT

Use most recent BlueSpice version numbers

← Older revision		Revision as of 11:14, 8 April 2026
Line 29:		Line 29:
	For example, run:		For example, run:
	<syntaxhighlight lang=sh>		<syntaxhighlight lang=sh>
	wget https://github.com/hallowelt/bluespice-deploy/archive/refs/tags/5.2.1.zip \		wget https://github.com/hallowelt/bluespice-deploy/archive/refs/tags/5.2.2.zip \
	&& unzip 5.2.1.zip \		&& unzip 5.2.2.zip \
	&& cd bluespice-deploy-5.2.1/compose		&& cd bluespice-deploy-5.2.2/compose
	</syntaxhighlight>		</syntaxhighlight>
	{{Textbox\|boxtype=note\|header=Use one consistent version number\|text=The tag number 5.2.1 in this command (could be 5.1.4, 5.1.5 etc. as well) should also be used as the <code>VERSION=</code> number in Step 2.\|icon=yes}}		{{Textbox\|boxtype=note\|header=Use one consistent version number\|text=The tag number 5.2.2 in this command (could be 5.1.4, 5.1.5, 5.2.1 etc. as well) should also be used as the <code>VERSION=</code> number in Step 2.\|icon=yes}}

	The directory contains the following files:		The directory contains the following files:
Line 94:		Line 94:
	# set or use your data directory		# set or use your data directory
	DATADIR=/data/bluespice		DATADIR=/data/bluespice
	VERSION=5.2.1		VERSION=5.2.2
	EDITION=free		EDITION=free
	BACKUP_HOUR=04		BACKUP_HOUR=04

Manual:Extension/Page Forms

Margit.link-rodrigue — Mon, 30 Mar 2026 15:57:54 GMT

← Older revision		Revision as of 15:57, 30 March 2026
Line 54:		Line 54:
	\|Text-area with simplified [[:de:VisualEditor\|VisualEditor]]. This form input allows to also add tables via form.		\|Text-area with simplified [[:de:VisualEditor\|VisualEditor]]. This form input allows to also add tables via form.
	This functionality is provided by extension [[Reference:VEforAll\|VEforAll]].		This functionality is provided by extension [[Reference:VEforAll\|VEforAll]].

			Note: In some versions of BlueSpice, the display of the drop-down actions in the editor are broken. You can fix them by adding the following to the global stylesheet <code>MediaWiki:Common.css</code>:<syntaxhighlight lang="css">
			/fix page forms issue with visualeditor input /
			.oo-ui-popupToolGroup-tools .oo-ui-tool-link {
			display: block!important;
			}
			</syntaxhighlight>
	\|}		\|}

Reference:BlueSpiceAvatars

Margit.link-rodrigue — Mon, 23 Mar 2026 16:17:37 GMT

← Older revision		Revision as of 16:17, 23 March 2026
Line 1:		Line 1:
	{{BSExtensionInfo		{{BSExtensionInfo
			\|removed=No
	\|status=stable		\|status=stable
	\|developer=HalloWelt		\|developer=HalloWelt
	\|type=BlueSpice		\|type=BlueSpice
	\|edition=BlueSpice ~~pro~~, BlueSpice ~~free~~, BlueSpice farm, BlueSpice cloud		\|edition=BlueSpice free, BlueSpice pro, BlueSpice farm, BlueSpice cloud
	\|compatible=BlueSpice		\|compatible=BlueSpice
	\|category=Personalization		\|category=Personalization
	\|features='''BlueSpiceAvatars''' handles profile images of wiki users. Initially, every user has an automatically generated avatar.		\|features='''BlueSpiceAvatars''' handles profile images of wiki users. Initially, every user has an automatically generated avatar.

	This extension adds an option to each user's page to change ~~his~~ profile image. At the top of a user's page users can see their current profile image and the link "Userimage". Clicking on this link opens a dialog offering several options for setting a profile image:		This extension adds an option to each user's page to change their profile image. At the top of a user's page users can see their current profile image and the link "Userimage". Clicking on this link opens a dialog offering several options for setting a profile image:

	*upload a new image		* upload a new image
	*link to an image that has already been uploaded		* link to an image that has already been uploaded
	*generate a new avatar		* generate a new avatar
	\|desc=Assigns an automatically generated individual profile picture for every user.		\|desc=Assigns an automatically generated individual profile picture for every user.
	\|active=Yes		\|active=Yes

Manual:Extension/BlueSpiceAvatars

Margit.link-rodrigue — Mon, 23 Mar 2026 16:17:04 GMT

← Older revision		Revision as of 16:17, 23 March 2026
Line 54:		Line 54:
	[[File:Manual:Avatars3.png\|alt=\|center\|thumb\|415x415px\|Settings in Config manager]]		[[File:Manual:Avatars3.png\|alt=\|center\|thumb\|415x415px\|Settings in Config manager]]
	{{#dpl:title=Manual:Extension/BlueSpiceConfigManager\|include=#BlueSpiceAvatars}}		{{#dpl:title=Manual:Extension/BlueSpiceConfigManager\|include=#BlueSpiceAvatars}}

	~~{{Box Links-en\|Topic1=[[Reference:BlueSpiceAvatars]]}}~~

	{{Translation}}		{{Translation}}
	[[Category:Personalization]]		[[Category:Personalization]]

Confluence migration

Margit.link-rodrigue — Mon, 23 Mar 2026 12:53:33 GMT

← Older revision		Revision as of 12:53, 23 March 2026
Line 2:		Line 2:

	==Migration tool==		==Migration tool==
	The [https://github.com/hallowelt/migrate-confluence~~?tab=readme-ov-file#migrate-confluence-xml-export-to-mediawiki-import-data~~ migration tool can be found on GitHub] and is [https://github.com/hallowelt/migrate-confluence?tab=readme-ov-file#migrate-confluence-xml-export-to-mediawiki-import-data documented there].		The [https://github.com/hallowelt/migrate-confluence/releases/ migration tool can be found on GitHub] and is [https://github.com/hallowelt/migrate-confluence?tab=readme-ov-file#migrate-confluence-xml-export-to-mediawiki-import-data documented there].

			It is also available as [https://hub.docker.com/r/bluespice/migrate-confluence docker container] for ease of installation and better automation.

	==Extensions==		==Extensions==
Line 24:		Line 26:
	*Comments		*Comments
	*Various macros		*Various macros
	*~~Various~~ layouts		*Some layouts
	*Blog posts
	*Files in an area that cannot be assigned to a page		*Files in an area that cannot be assigned to a page

	== Roadmap ==		== Roadmap ==
	* ~~March '26: Provide Docker Container (ERM46685) - Eases installation and allows for better automation~~		* April '26: Allow for parallel processing (ERM45405) - Speeds up conversion of large Confluence exports
	* March/April '26: Allow for parallel processing (ERM45405) - Speeds up conversion of large Confluence exports		* April '26: Migrate page comments to [[mw:Extension:CommentStreams]] threads (ERM46627) - Additional content
	* ~~March/April '26: Migrate blogs posts to [[mw:Extension:SimpleBlogPage]] pages (ERM46628) - Additional content~~
	* March/April '26: Migrate page comments to [[mw:Extension:CommentStreams]] threads (ERM46627) - Additional content
	* April '26: Add support for historic page and file revisions (ERM35013) - Additional content		* April '26: Add support for historic page and file revisions (ERM35013) - Additional content

File:Semantic MediaWiki-Nomenklatur-86700495.drawio.png

Margit.link-rodrigue — Mon, 23 Mar 2026 10:47:09 GMT

Redaktion uploaded a new version of File:Semantic MediaWiki-Nomenklatur-86700495.drawio.png DrawioEditor

New page

Manual:Semantic MediaWiki/Naming conventions

Margit.link-rodrigue — Mon, 23 Mar 2026 10:44:45 GMT

← Older revision		Revision as of 10:44, 23 March 2026
Line 1:		Line 1:
	==Consistent naming of pages==		==Consistent naming of pages and properties==
	Before you create a semantic template, you first need to define which data to collect. Usually the data can be seen as a data set.		Before you create a semantic template, you first need to define which data to collect. Usually the data can be seen as a data set.
	{{Messagebox\|boxtype=example\|Note text=We want to collect customer data. All customers get their own wiki page. On each page we enter information about the company ''location'', the primary ''contact person'' and the ''date of first contact'' with the company.}}		{{Messagebox\|boxtype=example\|Note text=We want to collect customer data. All customers get their own wiki page. On each page we enter information about the company ''location'', the primary ''contact person'' and the ''date of first contact'' with the company.}}
	It makes sense to name the required pages consistently. In our example, we would create the pages ~~''Template:Customer data'', ''Form:Customer data'' and ''Category:Customer data.'' You can even consider putting the pages in their own [[Manual:The concept of namespaces\|namespace]] ''Customer''.~~		It makes sense to name the required pages consistently. In our example, we would create the pages

	For the properties, you have to consider that the property ''location'' could also be used outside the context of customer pages. There could be locations for partners or vendors, for example. ~~Each context could get their own property~~ (~~e.g. ''~~Customer location'') ~~or share~~ the ~~same property~~ location ~~and then use a different category (~~Customer ~~data, Partner data~~, ...) ~~on the wiki pages to distinguish them.~~		* <code>Template:Customer</code> to show the customer information,
			* <code>Form:Customer</code> to enter the values for the customer data,
			* <code>Category:Customer</code> to collect all pages that use the template "Customer".


			To maintain a catalog with all your customer information, you can

			* consider putting the pages in their own [[Manual:The concept of namespaces\|namespace]] <code>Customer</code>'','' or
			* collect the pages as subpages of the page <code>Customer.</code>

			The choice where to maintain your customer pages depends on the setup of your wiki and how you organize content for your specific use-case.

			=== Organizing your properties ===
			For the properties, you have to consider that the property ''location'' could also be used outside the context of customer pages. There could be locations for partners or vendors, for example. You need to decide if they are related or not. Based on your decision, you can collect the values for the customer locations in the following properties:

			* Property:Location (collects all location information in the wiki)
			* Poperty:Customer location (collects specifically the location information of customers)
			* Property:Customer/location (collects specifically the location of customers, but seen as one of multiple "grouped" properties for customers such as Customer/contact, etc...)

	==Classification of information==		==Classification of information==
Line 14:		Line 31:
	Certain properties that describe each customer more precisely are now collected as customer data. Normally, these properties are directly related to the page itself. It can therefore be helpful to express the semantic relationship directly in the property:<pre>Customer Technicon has location Regensburg.		Certain properties that describe each customer more precisely are now collected as customer data. Normally, these properties are directly related to the page itself. It can therefore be helpful to express the semantic relationship directly in the property:<pre>Customer Technicon has location Regensburg.
	(page) (property) (value)</pre>		(page) (property) (value)</pre>
	Therefore, we capture the relationship to the page in the property name: ''Has location''.		Therefore, we can capture the relationship to the page in the property name: ''Has location''.

	{{Messagebox\|boxtype=note\|Note text=It is not required to express this relationship function of properties (as predicates). The property can also simply be named "location" if its intended use is clear.		{{Messagebox\|boxtype=note\|Note text=It is not required to express this relationship function of properties (as predicates). The property can also simply be named "location" if its intended use is clear.


	There is, however a difference between "Has location" and "Is location of". For example, the customer Technicon has the location Regensburg. The city of Regensburg, on the other hand, is the location of the customer Technicon.}}<br /><bs:drawio filename="Semantic MediaWiki/Nomenklatur-86700495" /><br />		There is, however a difference between "Has location" and "Is location of". For example, the customer Technicon has the location Regensburg. The city of Regensburg, on the other hand, is the location of the customer Technicon.}}<br /><bs:drawio filename="Semantic MediaWiki/Nomenklatur-86700495" /><br />{{Box Links-en\|Topic1=[https://www.semantic-mediawiki.org/wiki/Help:Classification https://www.semantic-mediawiki.org/wiki/Help:Classification]}}

	~~==Subpages==~~
	We can also work with a subpage system and work with properties like Property:Customer/Has_location, Property:Customer/ Has_first_contact, and so on. If the property "Location" is also to be used elsewhere, it is advisable to define Property: Has_location instead of Property:Customer/Has_location.

	When properties can be clearly assigned to a use case or have several use cases, it makes sense to name them accordingly. For example, Property:Customer/Contract_number can be a sequential, whole number, but Property:Partner/Contract_number can contain entries such as "1.1.5" or "4.3.7".
	{{Box Links-en\|Topic1=[https://www.semantic-mediawiki.org/wiki/Help:Classification https://www.semantic-mediawiki.org/wiki/Help:Classification]}}
	[[de:Handbuch:Semantic_MediaWiki/Nomenklatur]]		[[de:Handbuch:Semantic_MediaWiki/Nomenklatur]]
	[[en:{{FULLPAGENAME}}]]		[[en:{{FULLPAGENAME}}]]

Manual:Create pages

Margit.link-rodrigue — Mon, 23 Mar 2026 10:29:47 GMT

← Older revision		Revision as of 10:29, 23 March 2026
Line 6:		Line 6:

	#'''Click''' the + button in the [[Manual:Extension/BlueSpiceDiscovery\|Header]]. A dialog window opens.		#'''Click''' the + button in the [[Manual:Extension/BlueSpiceDiscovery\|Header]]. A dialog window opens.
	#'''Enter <nowiki/>'''a page name. If th'''''<nowiki/>'''''e page already exists, it will be listed under the text field. ~~This makes it easier to create the new page as a subpage.~~ If you want to create the page in an existing namespace, add the namespace name as a prefix, followed by a colon. Example: <code>Manual:Visual editing</code> [[File:Manual:Manual Create pages 1748245897327.png\|alt=Dialog field with the new page name "Community"\|center\|thumb\|Create a new page]]		#'''Enter <nowiki/>'''a page name. If th'''''<nowiki/>'''''e page already exists, it will be listed under the text field. If you want to create the page in an existing [[Manual:The concept of namespaces\|namespace]], add the namespace name as a prefix, followed by a colon. Example: <code>Manual:Visual editing</code> [[File:Manual:Manual Create pages 1748245897327.png\|alt=Dialog field with the new page name "Community"\|center\|thumb\|Create a new page]]
	#'''Click''' done.		#'''Click''' done.
	#'''C''<nowiki/>''hoose''' ''Blank Page'' or a page template if your wiki ~~shows the~~ page templates page as the next step. This step is omitted if no page templates are available. The page now opens in edit mode.		#'''C''<nowiki/>''hoose''' ''Blank Page'' or a page template if your wiki offers a selection page templates page as the next step. This step is omitted if no page templates are available. The page now opens in edit mode.
	#'''Save''' the page. After saving the page for the first time, the page exists in the wiki. Click the edit icon of the page to switch back to edit mode.		#'''Save''' the page. After saving the page for the first time, the page exists in the wiki. Click the edit icon of the page to switch back to edit mode.

Manual:Semantic MediaWiki/Naming conventions

Margit.link-rodrigue — Mon, 23 Mar 2026 09:48:20 GMT

← Older revision		Revision as of 09:48, 23 March 2026
Line 1:		Line 1:
	~~{{Messagebox\|<bookshelf src="Book:Getting started with Semantic MediaWiki" />~~
	==Consistent naming of pages==		==Consistent naming of pages==
	Before you create a semantic template, you first need to define which data to collect. Usually the data can be seen as a data set.		Before you create a semantic template, you first need to define which data to collect. Usually the data can be seen as a data set.
	{{Messagebox\|boxtype=example\|Note text=We want to collect customer data. All customers get their own wiki page. On each page we enter information about the company ''location'', the primary ''contact person'' and the ''date of first contact'' with the company.}}		{{Messagebox\|boxtype=example\|Note text=We want to collect customer data. All customers get their own wiki page. On each page we enter information about the company ''location'', the primary ''contact person'' and the ''date of first contact'' with the company.}}
	It makes sense to name the required pages consistently. In our example, we would create the pages ''Template:Customer data'', ''Form:Customer data'' and ''Category:Customer data.'' You can even consider putting the pages in their own ~~namespace~~ [[Manual:The concept of namespaces\|namespace]] ''Customer''.		It makes sense to name the required pages consistently. In our example, we would create the pages ''Template:Customer data'', ''Form:Customer data'' and ''Category:Customer data.'' You can even consider putting the pages in their own [[Manual:The concept of namespaces\|namespace]] ''Customer''.
	~~[[Manual:The concept of namespaces]]~~
	For the properties, you have to ~~consdier~~ that the property ''location'' could also be used outside the context of customer pages. There could be locations for partners or vendors, for example. Each context could get their own property (e.g. ''Customer location'') or share the same property location and then use a different category (Customer data, Partner data, ...) on the wiki pages to distinguish them.		For the properties, you have to consider that the property ''location'' could also be used outside the context of customer pages. There could be locations for partners or vendors, for example. Each context could get their own property (e.g. ''Customer location'') or share the same property location and then use a different category (Customer data, Partner data, ...) on the wiki pages to distinguish them.

	==Classification of information==		==Classification of information==

	===Categories===		===Categories===
	Generell unterscheiden wir bei der Klassifizierung von Seiten zwischen Kategorien und Attributen. Mit Kategorien wird die Seite an sich beschrieben. Am Beispiel Kunden kategorisieren wir jede Kundenseite mit dem Schlagwort ''Kundendaten.'' Die Kategorie sammelt also alle Seiten, auf der sich Kundendaten befinden.

	When classifying pages, we generally differentiate between categories and properties. The page itself is described with categories. Using the example of customers, we categorize each customer page with the keyword ''Customer data''. The category therefore collects all pages on which customer data is located.		When classifying pages, we generally differentiate between categories and properties. The page itself is described with categories. Using the example of customers, we categorize each customer page with the keyword ''Customer data''. The category therefore collects all pages on which customer data is located.

	===Properties===		===Properties===
	In den Kundendaten werden nun bestimmte Eigenschaften gesammelt, die jeden Kunden genauer beschreiben. Hierzu werden Attribute erstellt. Im Normalfall stehen diese Attribute in einer direkten Beziehung zur Seite selbst. Daher kann es hilfreich sein, die semantische Beziehung über das Attribut auszudrücken:		Certain properties that describe each customer more precisely are now collected as customer data. Normally, these properties are directly related to the page itself. It can therefore be helpful to express the semantic relationship directly in the property:<pre>Customer Technicon has location Regensburg.

	Certain properties that describe each customer more precisely are now collected as customer data. Normally, these properties are directly related to the page itself. It can therefore be helpful to express the semantic relationship directly in the property:
	<pre>Customer Technicon has location Regensburg.
	(page) (property) (value)</pre>		(page) (property) (value)</pre>
	Therefore, we capture the relationship to the page in the property name: ''Has location''.		Therefore, we capture the relationship to the page in the property name: ''Has location''.

	{{Messagebox\|boxtype=note\|Note text=It is not required to express this relationship function of properties (as predicates). The property can also simply be ~~names~~ "location" if its intended use is clear.		{{Messagebox\|boxtype=note\|Note text=It is not required to express this relationship function of properties (as predicates). The property can also simply be named "location" if its intended use is clear.

BlueSpice 5.1

Margit.link-rodrigue — Fri, 20 Mar 2026 13:22:28 GMT

Redirected page to BlueSpice 5

New page

#REDIRECT [[BlueSpice 5]]

Manual:Extension/BlueSpiceArticleInfo

Margit.link-rodrigue — Fri, 20 Mar 2026 09:46:39 GMT

← Older revision		Revision as of 09:46, 20 March 2026
Line 1:		Line 1:
	~~<bookshelf src="Book:User manual" />~~
	{{DISPLAYTITLE:Page information}}		{{DISPLAYTITLE:Page information}}

Line 12:		Line 11:
	*Last edit (list of editors, time of last edit, last editor)		*Last edit (list of editors, time of last edit, last editor)
	*Properties (associated categories, templates used on the page, links, etc.)		*Properties (associated categories, templates used on the page, links, etc.)
	*Authors of this page		*[[Manual:Extension/BlueSpiceAuthors\|Authors]] of this page
	*[[Manual:Extension/BlueSpicePageAssignments\|Assignments]]		*[[Manual:Extension/BlueSpicePageAssignments\|Assignments]]
	*Readers of this page (only visible to admin users)		*[[Manual:Extension/BlueSpiceReaders\|Readers]] of this page (only visible to admin users)
	*[[Manual:Extension/BlueSpiceExpiry\|Expiry of the page]]		*[[Manual:Extension/BlueSpiceExpiry\|Expiry]] of the page
	*[[Manual:Extension/BlueSpiceReminder\|Reminder]]		*[[Manual:Extension/BlueSpiceReminder\|Reminder]]
	*Process usage		*[[Manual:Extension/CognitiveProcessDesigner\|Process]] usage

			* [[Manual:Extension/ChatBot\|ChatBot]] indexing status

	[[File:Manual:Manual Extension BlueSpiceArticleInfo 1750167946366.png\|alt=Page information dialog\|center\|thumb\|500x500px\|Page information dialog]]		[[File:Manual:Manual Extension BlueSpiceArticleInfo 1750167946366.png\|alt=Page information dialog\|center\|thumb\|500x500px\|Page information dialog]]

Reference:BlueSpiceArticleInfo

Margit.link-rodrigue — Fri, 20 Mar 2026 09:42:18 GMT

← Older revision		Revision as of 09:42, 20 March 2026
Line 9:		Line 9:
	\|features=This extension provides additional information compared to the standard MediaWiki page information. In the Discovery skin, this information can be accessed in the [[Manual:Extension/BlueSpiceDiscovery{{!}}page tools]] using the link ''all actions... > Page Information''.		\|features=This extension provides additional information compared to the standard MediaWiki page information. In the Discovery skin, this information can be accessed in the [[Manual:Extension/BlueSpiceDiscovery{{!}}page tools]] using the link ''all actions... > Page Information''.

	The following information is included:		The following information is included (depending on installed extensions):

	*General ~~Info~~		*General
	*Last edit		*Last edit
	*Properties		*Properties
	*Expiry of page
	*Authors of this page		*Authors of this page
			*Assignments
	*Readers of this page		*Readers of this page
			*Expiry of page
	*Reminder		*Reminder
			*Process usage
			*ChatBot indexing status
	\|desc=Displays important meta information about a page like the last edit or the number of edits.		\|desc=Displays important meta information about a page like the last edit or the number of edits.
	}}		}}

Manual:Extension/HitCounters

Margit.link-rodrigue — Thu, 19 Mar 2026 16:44:39 GMT

← Older revision		Revision as of 16:44, 19 March 2026
Line 1:		Line 1:
	The extension '''HitCounter''' counts human page views~~, but does not ignore multiple visits~~.		The extension '''HitCounter''' counts human page views.

	== How it works ==		== How it works ==

Reference:HitCounters

Margit.link-rodrigue — Thu, 19 Mar 2026 16:41:33 GMT

← Older revision		Revision as of 16:41, 19 March 2026
Line 9:		Line 9:
	\|license=GPL v3+		\|license=GPL v3+
	\|docu=https://www.mediawiki.org/wiki/Extension:HitCounters		\|docu=https://www.mediawiki.org/wiki/Extension:HitCounters
	\|features='''HitCounters''' extension provides the page views functionality that was [https://www.mediawiki.org/wiki/MediaWiki_1.25#Hit_counters_removed removed in MediaWiki 1.25].		\|features=The '''HitCounters''' extension provides the page views functionality that was [https://www.mediawiki.org/wiki/MediaWiki_1.25#Hit_counters_removed removed in MediaWiki 1.25].

	Before MediaWiki 1.25, the page views counting functionality was ~~in core~~ MediaWiki. This extension is based on that same code, but was deliberately done in a more lightweight way in order to speed up processing time. Many lines of superfluous code were removed. Also, the old MediaWiki core code did numerous database queries on every page hit; these have all been removed as well. This change may possibly lead to some inaccuracies in the data.		Before MediaWiki 1.25, the page views counting functionality was part ofcore MediaWiki. This extension is based on that same code, but was deliberately done in a more lightweight way in order to speed up processing time. Many lines of superfluous code were removed. Also, the old MediaWiki core code did numerous database queries on every page hit; these have all been removed as well. This change may possibly lead to some inaccuracies in the data.

	~~The core differences that wiki administrators need to know are:~~

	*The hit counts are stored in cache.
	*The visible hit count at the bottom of each page is updated only once per day. (Pages with hit count less than 100 are updated once per minute.)
	*If you refresh your browser on a wiki page, that hit is ignored.
	}}		}}
	{{wcagCheck		{{wcagCheck

Manual:Extension/HitCounter

Margit.link-rodrigue — Thu, 19 Mar 2026 16:39:36 GMT

← Older revision		Revision as of 16:39, 19 March 2026
(4 intermediate revisions by the same user not shown)
Line 8:		Line 8:

	=== Why SMW and DPL show different page-view numbers ===		=== Why SMW and DPL show different page-view numbers ===
	Even when both rely on HitCounters, they read the values at '''different points in time''' and with '''different caching layers''', which leads to ~~small~~ discrepancies. Below are the main reasons.		Even when both rely on HitCounters, they read the values at '''different points in time''' and with '''different caching layers''', which leads to discrepancies. Below are the main reasons.
	{\| class="wikitable"		{\| class="wikitable"
	!Feature		!Feature
Line 98:		Line 98:
	# Run your SMW query again.		# Run your SMW query again.

	You will see SMW “catch up” to the DPL counter. However, the values might still differ.		You will see SMW “catch up” to the DPL counter. However, the values might still differ based on the above reasons.


	Example queries:<syntaxhighlight lang="text">		Example queries:<syntaxhighlight lang="text">
			'''Output SMW:'''
	{{#ask: [[:+]] [[Modification date::+]]		{{#ask: [[:+]] [[Modification date::+]]
	\|?Number_of_page_views		\|?Number_of_page_views
Line 109:		Line 110:
	\|sort=Number_of_page_views		\|sort=Number_of_page_views
	\|order=desc		\|order=desc
			\|searchlabel=
	}}		}}

			'''Output DPL:'''
	<dpl>		<dpl>
	namespace =		namespace =
Line 120:		Line 122:
	</dpl>		</dpl>
	</syntaxhighlight>		</syntaxhighlight>
	Output:		'''Output SMW:'''
	{{#ask: [[:+]] [[Modification date::+]]		{{#ask: [[:+]] [[Modification date::+]]
	\|?Number_of_page_views		\|?Number_of_page_views
Line 128:		Line 130:
	\|sort=Number_of_page_views		\|sort=Number_of_page_views
	\|order=desc		\|order=desc
			\|searchlabel=
	}}		}}

			'''Output DPL:'''
	<dpl>		<dpl>
	namespace =		namespace =
Line 138:		Line 141:
	addpagecounter = true		addpagecounter = true
	</dpl>		</dpl>

	~~Current page (localized):~~
	~~{{#invoke:PageViews\|get}}~~
	~~Specific page (number only):~~
	~~{{#invoke:PageViews\|get\|page=Main Page\|plain=yes}}~~
	~~With fallback if anything goes wrong:~~
	~~{{#invoke:PageViews\|get\|page=Unknown:Title\|plain=yes\|fallback=0}}~~

Module:PageViews

Margit.link-rodrigue — Thu, 19 Mar 2026 16:20:09 GMT

← Older revision		Revision as of 16:20, 19 March 2026
Line 1:		Line 1:
	-- Module:PageViews (~~compact~~)		-- Module:PageViews (preprocess variant)
	-- Live page view count via Extension:HitCounters' NUMBEROFVIEWS.		-- Live page view count via Extension:HitCounters' {{NUMBEROFVIEWS:Title}}.
	-- Usage:		-- Usage:
	-- {{#invoke:PageViews\|get}} -- current page, localized		-- {{#invoke:PageViews\|get}} -- current page, localized
	-- {{#invoke:PageViews\|get\|page=Main Page}} -- specific page, localized		-- {{#invoke:PageViews\|get\|page=Main Page}} -- specific page, localized
	-- {{#invoke:PageViews\|get\|page=Main Page\|plain=yes}}-- just the number		-- {{#invoke:PageViews\|get\|page=Main Page\|plain=yes}}-- just the number
	-- {{#invoke:PageViews\|get\|page=Foo\|fallback=0}} -- 0 if ~~not available~~		-- {{#invoke:PageViews\|get\|page=Foo\|fallback=0}} -- fallback if unavailable

	local p = {}		local p = {}
Line 18:		Line 18:
	local function fetchViews(title)		local function fetchViews(title)
	local frame = mw.getCurrentFrame()		local frame = mw.getCurrentFrame()
	-- Try raw ~~flags (some~~ HitCounters ~~builds support them)~~, then ~~fallback~~.		-- Try raw flag if your HitCounters build supports it, then fall back.
	local v = ~~frame:callParserFunction~~('NUMBEROFVIEWS', title.prefixedText ~~.. '\|R'~~)		local wikitext = string.format('{{NUMBEROFVIEWS:%s\|R}}', title.prefixedText)
	or frame:~~callParserFunction~~('~~NUMBEROFVIEWS~~'~~, title.prefixedText ..~~ '~~\|raw~~')		local v = frame:preprocess(wikitext)
	or frame:~~callParserFunction~~('NUMBEROFVIEWS', title.prefixedText)		if not v or v == '' or v:match('^⧼') then
			v = frame:preprocess(string.format('{{NUMBEROFVIEWS:%s}}', title.prefixedText))
			end
	if not v or v == '' then return nil end		if not v or v == '' then return nil end
	local digits = tostring(v):gsub('[^0-9]', '')		local digits = tostring(v):gsub('[^0-9]', '')
Line 28:		Line 30:
	end		end

	~~-- {{#invoke:PageViews\|get\|page=...\|plain=yes\|fallback=...}}~~
	function p.get(frame)		function p.get(frame)
	-- collect args (support parent template)		-- collect args (support parent template)

Manual:Extension/HitCounter

Margit.link-rodrigue — Thu, 19 Mar 2026 16:19:07 GMT

← Older revision		Revision as of 16:19, 19 March 2026
Line 138:		Line 138:
	addpagecounter = true		addpagecounter = true
	</dpl>		</dpl>

			Current page (localized):
			{{#invoke:PageViews\|get}}
			Specific page (number only):
			{{#invoke:PageViews\|get\|page=Main Page\|plain=yes}}
			With fallback if anything goes wrong:
			{{#invoke:PageViews\|get\|page=Unknown:Title\|plain=yes\|fallback=0}}

Module:PageViews

Margit.link-rodrigue — Thu, 19 Mar 2026 16:17:59 GMT

Created page with "-- Module:PageViews (compact) -- Live page view count via Extension:HitCounters' NUMBEROFVIEWS. -- Usage: -- {{#invoke:PageViews|get}} -- current page, localized -- {{#invoke:PageViews|get|page=Main Page}} -- specific page, localized -- {{#invoke:PageViews|get|page=Main Page|plain=yes}}-- just the number -- {{#invoke:PageViews|get|page=Foo|fallback=0}} -- 0 if not available local p = {} local function normalizeTitle(txt)..."

New page

-- Module:PageViews (compact)
-- Live page view count via Extension:HitCounters' NUMBEROFVIEWS.
-- Usage:
-- {{#invoke:PageViews|get}} -- current page, localized
-- {{#invoke:PageViews|get|page=Main Page}} -- specific page, localized
-- {{#invoke:PageViews|get|page=Main Page|plain=yes}}-- just the number
-- {{#invoke:PageViews|get|page=Foo|fallback=0}} -- 0 if not available

local p = {}

local function normalizeTitle(txt)
if not txt or txt == '' then
return mw.title.getCurrentTitle()
end
return mw.title.new(txt)
end

local function fetchViews(title)
local frame = mw.getCurrentFrame()
-- Try raw flags (some HitCounters builds support them), then fallback.
local v = frame:callParserFunction('NUMBEROFVIEWS', title.prefixedText .. '|R')
or frame:callParserFunction('NUMBEROFVIEWS', title.prefixedText .. '|raw')
or frame:callParserFunction('NUMBEROFVIEWS', title.prefixedText)
if not v or v == '' then return nil end
local digits = tostring(v):gsub('[^0-9]', '')
if digits == '' then return nil end
return tonumber(digits)
end

-- {{#invoke:PageViews|get|page=...|plain=yes|fallback=...}}
function p.get(frame)
-- collect args (support parent template)
local a = frame.args or {}
local parent = frame:getParent()
if parent and parent.args then
for k,v in pairs(parent.args) do
if a[k] == nil or a[k] == '' then a[k] = v end
end
end

local t = normalizeTitle(a.page or a[1])
if not t then return a.fallback or '' end

local n = fetchViews(t)
if not n then return a.fallback or '' end

if (a.plain or ''):lower():match('^(yes|true|1)$') then
return tostring(n)
end
return mw.language.getContentLanguage():formatNum(n)
end

return p

Manual:Extension/HitCounter

Margit.link-rodrigue — Thu, 19 Mar 2026 16:12:44 GMT

← Older revision		Revision as of 16:12, 19 March 2026
(3 intermediate revisions by the same user not shown)
Line 9:		Line 9:
	=== Why SMW and DPL show different page-view numbers ===		=== Why SMW and DPL show different page-view numbers ===
	Even when both rely on HitCounters, they read the values at '''different points in time''' and with '''different caching layers''', which leads to small discrepancies. Below are the main reasons.		Even when both rely on HitCounters, they read the values at '''different points in time''' and with '''different caching layers''', which leads to small discrepancies. Below are the main reasons.
			{\| class="wikitable"
			!Feature
			!Source
			!Updates
			!May lag?
			\|-
			!'''SMW <code>Number_of_page_views</code>'''
			\|SMW store (snapshot)
			\|Only when page is parsed/resaved
			\|✔ Yes
			\|-
			!'''DPL <code>ordermethod=counter</code>'''
			\|<code>page.page_counter</code> (live)
			\|Immediately when HitCounters logs a view
			\|✘ No
			\|}

	==== SMW stores values (snapshot) – DPL reads live values ====		==== SMW stores values (snapshot) – DPL reads live values ====
Line 89:		Line 105:
	\|?Number_of_page_views		\|?Number_of_page_views
	\|limit=5		\|limit=5
			\|format=ul
			\|headers=hide
	\|sort=Number_of_page_views		\|sort=Number_of_page_views
	\|order=desc		\|order=desc
Line 105:		Line 123:
	{{#ask: [[:+]] [[Modification date::+]]		{{#ask: [[:+]] [[Modification date::+]]
	\|?Number_of_page_views		\|?Number_of_page_views
	\|limit=10		\|limit=5
			\|format=ul
			\|headers=hide
	\|sort=Number_of_page_views		\|sort=Number_of_page_views
	\|order=desc		\|order=desc
Line 115:		Line 135:
	ordermethod = counter		ordermethod = counter
	order = descending		order = descending
	count = 10		count = 5
	addpagecounter = true		addpagecounter = true
	</dpl>		</dpl>

MediaWiki:Hitcounters-nviews

Margit.link-rodrigue — Thu, 19 Mar 2026 16:09:30 GMT

← Older revision		Revision as of 16:09, 19 March 2026
Line 1:		Line 1:
	$		$1

MediaWiki:Hitcounters-nviews

Margit.link-rodrigue — Thu, 19 Mar 2026 16:08:49 GMT

Created page with "$"

New page

Manual:Extension/HitCounter

Margit.link-rodrigue — Thu, 19 Mar 2026 16:08:25 GMT

Created page with "The extension '''HitCounter''' counts human page views, but does not ignore multiple visits. == How it works == The extension counts page views and stores them in the MediaWiki database field <code>page.page_counter</code>. Other extensions use this field to return page visit numbers. == Output of the page views number == The extensions Semantic MediaWiki (SMW) and DPL3 (DPL), which are bundled with the BlueSpice distribution, both use the field value for <code>page...."

New page

The extension '''HitCounter''' counts human page views, but does not ignore multiple visits.

== How it works ==
The extension counts page views and stores them in the MediaWiki database field <code>page.page_counter</code>. Other extensions use this field to return page visit numbers.

== Output of the page views number ==
The extensions Semantic MediaWiki (SMW) and DPL3 (DPL), which are bundled with the BlueSpice distribution, both use the field value for <code>page.page_counter.</code> However, the number that is returned in SMW and DPL queries usually differs.

=== Why SMW and DPL show different page-view numbers ===
Even when both rely on HitCounters, they read the values at '''different points in time''' and with '''different caching layers''', which leads to small discrepancies. Below are the main reasons.

==== SMW stores values (snapshot) – DPL reads live values ====
'''SMW’s property "Number_of_page_views":'''

* SMW stores the value in its DataStore.
* A page must be parsed/resaved for SMW to update the stored property.
* Therefore: the number can lag behind the real counter.

'''DPL3 ordermethod=counter:'''

* DPL reads the current page.page_counter field directly.
* It does not use SMW data.
* This always shows the latest number, as recorded by HitCounters.

'''Result:''' SMW can show an older number than DPL.

==== Caching differences (ParserCache vs. SMW store) ====
'''SMW:'''

* Uses its own store (SQL + SMW query cache).
* Property values only change when the page is reparsed.

'''DPL:'''

* Uses MediaWiki’s normal page cache but reads the counter directly every time.

If a page received new hits since its last SMW update:

* DPL shows the new higher number
* SMW still shows the older value until the page is updated

=== HitCounters updates only on full page views ===
HitCounters increments the view count only when:

* A normal, human page view occurs

* Not on: API calls, bot views, thumbnail loads, SMW queries, DPL queries

This means numbers may diverge temporarily depending on viewing patterns.

==== Some skins bypass counters ====
If some users view pages via:

* mobile skin
* VisualEditor previews
* REST requests
* API-parsed pages

…those views may not be counted.

If these users access a page differently at different times, SMW and DPL appear inconsistent.

==== SMW’s “Number_of_page_views” rounds or normalizes values ====
SMW’s special property sometimes:

* stores the view count as an integer
* may update only when semantic parsing occurs
* may skip updates depending on SMW’s DeferredUpdate behavior

DPL always shows the raw integer.

==== Quick way to test ====
Take a page with a visible difference (example: SMW shows 120, DPL shows 132).

Do this:

# Open the page → Edit → Save (no change needed). This forces SMW to refresh <code>Number_of_page_views</code>.
# Run your SMW query again.

You will see SMW “catch up” to the DPL counter. However, the values might still differ.

Example queries:<syntaxhighlight lang="text">
{{#ask: [[:+]] [[Modification date::+]]
|?Number_of_page_views
|limit=5
|sort=Number_of_page_views
|order=desc
}}

<dpl>
namespace =
ordermethod = counter
order = descending
count = 5
addpagecounter = true
</dpl>
</syntaxhighlight>
Output:
{{#ask: [[:+]] [[Modification date::+]]
|?Number_of_page_views
|limit=10
|sort=Number_of_page_views
|order=desc
}}

<dpl>
namespace =
ordermethod = counter
order = descending
count = 10
addpagecounter = true
</dpl>

Manual:Extension/PDFCreator

Margit.link-rodrigue — Wed, 18 Mar 2026 08:43:56 GMT

← Older revision		Revision as of 08:43, 18 March 2026
Line 97:		Line 97:
	{		{
	"embed-page-toc": true,		"embed-page-toc": true,
			"nsPrefix":true,
	"attachments": true,		"attachments": true,
	"suppress-links": false,		"suppress-links": false,
Line 126:		Line 127:
	</syntaxhighlight>This setting is applied to the book PDF export and ,starting with BlueSpice{{Bsvs\|bsvFrom=5.1.2}}, also works for the single-page PDF export.		</syntaxhighlight>This setting is applied to the book PDF export and ,starting with BlueSpice{{Bsvs\|bsvFrom=5.1.2}}, also works for the single-page PDF export.
	\|-		\|-
	\| ~~style="" \|Ignore redirect~~		\|Hide namespace prefix
	\| ~~style="" \|no-redirect~~		\|nsPrefix
	\| ~~style="" \|false~~		\|true
	\| ~~style="" \|If links are redirecting to a different page,~~ the ~~target~~ page ~~is not included~~ in the ~~pdf~~.		\|Suppresses the output of the namespace prefix for all page names in the header, footer, and PDF cover page.
	\|-		\|-
	\| style="" \|Allow attachments		\| style="" \|Allow attachments
Line 135:		Line 136:
	\| style="" \|true		\| style="" \|true
	\| style="" \|If files are directly linked with syntax <code>Media:</code> , the files are also attached in the pdf.		\| style="" \|If files are directly linked with syntax <code>Media:</code> , the files are also attached in the pdf.
			\|-
			\| style="" \|Ignore redirect
			\| style="" \|no-redirect
			\| style="" \|false
			\| style="" \|If links are redirecting to a different page, the target page is not included in the pdf.
	\|-		\|-
	\| style="" \|Disable links in PDF		\| style="" \|Disable links in PDF
Line 215:		Line 221:
	\|-		\|-
	! style="" \|Properties		! style="" \|Properties
	\| style="" \|~~Allows to control some aspects of the PDF output. The following properties are available (shown in default settings):<syntaxhighlight lang="json">~~		\| style="" \|see section [[#Properties]]
	{
	~~"embed-page-toc": true,~~
	~~"nsPrefix": true,~~
	~~"attachments": true,~~
	~~"suppress-links": false,~~
	~~"no-redirect": false,~~
	~~"coverBackground": "File:filename.jpg"~~
	}
	~~</syntaxhighlight>~~
	\|-		\|-
	! style="" \|Description		! style="" \|Description

Manual:Extension/BlueSpiceConfigManager

Margit.link-rodrigue — Wed, 18 Mar 2026 08:28:51 GMT

erm 43603

← Older revision		Revision as of 08:28, 18 March 2026
(One intermediate revision by the same user not shown)
Line 368:		Line 368:
	===PDFCreator===		===PDFCreator===
	[[File:PDFCreator_config.png\|alt=Konfiguration for the default page export template and default cover image\|center\|thumb\|650x650px\|PDFCreator Konfiguration]]		[[File:PDFCreator_config.png\|alt=Konfiguration for the default page export template and default cover image\|center\|thumb\|650x650px\|PDFCreator Konfiguration]]
	:
	~~'''Hide namespace prefix in PDF:''' Removes the namespace prefix from titles and from template parameter "title" in the PDF output.~~
	* '''Default export template for pages:''' The default template is shown when users select an export template in "Page" mode. It is also used when clicking on the PDF link for the [[Manual:Extension/ContentDroplets\|Content Droplet]] ''PDF Link'' .		* '''Default export template for pages:''' The default template is shown when users select an export template in "Page" mode. It is also used when clicking on the PDF link for the [[Manual:Extension/ContentDroplets\|Content Droplet]] ''PDF Link'' .

	* '''Default cover background image'''		* '''Default cover background image:''' Admins can also set a default cover background image. It is applied whenever the document preface of the template contains the standard "intro"-wrapper: <syntaxhighlight lang="html">


	Admins can also set a default cover background image. It is applied whenever the document preface of the template contains the standard "intro"-wrapper:<syntaxhighlight lang="html">
	<div class="pdfcreator-intro">		<div class="pdfcreator-intro">
	....		....
	</div>		</div>
	</syntaxhighlight>Default image:		</syntaxhighlight>Default image: <code>/app/bluespice/w/extensions/BlueSpiceBookshelf/data/common/images/bs-cover.png</code> Output: [[File:Manual:Standard PDF cover.png\|alt=Image of an enlarged keyboard key with book symbol\|center\|thumb\|Default PDF cover image]]

	<code>/app/bluespice/w/extensions/BlueSpiceBookshelf/data/common/images/bs-cover.png</code>

	Output:
	[[File:Manual:Standard PDF cover.png\|alt=Image of an enlarged keyboard key with book symbol\|center\|thumb\|Default PDF cover image]]



	~~The~~ image path can be deleted. In this case, no image will be output by default.		The image path can be deleted. In this case, no image will be output by default.

	Alternatively, an uploaded image file can be specified (without a namespace prefix), for example: <code>industry.jpg</code>		Alternatively, an uploaded image file can be specified (without a namespace prefix), for example: <code>industry.jpg</code>

Development

Rvogel1 — Tue, 17 Mar 2026 07:03:30 GMT

← Older revision		Revision as of 07:03, 17 March 2026
Line 18:		Line 18:
	Create a <code>docker-compose.overrides.yml</code> file with the following content:		Create a <code>docker-compose.overrides.yml</code> file with the following content:
	<syntaxhighlight lang="yaml">		<syntaxhighlight lang="yaml">
			x-common-dev: &x-common
			image: docker.bluespice.com/bluespice-qa/wiki:latest
			volumes:
			- ${CODEDIR}:/app/bluespice/w/

	services:		services:

	wiki-installer:		wiki-installer:
	~~image~~: ~~docker.bluespice.com/bluespice~~-~~qa/wiki:latest~~		<<: *x-common
	~~volumes:~~
	~~- ${CODEDIR}:/app/bluespice/w/~~

	wiki-web:		wiki-web:
	~~image~~: ~~docker.bluespice.com/bluespice~~-~~qa/wiki:latest~~		<<: *x-common
	~~volumes:~~		restart: no
	~~- ${CODEDIR}~~:~~/app/bluespice/w/~~

	wiki-task:		wiki-task:
	~~image~~: ~~docker.bluespice.com/bluespice~~-~~qa/wiki:latest~~		<<: *x-common
	~~volumes:~~		restart: no
	~~- ${CODEDIR}~~:~~/app/bluespice/w/~~

	mailhog:		mailhog:
	image: mailhog/mailhog		image: mailhog/mailhog
	container_name: mailhog		container_name: ${COMPOSE_PROJECT_NAME:-bluespice}-mailhog
	environment:		environment:
	VIRTUAL_HOST: ${WIKI_HOST}		VIRTUAL_HOST: ${WIKI_HOST}
	VIRTUAL_PATH: /_mailhog		VIRTUAL_PATH: /_mailhog/
	VIRTUAL_PORT: 8025		VIRTUAL_PORT: 8025
	VIRTUAL_DEST: /		VIRTUAL_DEST: /
			restart: no

			cache:
			restart: no

			collabpads:
			restart: no

			collabpads-database:
			restart: no

			database:
			restart: no

			diagram:
			restart: no

			formula:
			restart: no

			pdf:
			restart: no

			proxy:
			restart: no

			search:
			restart: no

			wire:
			restart: no
	</syntaxhighlight>		</syntaxhighlight>

Manual:Extension/BlueSpiceTranslationTransfer

Margit.link-rodrigue — Mon, 16 Mar 2026 15:28:55 GMT

← Older revision		Revision as of 15:28, 16 March 2026
(One intermediate revision by the same user not shown)
Line 20:		Line 20:

	=== Matching path and content language ===		=== Matching path and content language ===
	When creating a wiki instance, you must ensure that both the path and the content language match the ISO language code. Otherwise, the instance will not be recognized as a language wiki. Subsequent reconfiguration of wikis that already contain content can be difficult, as some terms are language-specific (e.g., the syntax of image attributes).		When creating a wiki instance, you must ensure that both the path and the content language match the ISO language code. Otherwise, the instance will not be recognized as a language wiki. The site name can be freely chosen, however it is recommended to consistently use the language code here as well. Subsequent reconfiguration of wikis that already contain content can be difficult, as some terms are language-specific (e.g., the syntax of image attributes).
	[[File:Wiki farm - create language instance.png\|alt=Dialog box for creating an English language instance in Wikifarm\|center\|thumb\|450x450px\|Dialog window for creating a new language instance with path name (1) and matching content language (2) in an English root wiki.]]		[[File:Wiki farm - create language instance.png\|alt=Dialog box for creating an English language instance in Wikifarm\|center\|thumb\|450x450px\|Dialog window for creating a new language instance with site name (1), path name (2) and matching content language (3) in an English root wiki.]]
	The relationship between the instances of a wiki farm with regard to translation can therefore be visualized as follows:<drawio filename="translation_wikis" alt="Diagram showing a root wiki and four other wikis in the same farm">		The relationship between the instances of a wiki farm with regard to translation can therefore be visualized as follows:<drawio filename="translation_wikis" alt="Diagram showing a root wiki and four other wikis in the same farm">

File:Wiki farm - create language instance.png

Margit.link-rodrigue — Mon, 16 Mar 2026 15:22:39 GMT

Redaktion uploaded a new version of File:Wiki farm - create language instance.png

New page

File:Wiki farm - create language instance.png

Margit.link-rodrigue — Mon, 16 Mar 2026 15:15:34 GMT

Redaktion uploaded a new version of File:Wiki farm - create language instance.png

New page

File:translation wikis.png

Margit.link-rodrigue — Mon, 16 Mar 2026 15:09:51 GMT

Redaktion uploaded a new version of File:translation wikis.png DrawioEditor

New page

Manual:Extension/BlueSpiceTranslationTransfer

Margit.link-rodrigue — Mon, 16 Mar 2026 15:08:48 GMT

← Older revision		Revision as of 15:08, 16 March 2026
Line 1:		Line 1:
	{{DISPLAYTITLE:Translations in a Wiki farm (TranslationTransfer)}}		The translation mechanism in a Wiki farm is controlled via the '''BlueSpiceTranslationTransfer''' extension.{{DISPLAYTITLE:Translations in a Wiki farm (TranslationTransfer)}}

	{{Textbox\|boxtype=important\|header=DeepL API key required:\|text=This feature requires a valid DeepL API key, which is not provided by BlueSpice. The key is entered in the [[Manual:Extension/BlueSpiceConfigManager#BlueSpiceTranslationTransfer_(farm)\|Config manager of the translation source wiki]].\|icon=yes}}		{{Textbox\|boxtype=important\|header=DeepL API key required:\|text=This feature requires a valid DeepL API key, which is not provided by BlueSpice. The key is entered in the [[Manual:Extension/BlueSpiceConfigManager#BlueSpiceTranslationTransfer_(farm)\|Config manager of the translation source wiki]].\|icon=yes}}
Line 14:		Line 14:
	The page tools of the wiki pages therefore automatically displays a translation link, even if no DeepL API key has been entered.		The page tools of the wiki pages therefore automatically displays a translation link, even if no DeepL API key has been entered.

	==== Creating the target wikis ====		=== Creating the target wikis ===
	Language wikis are always created with their [[wikipedia:ISO_639-1\|two-letter ISO 639-1 language code]] (e.g., DE for the German language instance, FR for the French one). During translation, any translation instance supported by the DeepL translation service can be created.		Language wikis are always created with their [[wikipedia:ISO_639-1\|two-letter ISO 639-1 language code]] (e.g., DE for the German language instance, FR for the French one). During translation, any translation instance supported by the DeepL translation service can be created.

	This also means that a wiki instance named IT is automatically recognized as a language wiki. An instance must then be created for the IT department that does not correspond to the language code for Italian (e.g., IT-Wiki).		This also means that a wiki instance named IT is automatically recognized as a language wiki. An instance must then be created for the IT department that does not correspond to the language code for Italian (e.g., IT-Wiki).

	If a wiki ~~farm requires a different setup~~, the ~~server configuration must~~ be ~~adjusted accordingly by~~ a ~~server administrator~~ (~~only possible~~ for ~~on-premises installations~~).		=== Matching path and content language ===
			When creating a wiki instance, you must ensure that both the path and the content language match the ISO language code. Otherwise, the instance will not be recognized as a language wiki. Subsequent reconfiguration of wikis that already contain content can be difficult, as some terms are language-specific (e.g., the syntax of image attributes).
	<drawio filename="translation_wikis" alt="Diagram showing a root wiki and four other wikis in the same farm">		[[File:Wiki farm - create language instance.png\|alt=Dialog box for creating an English language instance in Wikifarm\|center\|thumb\|450x450px\|Dialog window for creating a new language instance with path name (1) and matching content language (2) in an English root wiki.]]
			The relationship between the instances of a wiki farm with regard to translation can therefore be visualized as follows:<drawio filename="translation_wikis" alt="Diagram showing a root wiki and four other wikis in the same farm">

	</drawio>		</drawio>

			If a wiki farm requires a different setup, the server configuration must be adjusted accordingly by a server administrator (only possible for on-premises installations).

	== Translation of a page ==		== Translation of a page ==

File:Wiki farm - create language instance.png

Margit.link-rodrigue — Mon, 16 Mar 2026 15:03:25 GMT

Redaktion uploaded File:Wiki farm - create language instance.png

New page