wbb Update: WoltLab Suite 5.4.6 / 5.3.13 / 5.2.15 / 3.1.23

[Guest Alexander Ebert]

We have just released new versions of our products:

 

• WoltLab Suite 5.4.6
  
• WoltLab Suite 5.3.13
  
• WoltLab Suite 5.2.15
  
• WoltLab Suite 3.1.23
  

 

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.

 

How to Apply 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 Calendar

 

• Creating a menu link to the list of a user's events erroneously did not require entering a user ID. 5.2
  
• Required input fields in inactive categories no longer block submitting the form for events. 5.4
  

WoltLab Suite Filebase

 

• Inactive form elements no longer block form submission. 5.3
  
• Moving selected files to the trash bin properly removes the selection afterwards. 5.2 3.1
  

WoltLab Suite Forum

 

• Some actions in the dropdown for marked topics, such as moving, were without function within a thread. 5.4
  
• Errors in determining the similar threads, for example if the search index is broken, no longer lead to an error message when submitting a thread. 5.4
  
• The hover text of the done marker is now updated correctly when the status is changed. 5.3
  
• A calculation error when loading new posts at the bottom of the page was fixed. 5.3
  
• Displaying advertisements when accessing a deleted thread no longer results in an error message. 5.3
  
• After creating a new forum, checkboxes in the form are correctly reset to default value. 5.2
  
• The canonical URLs of the first page of a forum were corrected. 5.2
  

WoltLab Suite Gallery

 

• Albums without content are no longer part of the sitemap. 5.2 3.1
  

WoltLab Suite Core: Elasticsearch

 

• Elasticsearch server version check no longer results in error messages when an HTTP server responds but it is not an Elasticsearch server. 5.4
  
• The creation of the search index for plugins with capital letters in the internal identifier has been fixed. 5.3
  
• A problem with selecting other sorting criteria was fixed. 5.2
  

WoltLab Suite Core

 

• Updating users now removes database entries of title images that no longer exist in the file system. 5.4
  
• Guest messages now correctly show Guest as user name in moderation. 5.4
  
• Recent activities now show article labels. 5.4
  
• "Mark all articles as read" now also removes the red number from the submenus of the main menu. 5.4
  
• Editing styles could sometimes leave an empty language variable in the system, which would cause the style description to be displayed in various places. This is now prevented and the erroneous language variable is deleted. 5.4
  
• The style import now downloads Google Fonts correctly. 5.4 5.3
  
• The user experience of logging into the administration interface has been improved by making the web browser input fields mandatory. 5.4
  
• A localized page title is now correctly stored in the QR code for setting up multi-factor authentication with smartphone app ("TOTP"). 5.4
  
• Support for Unicode characters ("umlauts") in smiley titles has been fixed. 5.4
  
• About 2% of generated session IDs could not be read correctly from the cookie on the next request. This issue could result in a user not being logged in correctly despite a success message when logging in, if the user received an affected session ID for the user change. 5.4
  
• Cookies get the SameSite=none attribute when embedding in frames is allowed, to ensure functionality. 5.4
  
• The list of users to activate when activated by the administrator no longer lists banned users. 5.4
  
• Editing the landing page in the app management did not become active immediately. 5.4
  
• In links containing a @ a mention could be detected incorrectly, breaking the link. 5.4
  
• When editing main menu items, it is now correctly checked that a menu item itself cannot be its parent menu item. 5.4
  
• A display error of the title line of code boxes when the editor is active has been corrected. 5.4
  
• The drop-down menus for editing messages were sometimes placed incorrectly. 5.4
  
• The preview of an empty editor does not send server requests now. 5.3
  
• Deletion of reaction images when deleting a reaction was fixed. 5.3 5.2
  
• An error in processing {foreach} in the template was corrected. 5.3
  
• Smiley titles with a " no longer lead to invalid HTML output. 5.3 5.2 3.1
  
• When reloading comment responses, the counter was not updated. 5.2 3.1
  
• Sitemaps were generated incorrectly in rare cases. 5.2 3.1
  
• Articles in disabled categories are no longer accessible. 5.2 3.1
  
• Filtering and sorting of articles is preserved when changing pages. 5.2
  
• Deactivated comments were not removed from moderation during deletion. 5.2 3.1
  
• Search and Last activities contained an outdated date when automatically activating articles. 5.2
  
• For developers: The TypeScript module WoltLabSuite/Core/Ui/Object/Action/Toogle has been renamed to WoltLabSuite/Core/Ui/Object/Action/Toggle. The old name is still available for compatibility, but should no longer be used. 5.4
  
• For developers: There is a new class AbstractFormFieldDecorator. 5.4
  
• For developers: fixed support for arbitrary error types on input fields in various forms. 5.4 5.3 5.2
  
• For developers: isAvailable() for IFormButton objects is now checked correctly and buttons are hidden if necessary. 5.4 5.3 5.2
  
• For developers: The PHP-based DDL API could sometimes reject valid changes as invalid. 5.4
  
• For developers: The UserFormField no longer returns errors if the corresponding field is completely missing from the request data. 5.4 5.3 5.2
  
• For developers: The PHP-based DDL API may not have implemented database changes or may have done so incorrectly. 5.3 5.2
  
• For developers: The LabelFormField now considers dependencies correctly and does not provide values if the dependencies are not met. 5.3 5.2
  
• For developers: Various fixes to FormBuilder and dev tools. 5.2
  

 

Continue reading...