BlueSpice Helpdesk - Recent changes [en]

Security:Security Advisories

Rvogel1 — Mon, 08 Jun 2026 09:06:59 GMT

← Older revision		Revision as of 09:06, 8 June 2026
Line 6:		Line 6:
	! style="" \|Summary		! style="" \|Summary
	!Severity		!Severity
			\|-
			\|[[Security:Security Advisories/BSSA-2026-03\|BSSA-2026-03]]
			\|2026-06-08
			\|Security vulnerabilities in containers of the Cloudogu stack
			\|[https://nvd.nist.gov/vuln/detail/CVE-2026-31789 CVE-2026-31789], [https://nvd.nist.gov/vuln/detail/CVE-2026-43512 CVE-2026-43512], [https://nvd.nist.gov/vuln/detail/CVE-2026-7261 CVE-2026-7261]
			\|Heap buffer overflow in OpenSSL, Apache Tomcat DIGEST authentication bypass and PHP SOAP server session persistence vulnerability
			\| style="" class="col-green-bg" \|Low
	\|-		\|-
	\|[[Security:Security Advisories/BSSA-2026-02\|BSSA-2026-02]]		\|[[Security:Security Advisories/BSSA-2026-02\|BSSA-2026-02]]

Security:Security Advisories/BSSA-2026-03

Rvogel1 — Mon, 08 Jun 2026 09:02:50 GMT

← Older revision		Revision as of 09:02, 8 June 2026
Line 21:		Line 21:
	* [https://nvd.nist.gov/vuln/detail/CVE-2026-43512 CVE-2026-43512]		* [https://nvd.nist.gov/vuln/detail/CVE-2026-43512 CVE-2026-43512]
	* [https://nvd.nist.gov/vuln/detail/CVE-2026-7261 CVE-2026-7261]		* [https://nvd.nist.gov/vuln/detail/CVE-2026-7261 CVE-2026-7261]
	\|-
	~~\|Validated by~~
	~~\|RV, FS~~
	\|}		\|}

Line 32:		Line 29:
	!'''Type of vulnerability'''		!'''Type of vulnerability'''
	!'''BlueSpice 5'''		!'''BlueSpice 5'''
	~~!'''BlueSpice 4'''~~
	\|-		\|-
	\|CVE-2026-31789		\|CVE-2026-31789
	\|<code>hallowelt/bluespice-mathoid</code>, <code>hallowelt/bluespice-collabpadsbackend</code>, <code>hallowelt/mongodb</code>		\|<code>hallowelt/bluespice-mathoid</code>, <code>hallowelt/bluespice-collabpadsbackend</code>, <code>hallowelt/mongodb</code>
	\|Heap Buffer Overflow (OpenSSL, 32-bit only)		\|Heap Buffer Overflow (OpenSSL, 32-bit only)
	~~\| style="" class="col-green-bg" \|not affected~~
	\| style="" class="col-green-bg" \|not affected		\| style="" class="col-green-bg" \|not affected
	\|-		\|-
Line 43:		Line 38:
	\|<code>hallowelt/bluespice-pdfrenderer</code>, <code>hallowelt/drawio</code>		\|<code>hallowelt/bluespice-pdfrenderer</code>, <code>hallowelt/drawio</code>
	\|Authentication Bypass (Apache Tomcat DIGEST)		\|Authentication Bypass (Apache Tomcat DIGEST)
	~~\| style="" class="col-green-bg" \|not affected~~
	\| style="" class="col-green-bg" \|not affected		\| style="" class="col-green-bg" \|not affected
	\|-		\|-
Line 49:		Line 43:
	\|<code>hallowelt/bluespice</code>		\|<code>hallowelt/bluespice</code>
	\|PHP SOAP Server Session Persistence		\|PHP SOAP Server Session Persistence
	~~\| style="" class="col-green-bg" \|not affected~~
	\| style="" class="col-green-bg" \|not affected		\| style="" class="col-green-bg" \|not affected
	\|}		\|}

Security:Security Advisories/BSSA-2026-03

Rvogel1 — Mon, 08 Jun 2026 09:00:07 GMT

