Update: WoltLab Suite 5.2.7 / 3.1.15 / 3.0.25

We have just released new versions of our products:

• WoltLab Suite 5.2.7
• WoltLab Suite 3.1.15
• WoltLab Suite 3.0.25

Stability releases (also known as "minor releases") aim to solve existing problems in the current version. Like every stability release, they do not introduce new features; It is strongly recommended to apply these updates.

Applying System Updates

Open your Administration Control Panel and navigate to Configuration > Packages > List Packages. Please click on the button Search for Updates located in the right corner above the package list.

Notable Changes

The list below includes only significant changes, minor fixes or typos are generally left out.

WoltLab Suite Blog

• The link to show more blogs in the user profile was broken. 3.1

WoltLab Suite Calendar

• Inconsistent use of the icon to share an event. 5.2

WoltLab Suite Filebase

• The [file] bbcode is now properly recognized as a block level element. 3.1 5.2

WoltLab Suite Forum

• Incorrect encoding of object names in conditions. 5.0 5.1 5.2
• Restoring the only post of a thread caused incorrect counter updates. 5.1 5.2
• The restrictions on the minimum length and word count of threads was not applied correctly. 5.1 5.2
• External links had not been excluded from the sitemap. 5.1 5.2
• Editing a post and inserting quotes did not yield notifications. 5.1 5.2
• Publishing a thread with an updated time did not update the post dates. 5.2

WoltLab Suite Gallery

• The upload button is now hidden if the user is at most allowed to create links to external video sources. 3.1 5.2

WoltLab Suite Core: Konversationen

• Missing phrase in the dialog to edit the subject. 3.1 5.2
• Redundant encoding of special characters in usernames caused recipients failing to validate. 5.2

WoltLab Suite Core: Importer

• WoltLab Burning Board 4.x
  • Custom user profile fields had been imported using incorrect type identifiers. 3.1 5.2

WoltLab Suite Core: Verwarnungen

• Issuing a warning in the user profile did not work previously. 3.1 5.2

WoltLab Suite Core

• Incorrect encoding of object names in conditions. 3.0 3.1 5.2
• Patched jQuery against CVE-2019-11358. 3.0 3.1 5.2
• Exceptions raised in cronjobs are now being forwarded to the global error log. 3.1 5.2
• The notification for expiring paid subscriptions did not properly reflect the number of remaining days. 3.1 5.2
• Resolved conflicts when embedding multiple instances of the comment system on the same page. 3.1 5.2
• The bulk processing for users failed when the conditions matched over 65k users. 3.1 5.2
• Teaser images in articles could sometimes use the wrong translation for the image caption. 3.1 5.2
• Incorrect detection of the large iPad Pro. 5.2
• Legacy attachment bbcodes were incorrectly evaluated, causing them to be converted into thumbnails. 5.2
• Mentions for user groups containing more than one whitespace had not been recognized. 5.2
• Prevent browsers from auto filling in certain password fields in the admin panel. 5.2
• Improved the error reporting for failed SSL/TLS connections. 5.2
• Recreated the Twitch bbcode to comply with their recent API changes. 5.2

Misleading Error Reports for Failed Cronjobs

Some users have reported recurring errors with the message "Cronjob stuck in state 1 for two periods, resetting.". These errors are false positives and are caused by a calculation error of the next execution time of cronjobs, causing them to be flagged as overdue.

This update will resolve this error, however, errors ocurring until the update is applied can still appear in the error log of the same day.

Notable Changes

WoltLab Suite Core 3.1.16 5.2.8

• Incorrect calculation of cronjob execution times caused false positive error reports. 3.1 5.2
• Pasting an image from clipboard in Chromium based browsers caused a hidden base64 encoded image to be injected. 3.1 5.2
• Resolved an issue that caused the client-side scaling to improperly rotate an image with the EXIF orientation tag. 5.2
• The attempt to revoke a trophy could fail due to a faulty database query. 5.2
• Suppressing fatal errors with @ did not work in PHP 8.0 due to PHP-API changes. 5.2