Posts by Alexander Ebert

    We have just released new versions of our products:

    • WoltLab Suite 5.2.1

    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.

    Performing 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 search for items matching one or more tags could raise an error under certain circumstances.

    WoltLab Suite Calendar

    • The list of user events raised an exception if no user id was provided.
    • The year view incorrectly defaulted to 2019 rather than the current year.
    • Invalid date ranges will no longer cause an error in the event overlap check.
    • Repeated events were affected by an incorrect calculation of the end date.
    • The search for items matching one or more tags could raise an error under certain circumstances.

    WoltLab Suite Filebase

    • An incorrect number of purchased quantities was reported to customers of a file.
    • Approving a file attempted to remove non existent items in the moderation queue.
    • Rebuilding files and versions failed due to a pending query cursor.
    • The search for items matching one or more tags could raise an error under certain circumstances.

    WoltLab Suite Gallery

    • Albums did not use the new masonry layout.
    • The search for items matching one or more tags could raise an error under certain circumstances.

    WoltLab Suite Forum

    • Disallowing attachments for users caused an incorrect validation error.
    • The search for items matching one or more tags could raise an error under certain circumstances.

    WoltLab Suite Core

    • An implicit limit caused the list of received reactions to be cut off.
    • The link recognition in messages performed incorrect operations on the message.
    • Captions for media items used as article images did not support HTML.
    • The teaser image of articles had not been used on the article list.
    • Removed an unintentional gap after a user was mentioned in a message.
    • Improved the upgrade process from WoltLab Suite 3.1, all steps during the Core upgrade are now idempotent.
    • The owner group now has always access to all user groups as intended.
    • MySQL 8 suffered from a serious bug that caused incorrect reports of the key definitions. For MySQL 8 only, we'll now require MySQL 8.0.14 or newer.
    • The search for items matching one or more tags could raise an error under certain circumstances.

    This is by design, there is (for whatever reasons) a technical difference between those two types, in particular if another language is added afterwards. Since both types are fully functional in an environment with only a single language, there is nothing to do at this point.


    The caching is enforced via a HTTP header set by the webserver itself. You can either set headers with a short cache duration for the particular file, for example, via .htaccess, or use different filenames for each header image.

    If you're using the same images but rotate them regularly, I would recommend to use distinctive file name. You would achieve both an instantaneous update of the displayed image while still making use of the browser cache to reduce traffic for both you and your users.

    Is this a paid upgrade and if so, what is the cost? Or is it free to existing 3.1 users?

    This is a paid upgrade. However, starting with WoltLab Suite 5.2 each license, including those upgraded from Burning Board 4.0 or newer, will receive all new versions that are released within one year. Please see Sales Launch and Pricings of WoltLab Suite 5.2 to learn more.

    I'm sure I saw that Link Preview is part of the new 5.2 forum, although I may be mistaken.

    There had been plans at one point, but these have been postponed for now due to legal concerns, in particular in regards to the EU Directive 2019/790 (Directive on Copyright in the Digital Single Market), which is still pending to be implemented by the member states.

    Is it best to update all the plugins first prior to upgrading, assuming that they are all compatible? Or just select all updates and hit submit?

    Some updates do not require 5.2, so these can and should be installed first. The easiest way to do this is to disable those update servers for 2019 and run the update, once there is nothing left, proceed with the upgrade. The upgrade requires all available updates to be selected, because they need to be applied in the same process.

    Would a database back up and full home directory back up from within CPanel be sufficient in case they are needed? That's where I usually do my back ups anyway.

    This should be fine.

    The procedure below describes an upgrade from WoltLab Suite 3.1.x only. If you would like to upgrade from an earlier version, please see our help guides to learn more.

    Step 1: Enable maintenance mode

    The maintenance mode disables the forums and most other features (including cronjobs) to preserve data consistency. We understand that putting a live forum into maintenance mode is unpleasant, but failing to do so will most likely cause data inconsistency and might even cause the upgrade to fail.

    Step 2: Create a backup

    You should always create a backup before applying any updates, but upgrading is a much more complicated and irreversible process. If for any reason the process fails before completion, your installation is most likely irreparably damaged and cannot be recovered, except for restoring it from a backup.

    A full backup consists of two parts:

    1. Full database dump
      We recommend using mysqldump (if you have access to the command line) or the free PhpMyAdmin.
    2. Full copy of the forum files
      Create a copy of all files belonging to the software and its components, including all user-generated data, e.g. attachments

    Avoid mixing database dumps with file copies originating from a different point of time, it will most likely not work or cause serve damage to your forums.

    Step 3: (Optional) Increase PHP and/or database timeouts if possible

    The upgrade process will make changes to some key tables, including the user table and message-related tables, e.g. for posts or conversation messages. Depending on the size of your forum, this can take quite some time to complete and running into a timeout will break the entire upgrade. Please make temporary adjustments to these timeouts at your own discretion.

    Step 4: Update your Installation

    Please run a full update through ACP > System > Packages > List Packages and click on the button Search for Updates. You must run the latest versions in order to perform an upgrade, earlier versions are not supported.

    Step 5: Add the update servers

    1. Navigate to ACP > System > Packages > List Update Servers
    2. Click on the button Add Server
    3. Insert into the field Address and leave all other fields empty
    4. Click the Submit button to add the new Server
    5. Insert into the field Address and leave all other fields empty
    6. Click the Submit button to add the new Server

    Step 6: Perform the update

    Please navigate to ACP > System > Packages > List Packages and click on the button Search for Updates. The system should redirect you to a new page offering WoltLab Suite 3 and maybe other products.

    Step 7: Rebuild all data

    Some changes require you to rebuild data, it is recommended to run all steps listed in ACP > Management > Rebuild Data once the update has completed.

    We're pleased to announce the release of the WoltLab Suite 5.2, consisting of the powerful Core package and our 5 modular apps that enrich your site and community.

    This version puts great emphasis on consistency and backwards-compatibility, evolving existing features to match the on-going development in expectations and adding more features that tightly integrate into existing sites. We've spend quite a lot of time evaluating every single feature in our software suite, eventually making a lot of small and large changes to both improve your users' experience and to make it easier for you to manage your community. We truly believe that a community is a living thing that is constantly evolving and so should the software, the very foundation of your community.

    We have also made a slight change to the version numbers, all products now share the same version number 5.2.

    We were really amazed by the large amount of people that have actively participated in the beta test and supported us with their observations and suggestions, enabling us to build a truly amazing software for your community. Thank you!

    Introducing WoltLab Suite 5.2, the next big step in the history of community and forum solutions and successor of the previous WoltLab Suite 3 series.

    System Requirements

    WoltLab Suite 5.2 requires the following prerequisites to install and run the software:

    • Webserver with PHP 7.0.22 or newer (PHP 7.4+ recommended)
    • MySQL 5.5.35 (or newer) / MariaDB 5.5.47 (or newer) / MariaDB 10.0.22 (or newer)
    • 20 MB free disk space
    • Current Webbrowser (Chrome 76+, Firefox 68+, Safari 12+, Microsoft Edge 44+ [EdgeHTML 18+])

    Installation Guide

    1. Download the installation archive onto your computer.
    2. Extract the archive.
    3. Upload the files install.php, test.php and WCFSetup.tar.gz onto your webserver.
    4. Start the installation by navigating with your webbrowser to the test.php.

    Updating from earlier versions

    Upgrading is supported for WoltLab Suite 3.1.11 or newer, the responsible update server needs to be added to the list of update servers. Please keep in mind that we do not gurantee the stability of the upgrade, under no circumstances should you upgrade your installation without creating a full backup before. Upgrade at your own risk!

    Usage and Support

    This evaluation version is not suitable for use in production environments, doing so is entirely at your own risk. An update from WoltLab Suite 5.2 RC 2 to future versions is guaranteed. You may use the apps until February 6th, 2020, if you would like to continue using this software past this date, you'll have obtain a valid product license.

    We're looking forward to hear your feedback and report of possible issues in this forum.

    Version Number Changes

    The forum app historically used a much higher version number, which wasn't ideal at all times. Starting with this release, all our products have been bumped up to version 5.2.

    Compatibility with PHP 7.4

    This version is compatible with PHP 7.4.

    Download WoltLab Suite Forum 5.2 RC 2

    Download WoltLab Suite Blog 5.2 RC 2

    Download WoltLab Suite Calendar 5.2 RC 2

    Download WoltLab Suite Gallery 5.2 RC 2

    Download WoltLab Suite Filebase 5.2 RC 2

    The only proper way is too adjust everything that you want to be scaled down, like reducing the font size, paddings, margins, etc. "Zoom" is basically like using a scrap press to make your car a bit smaller. It works, but the result is a constant source of strange artifacts and rounding errors.

    The style author uses a different approach, but this additional (!) rule should do the job.

    @include screen-lg {
        .pageContainer {
            min-width: auto;
            max-width: none;
            width: 80%;

    I wouldn't recommend to zoom the site, the results are overall pretty poor and the aforementioned anti aliasing decreases the legibility of the site. Just looking at the menu buttons, that text is anything but sharp. This also means that image quality decreases and longer messages become harder to read.

    I can see the motivation behind your approach, but I don't think that it outweights the drawbacks from a user's perspective.

    Why would you even zoom the entire site, this introduces a lot of scaling issues including fuzzy text and other sorts of artifacts as a side effect of anti aliasing attempts? Are you just trying to reduce the width?


    This isn't the proper way to approach this, especially not with zoom which has so many strange effects. Just edit the style, set it to like 80% width and you're done, you don't need this strange and horribly outdated code

    Disclaimer: The custom style may have different settings applied that could interfere with this, when in doubt ask the style creator for help.


    The backup was not restored properly, some parts of the new version are still there. These white boxes are actually buttons that are missing some styles. Maybe this is just an issue with outdated caches, you can try to reset the cache via Maintenance > Cache.