Created page with "{| class="wikitable" |+ ! ! |- |Date |2026-06-08 |- |Severity |reported "medium/high", BlueSpice assessment: '''not affected''' |- |Affected |Cloudogu Container Images (library present, not exploitable) |- |Fixed in |Next regular update |- |CVE | * [https://nvd.nist.gov/vuln/detail/CVE-2026-31789 CVE-2026-31789] * [https://nvd.nist.gov/vuln/detail/CVE-2026-43512 CVE-2026-43512] * [https://nvd.nist.gov/vuln/detail/CVE-2026-7261 CVE-2026-7261] |- |Validated by |RV, FS |}..."

New page

{| class="wikitable"
|+
!
!
|-
|Date
|2026-06-08
|-
|Severity
|reported "medium/high", BlueSpice assessment: '''not affected'''
|-
|Affected
|Cloudogu Container Images (library present, not exploitable)
|-
|Fixed in
|Next regular update
|-
|CVE
|
* [https://nvd.nist.gov/vuln/detail/CVE-2026-31789 CVE-2026-31789]
* [https://nvd.nist.gov/vuln/detail/CVE-2026-43512 CVE-2026-43512]
* [https://nvd.nist.gov/vuln/detail/CVE-2026-7261 CVE-2026-7261]
|-
|Validated by
|RV, FS
|}

==Problem==
{| class="wikitable"
!'''CVE'''
!'''Component'''
!'''Type of vulnerability'''
!'''BlueSpice 5'''
!'''BlueSpice 4'''
|-
|CVE-2026-31789
|<code>hallowelt/bluespice-mathoid</code>, <code>hallowelt/bluespice-collabpadsbackend</code>, <code>hallowelt/mongodb</code>
|Heap Buffer Overflow (OpenSSL, 32-bit only)
| style="" class="col-green-bg" |not affected
| style="" class="col-green-bg" |not affected
|-
|CVE-2026-43512
|<code>hallowelt/bluespice-pdfrenderer</code>, <code>hallowelt/drawio</code>
|Authentication Bypass (Apache Tomcat DIGEST)
| style="" class="col-green-bg" |not affected
| style="" class="col-green-bg" |not affected
|-
|CVE-2026-7261
|<code>hallowelt/bluespice</code>
|PHP SOAP Server Session Persistence
| style="" class="col-green-bg" |not affected
| style="" class="col-green-bg" |not affected
|}

==Impact assessment==
{| class="wikitable" style="width: 100%;"
!CVE
!Assessment
!Mitigation without update
|-
| style="vertical-align:middle;text-align:left;" |CVE-2026-31789
| style="vertical-align:middle;text-align:left;" class="col-green-bg" |Not affected. The vulnerability only applies to 32-bit platforms. Additionally, the way OpenSSL is used in the affected container images does not expose any exploitable attack surface.
| style="vertical-align:middle;text-align:left;" |No action required.
|-
| style="vertical-align:middle;text-align:left;" |CVE-2026-43512
| style="vertical-align:middle;text-align:left;" class="col-green-bg" |Not affected. Neither <code>bluespice-pdfrenderer</code> nor <code>drawio</code> use DIGEST authentication. Access to both services is anonymous by design.
| style="vertical-align:middle;text-align:left;" |No action required.
|-
| style="vertical-align:middle;text-align:left;" |CVE-2026-7261
| style="vertical-align:middle;text-align:left;" class="col-green-bg" |Not affected. BlueSpice does not use a PHP SOAP server, and the affected <code>SOAP_PERSISTENCE_SESSION</code> setting is not in use.
| style="vertical-align:middle;text-align:left;" |No action required.
|}

== Solution ==
No immediate action required. The affected libraries will be updated in the next regular release.

Manual:Extension/Forms/5.1.8

Bhuber — Wed, 03 Jun 2026 13:07:24 GMT

← Older revision		Revision as of 13:07, 3 June 2026
Line 43:		Line 43:
	*'''Target type:''' Email		*'''Target type:''' Email
	*'''Recipient:''' Possible recipients must have been configured on the server for security reasons. Example:		*'''Recipient:''' Possible recipients must have been configured on the server for security reasons. Example:
	<syntaxhighlight lang="~~text~~">		<syntaxhighlight lang="php" line="1">
	$wgFormsTargetEMailRecipients = [		$wgFormsTargetEMailRecipients = [
			'Marketing' => "marketing@example.com",
	'Marketing' => "marketing@example.com",		'Administration' => 'WikiSysop'

	'Administration' => 'WikiSysop'

	];		];
	</syntaxhighlight>		</syntaxhighlight>
Line 58:		Line 55:


	[[mediawikiwiki:Help:Magic_words#Localisation\|Localization messages]] in combination with form fields can also be used as subject or email body:<syntaxhighlight lang="~~text~~">		[[mediawikiwiki:Help:Magic_words#Localisation\|Localization messages]] in combination with form fields can also be used as subject or email body:<syntaxhighlight lang="wikitext" line="1">
	{{int:Mailsubject\| {{{name}}}\|{{{surname}}} }}		{{int:Mailsubject\| {{{name}}}\|{{{surname}}} }}
	</syntaxhighlight>		</syntaxhighlight>

Manual:Extension/Forms

Bhuber — Wed, 03 Jun 2026 12:21:21 GMT

← Older revision		Revision as of 12:21, 3 June 2026
Line 46:		Line 46:
	*'''Target type:''' Email		*'''Target type:''' Email
	*'''Recipient:''' Possible recipients must have been configured on the server for security reasons. Example:		*'''Recipient:''' Possible recipients must have been configured on the server for security reasons. Example:
	<syntaxhighlight lang="~~text~~">		<syntaxhighlight lang="php">
	$wgFormsTargetEMailRecipients = [		$wgFormsTargetEMailRecipients = [
			'Marketing' => "marketing@example.com",
	'Marketing' => "marketing@example.com",		'Administration' => 'WikiSysop'

	'Administration' => 'WikiSysop'

	];		];
	</syntaxhighlight>		</syntaxhighlight>

Manual:Extension/Forms/Form elements and settings

Bhuber — Tue, 02 Jun 2026 07:42:47 GMT

Show changes

Manual:Extension/Forms/5.1.8

Bhuber — Mon, 01 Jun 2026 14:39:31 GMT

← Older revision		Revision as of 14:39, 1 June 2026
Line 66:		Line 66:
	Instead of creating a standard wiki page or sending the form content via E-Mail, a [[Manual:Templates\|Template]] can be used as the target for a form. In this case, the submitted form data is used to create a new wiki page based on an existing template structure, and form values are inserted into the template placeholders.		Instead of creating a standard wiki page or sending the form content via E-Mail, a [[Manual:Templates\|Template]] can be used as the target for a form. In this case, the submitted form data is used to create a new wiki page based on an existing template structure, and form values are inserted into the template placeholders.
	*'''Prerequisites''': Before a Template target can be used, a corresponding template page must already exist in the wiki. The template serves as the structural basis for the generated page. Form fields are mapped to placeholders defined in the template.		*'''Prerequisites''': Before a Template target can be used, a corresponding template page must already exist in the wiki. The template serves as the structural basis for the generated page. Form fields are mapped to placeholders defined in the template.
			[[File:Manual:Template Target.jpg\|alt=selecting Template as target for forms\|center\|thumb\|550x550px\|Template Target]]
	*'''Target type''': Template		*'''Target type''': Template
	*'''Template''': Name of the existing template used for page generation		*'''Template''': Name of the existing template used for page generation
	*'''Predefined title''': optional default title for the newly created page or to predefine a page path (e.g., to create all generated pages as subpages under a specific parent page) <br>		*'''Predefined title''': optional default title for the newly created page or to predefine a page path (e.g., to create all generated pages as subpages under a specific parent page) <br>
	<br>		<br>It is recommended to use identical or clearly related naming for the form and the template to improve maintainability and make configuration dependencies easier to identify. This is typically used to generate standardized, human-readable wiki pages, while JSON-based targets are more commonly used when the output is intended for structured data processing.
	It is recommended to use identical or clearly related naming for the form and the template to improve maintainability and make configuration dependencies easier to identify. This is typically used to generate standardized, human-readable wiki pages, while JSON-based targets are more commonly used when the output is intended for structured data processing.

	==Adjust the styling==		==Adjust the styling==

File:Manual:Template Target.jpg

Bhuber — Mon, 01 Jun 2026 14:38:49 GMT

Bettina Huber uploaded File:Manual:Template Target.jpg

New page

Template Target

Manual:Extension/Forms/5.1.8

Bhuber — Mon, 01 Jun 2026 12:48:17 GMT

← Older revision		Revision as of 12:48, 1 June 2026
(2 intermediate revisions by the same user not shown)
Line 62:		Line 62:
	</syntaxhighlight>		</syntaxhighlight>


			==Alternative Target: Template==
			Instead of creating a standard wiki page or sending the form content via E-Mail, a [[Manual:Templates\|Template]] can be used as the target for a form. In this case, the submitted form data is used to create a new wiki page based on an existing template structure, and form values are inserted into the template placeholders.
			*'''Prerequisites''': Before a Template target can be used, a corresponding template page must already exist in the wiki. The template serves as the structural basis for the generated page. Form fields are mapped to placeholders defined in the template.

			*'''Target type''': Template
			*'''Template''': Name of the existing template used for page generation
			*'''Predefined title''': optional default title for the newly created page or to predefine a page path (e.g., to create all generated pages as subpages under a specific parent page) <br>
			<br>
			It is recommended to use identical or clearly related naming for the form and the template to improve maintainability and make configuration dependencies easier to identify. This is typically used to generate standardized, human-readable wiki pages, while JSON-based targets are more commonly used when the output is intended for structured data processing.

	==Adjust the styling==		==Adjust the styling==

Manual:Extension/Forms/Progress bar

Bhuber — Mon, 01 Jun 2026 09:39:30 GMT

← Older revision		Revision as of 09:39, 1 June 2026
(14 intermediate revisions by the same user not shown)
Line 1:		Line 1:
	The progress bar is ~~useful~~ to ~~count completed~~ checklist ~~items~~, for ~~example~~.		The progress bar shows a calculated progress value based on selected options in a form. In this example, it is applied to a checklist, but it can also be used for other use cases.

	== Adding a progress bar ==		== Adding a progress bar ==
	~~We add~~ a progress bar to a checklist ~~that shows how many tasks habe been completed~~.		This example shows one possible implementation of a progress bar for a checklist.
	[[File:Extension Forms Progress bar example.png\|alt=checklist with two sets of checkbox groups for onboarding tasks\|center\|thumb\|550x550px\|Example of a progress bar for checklist items]]		[[File:Extension Forms Progress bar example.png\|alt=checklist with two sets of checkbox groups for onboarding tasks\|center\|thumb\|550x550px\|Example of a progress bar for checklist items]]
	~~For~~ this, ~~we need to set up~~ the following components:		To recreate this form, the following components are required:

	# '''Provide the logic''' in ''MediaWiki:Common.js''		# '''Provide the JavaScript logic''' in ''MediaWiki:Common.js''
	# '''~~Apply the~~ syntax''' ~~to the checklist items~~		# '''Define''' matching checkbox field and option '''syntax'''
	# '''~~Create~~ an event listener''' in the form properties		# '''Add an event listener''' in the form properties

	=== Provide the logic in ''MediaWiki:Common.js'' ===		=== Provide the logic in ''MediaWiki:Common.js'' ===
	Add the following ~~JavasScript~~ function to ''MediaWiki:Common.js'':<syntaxhighlight lang="javascript" line="1">		Add the following JavaScript function to [https://en.wiki.bluespice.com/wiki/Manual:The_concept_of_namespaces#Namespace_.22MediaWiki.22 ''MediaWiki:Common.js'']:<syntaxhighlight lang="javascript" line="1">
	/Extension:Forms - Add a progress bar for checkbox items /		/Extension:Forms - Add a progress bar for checkbox items /
	function CalcProgress( data ) {		function CalcProgress( data ) {
Line 41:		Line 41:
	</syntaxhighlight>On line 5, you define the prefix for each checkbox that should be included in the progress count:<syntaxhighlight lang="javascript">		</syntaxhighlight>On line 5, you define the prefix for each checkbox that should be included in the progress count:<syntaxhighlight lang="javascript">
	input[value^=check]		input[value^=check]
	</syntaxhighlight>This means that the "data" value for your checkboxes needs to start with "check". ~~You can verify this~~ in ~~the definition source of your~~ form:		</syntaxhighlight>This means that the ''data'' value for your checkboxes needs to start with ''check'' and refers to the ''data'' value defined in each checkbox option:
			[[File:Manual:checkbox data value check.jpg\|thumb\|center\|Data definition in form, here starting with "check-"]]


	On line 14, you define the included fields to only those that have the prefix of "checkbox_multi" in their name.<syntaxhighlight lang="javascript">		On line 14, you define the included fields to only those that have the prefix of ''checkbox_multi''in their name.<syntaxhighlight lang="javascript">
	if ( !name.startsWith( 'checkbox_multi-' ) ) {		if ( !name.startsWith( 'checkbox_multi-' ) ) {
	</syntaxhighlight>		</syntaxhighlight>

			Based on this implementation example, a checkbox option is included in the progress calculation only if the ''field'' name starts with ''checkbox_multi-'' and the option's ''data'' value starts with ''check''.

			If you use different prefixes for your field names or option values, you need to update the JavaScript code accordingly.

	=== Apply the syntax to the checklist items ===		=== Apply the syntax to the checklist items ===
Line 74:		Line 79:

	=== Create an event listener in the form properties ===		=== Create an event listener in the form properties ===
	To connect your form to the JavaScript function, you need to create the listener in the form properties:		To connect your form to the JavaScript function, you need to create the [https://en.wiki.bluespice.com/wiki/Manual:Extension/Forms/Form_elements_and_settings#Listeners listener] in the form properties:
	[[File:Extension Forms Progress bar listener.png\|center\|thumb\|650x650px\|Adding the listener to the form properties]]		[[File:Extension Forms Progress bar listener.png\|center\|thumb\|650x650px\|Adding the listener to the form properties]]
	To add the listener:		To add the listener:
Line 81:		Line 86:
	# '''Click''' on ''Listeners''.		# '''Click''' on ''Listeners''.
	# '''Select''' the event <code>beforeSubmitData</code> and enter the name of your JavaScript function. In our example, it is <code>CalcProgress</code>.		# '''Select''' the event <code>beforeSubmitData</code> and enter the name of your JavaScript function. In our example, it is <code>CalcProgress</code>.
			<br>
			<br>
			The <code>beforeSubmitData</code> event is triggered when the form is saved. As a result, changes to checkbox selections are not reflected immediately while editing. The progress bar is updated only after the form has been saved.<br>

			=== Complete implementation example ===
			This example relies on the JavaScript logic above (especially the required naming conventions). It also defines a page naming pattern in the JSON configuration below. Each checklist is saved as a separate wiki page under the ''ExampleChecklist/'' prefix, using the checklist name as part of the page title.

	~~If you want to test~~ this example, ~~you can~~ save ~~an empty example~~ form (e.g., ''ExampleChecklist.form'') and copy the following into the definition source:<syntaxhighlight lang="json">		To use this example, save a new form (e.g. ''ExampleChecklist.form'') and copy the following configuration into the definition source:<syntaxhighlight lang="json">
	{		{
	"title": "Example Progress Bar",		"title": "Example Progress Bar",

File:Manual:checkbox data value check.jpg

Bhuber — Mon, 01 Jun 2026 07:37:36 GMT

Bettina Huber uploaded File:Manual:checkbox data value check.jpg

New page

visual form editor checkbox data value check

Manual:Extension/Forms/Form elements and settings

Bhuber — Mon, 01 Jun 2026 06:52:39 GMT

← Older revision		Revision as of 06:52, 1 June 2026
Line 226:		Line 226:
	\|		\|
	\|Password strength		\|Password strength
	\|weak:		\|weak: <br>
	medium:		medium: <br>
	strong:		strong:
	\|-		\|-
Line 270:		Line 270:
	\|-		\|-
	\|Enable intermediate saving		\|Enable intermediate saving
	\|form instances show both a <code>Save</code> ~~end~~ a <code>Save & Close</code> button;		\|form instances show both a <code>Save</code> and a <code>Save & Close</code> button;
	the <code>Save</code> button saves the form values and keeps the form in edit-mode.		the <code>Save</code> button saves the form values and keeps the form in edit-mode.
	\|}		\|}

Setup:Installation Guide/Docker

Rvogel1 — Thu, 28 May 2026 06:56:24 GMT

← Older revision		Revision as of 06:56, 28 May 2026
Line 28:		Line 28:

	For example, run:		For example, run:
	<syntaxhighlight lang=sh>		<syntaxhighlight lang="sh">
	wget https://github.com/hallowelt/bluespice-deploy/archive/refs/tags/5.2.3.zip \		wget https://github.com/hallowelt/bluespice-deploy/archive/refs/tags/5.2.4.zip \
	&& unzip 5.2.3.zip \		&& unzip 5.2.4.zip \
	&& cd bluespice-deploy-5.2.3/compose		&& cd bluespice-deploy-5.2.4/compose
	</syntaxhighlight>		</syntaxhighlight>
	{{Textbox\|boxtype=note\|header=Use one consistent version number\|text=The tag number 5.2.3 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}}		{{Textbox\|boxtype=note\|header=Use one consistent version number\|text=The tag number 5.2.3 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}}

Setup:Release Notes

Vhoesl1 — Fri, 22 May 2026 07:17:29 GMT

5.2.4

← Older revision		Revision as of 07:17, 22 May 2026
Line 8:		Line 8:
	{{TOClimit\|limit=1\|notitle=1\|nonum=1\|inline=1}}		{{TOClimit\|limit=1\|notitle=1\|nonum=1\|inline=1}}
	==5.2.4 ==		==5.2.4 ==
	{{#subobject:Release=5\|Releasedate=05/21/2026\|Releasepatch=5.2.4}}Release date: 05/21/2026		{{#subobject:Release=5\|Releasedate=05/26/2026\|Releasepatch=5.2.4}}

			Release date: 05/26/2026
	=== BlueSpice Free ===		=== BlueSpice Free ===
	* '''BlueSpiceDiscovery - The enhanced MediaWiki sidebar does not properly respect the specified permissions''' (ERM47005)		* '''BlueSpiceDiscovery - The enhanced MediaWiki sidebar does not properly respect the specified permissions''' (ERM47005)
Line 74:		Line 76:

	==5.1.8 ==		==5.1.8 ==
	{{#subobject:Release=5\|Releasedate=05/21/2026\|Releasepatch=5.1.8}}Release date: 05/21/2026		{{#subobject:Release=5\|Releasedate=05/26/2026\|Releasepatch=5.1.8}}

			Release date: 05/26/2026
	=== BlueSpice Free ===		=== BlueSpice Free ===
	* '''BlueSpiceDiscovery - The enhanced MediaWiki sidebar does not properly respect the specified permissions''' (ERM47005)		* '''BlueSpiceDiscovery - The enhanced MediaWiki sidebar does not properly respect the specified permissions''' (ERM47005)

Setup:Release History

Vhoesl1 — Fri, 22 May 2026 07:16:40 GMT

← Older revision		Revision as of 07:16, 22 May 2026
Line 18:		Line 18:
	! rowspan="12" \|'''BlueSpice 5'''		! rowspan="12" \|'''BlueSpice 5'''
	\|5.2.4, 5.1.8		\|5.2.4, 5.1.8
	\|05/21/2026		\|05/26/2026
	\|[[Setup:Release Notes#5.2.4\|Release notes 5.2.4]]		\|[[Setup:Release Notes#5.2.4\|Release notes 5.2.4]]
	[[Setup:Release Notes#5.1.8\|Release notes 5.1.8]]		[[Setup:Release Notes#5.1.8\|Release notes 5.1.8]]

Reference:EnhancedStandardUIs

Margit.link-rodrigue — Thu, 21 May 2026 15:04:18 GMT

← Older revision		Revision as of 15:04, 21 May 2026
(4 intermediate revisions by the same user not shown)
Line 7:		Line 7:
	\|compatible=BlueSpice		\|compatible=BlueSpice
	\|category=Skinning		\|category=Skinning
	\|features=The extension provides special pages that replace some standard MediaWiki special pages. ~~Currently the following pages are implemented:~~		\|docu=
			\|features=The extension provides special pages that replace some standard MediaWiki special pages. Additionally, it provides a user-friendly view of the version history of wiki pages.
	* Special:Pages
	* Special:Filelist.

	Additionally, it provides a user-friendly view of the version history of wiki pages.
	}}		}}
	{{wcagCheck}}		{{wcagCheck}}

Template:BSExtensionInfo

Margit.link-rodrigue — Thu, 21 May 2026 14:44:53 GMT

← Older revision		Revision as of 14:44, 21 May 2026
Line 61:		Line 61:
	{{#dpl: title=AutoDoc:{{PAGENAME}}\|include=#Notifications}}\|}}		{{#dpl: title=AutoDoc:{{PAGENAME}}\|include=#Notifications}}\|}}
	</div>		</div>
			[[Category:Extension]]
	[[Category:Extension]]{{Translation}}</includeonly>		{{Translation}}</includeonly>

Reference:BlueSpiceEmoticons

Margit.link-rodrigue — Thu, 21 May 2026 14:44:12 GMT

@@ Line 12: / Line 12: @@
 |desc=Renders emoticons in a text as images.
 }}
 {{wcagCheck
 |wcagStatus=2-testing complete

Manual:Extension/DateTimeTools

Margit.link-rodrigue — Thu, 21 May 2026 10:29:47 GMT

← Older revision		Revision as of 10:29, 21 May 2026
(One intermediate revision by the same user not shown)
Line 1:		Line 1:
	{{~~BSVersion\|bsvFrom=4~~.~~4\|bsvFeature=~~The ~~"Date" Content Droplet}}~~[[File:droplet-date-inspector.png\|alt=Date inspector with Insert-button\|center\|thumb\|350x350px\|~~The~~ "~~Date~~" ~~Content Droplet~~]]		{{DISPLAYTITLE:Insert a date}}
			The Date droplet provides a way to quickly add a formatted dateto a page. The fastest way is to simply use two forward-slashes <code>//</code> as shortcut for opening the date picker widget.[[File:droplet-date-inspector.png\|alt=Date inspector with Insert-button\|center\|thumb\|350x350px\|Date picker]]This inserts the selected date in a badge style with a calendar icon:
			[[File:Manual:BlueSpice Extension DateTimeTools 002.png\|alt=Date with a calendar icon\|center\|thumb\|Inserted date ]]

			== Content droplet ==
			If you forget the shortcut to add a date, you can also find it in the [[Manual:Extension/ContentDroplets\|Content droplets]] menu by filtering for the "date" droplet.

			== Simple tasks ==
			Dates can be used in combination with checklists and user-mentions to [[Manual:Extension/SimpleTasks\|create tasks]].
			{{translation}}

File:Manual:BlueSpice Extension DateTimeTools 002.png

Margit.link-rodrigue — Thu, 21 May 2026 10:23:25 GMT

Editorial Staff uploaded File:Manual:BlueSpice Extension DateTimeTools 002.png

New page

User:Margit.link-rodrigue/Sandbox

Margit.link-rodrigue — Thu, 21 May 2026 09:52:50 GMT

← Older revision		Revision as of 09:52, 21 May 2026
Line 1:		Line 1:
			<datetime>2026-11-27</datetime>


	{{New}}		{{New}}
	#[[File:portalflex-PT-savepage.png\|thumb\|dfsafsadf\|alt=\|center]]		#[[File:portalflex-PT-savepage.png\|thumb\|dfsafsadf\|alt=\|center]]

Setup:Release History

Margit.link-rodrigue — Thu, 21 May 2026 06:52:43 GMT

← Older revision		Revision as of 06:52, 21 May 2026
(2 intermediate revisions by the same user not shown)
Line 1:		Line 1:
	{{#vardefine:latestpatch\|{{#ask: [[-Has subobject::Setup:Release_Notes]]\|?Releasepatch\|mainlabel=-\|format=plainlist\|headers=hide\|limit=1\|searchlabel=\|sort=Releasedate\|order=desc}}}}		{{#vardefine:latestpatch\|{{#ask: [[-Has subobject::Setup:Release_Notes]]\|?Releasepatch\|mainlabel=-\|format=plainlist\|headers=hide\|limit=1\|searchlabel=\|sort=Releasedate\|order=desc}}}}
	{{Featurepage\|featured=true\|featuredesc=Release Notes: {{#var:latestpatch}}, 5.1.~~7 (Security patch)~~\|featurestart=04/22/2026}}{{Textbox\|boxtype=important\|header=Note:\|text=*Support for BlueSpice 4.x ends on July 15, 2026.		{{Featurepage\|featured=true\|featuredesc=Release Notes: <!-- {{#var:latestpatch}} -->5.2.4, 5.1.8\|featurestart=05/21/2026}}{{Textbox\|boxtype=important\|header=Note:\|text=*Support for BlueSpice 4.x ends on July 15, 2026.
	*Support for BlueSpice 3.x ended on March 15, 2023.\|icon=yes}}		*Support for BlueSpice 3.x ended on March 15, 2023.\|icon=yes}}

Line 16:		Line 16:
	! style="" \|Type		! style="" \|Type
	\|-		\|-
	! rowspan="11" \|'''BlueSpice 5'''		! rowspan="12" \|'''BlueSpice 5'''
			\|5.2.4, 5.1.8
			\|05/21/2026
			\|[[Setup:Release Notes#5.2.4\|Release notes 5.2.4]]
			[[Setup:Release Notes#5.1.8\|Release notes 5.1.8]]
			\|Patch release
			\|-
	\|5.2.3, 5.1.7		\|5.2.3, 5.1.7
	\|04/23/2026		\|04/23/2026