wbb Update: WoltLab Suite 6.0.5

[Guest Alexander Ebert]

We have just released new versions of our products:

 

• WoltLab Suite 6.0.5
  

 

Stability releases (third part of the version number, also known as “patch 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.

 

[HEADING=1]How to Apply Updates[/HEADING]

 

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.

 

[HEADING=1]Notable Changes[/HEADING]

 

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

 

[HEADING=2]WoltLab Suite Filebase[/HEADING]

• In the file preview, the icon was positioned too far to the left and visually cut off. 6.0
  

[HEADING=2]WoltLab Suite Forum[/HEADING]

• The icons for the sorting order of the topic list were swapped. 6.0
  

[HEADING=2]WoltLab Suite Core: Elasticsearch[/HEADING]

• The timeout for waiting for a response from the bulk API has been increased from 15 to 60 seconds when using our CLI API. 6.0
  

[HEADING=2]WoltLab Suite Core: Importer[/HEADING]

• WoltLab Suite 5.x/6.x
  
  • Fixed a bug that prevented the export of blog entries and calendar events. 6.0
    

[HEADING=2]WoltLab Suite Core[/HEADING]

• Invalid e-mail addresses no longer generate an error message on the list of users. 6.0
  
• Closing a dialog window with the Esc key now triggers the cancel event. 6.0
  
• A specific type of error message was displayed incorrectly inside dialogs. 6.0
  
• The edit buttons of media on a smartphone using the light color scheme were incorrectly colorized. 6.0
  
• Fixed a bug when exporting user data in combination with WoltLab Suite Filebase. 6.0
  
• Embedding audio and video files using the media system caused an error. 6.0
  
• An embedded image at the beginning of the text, which flows around the text, caused an incorrect vertical spacing of the following text. 6.0
  

 

Continue reading...