Posts by Alexander Ebert

    Edit the user and when the form is returned with an "invisible" error, then please scroll down to the "Powered by WoltLab Suite" text at the very bottom. Right click on it and click on "Inspect element", this fires up the browser's developer tools.


    The button itself doesn't matter, but what you should look for is this block:



    This is an emergency fallback for badly behaving input validation that gives a hint on what is happening. This is always added to the document source whenever a form was rejected.

    We have just released new versions of our products:

    • WoltLab Suite 5.3.2


    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.

    Important Notice

    WoltLab Suite 5.3 ships with an updated library for CSS support in HTML emails to prevent issues when running under PHP 8.0. If you have modified the template email_html, please double check that it is up to date with the current version. In particular please verify that this change has been applied to your customized template: https://github.com/WoltLab/WCF…b4f69714c6259cc5d09ceb344.

    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 "deleted" badge had an incorrect color set to it. 5.3
    • Improved the error handling for the cover photo. 5.3

    WoltLab Suite Calendar

    • Navigating to different year views caused the applied filters to be discarded. 5.3
    • Improved the error handling for the cover photo. 5.3

    WoltLab Suite Filebase

    • Links to files in email notifications had been partially incorrect. 5.3

    WoltLab Suite Gallery

    • The calculation of the number of items in a category list was incorrect. 5.3
    • The preview image was incorrectly displayed when the upload of a video thumbnail has failed. 5.3

    WoltLab Suite Forum

    • Dynamically loading posts from a thread containing a post flagged as "best answer" could fail. 5.3
    • Removing forums did not clean up permissions set up for it, any orphaned data is removed during this update. 5.3

    WoltLab Suite Core: Conversations

    • Removed some references to legacy components that were no longer used. 5.3

    WoltLab Suite Core: Importers

    • vBulletin 3.x/4.x
      • Incorrect check for an installed blog addon. 5.3
    • vBulletin 5
      • Improved the export of images. 5.3
      • Promoted the importer from "experimental" to "supported". 5.3
    • WoltLab Suite 5.x
      • Files imported from the Filebase with mixed multi-lingualism feature caused some duplication errors. 5.3

    WoltLab Suite Core: Moderated User Groups

    • Improved the performance of the list of user groups. 5.3

    WoltLab Suite Core

    • Improved the randomized sort order of related articles. 5.3
    • Increased the default timeout for requests to slow external hosts or if the current host has a low bandwidth. 5.3
    • Package lists distributed from third party package servers could sometimes interfere with the update process. 5.3
    • Administrator were unable to edit styles that use the default preview icon after updating from 5.3.0 to 5.3.1. 5.3
    • Prevent the selection of the quote tooltip on Android devices and improved the overall test selection behavior. 5.3
    • Force the display of a thumbnail if an attachment is embedded in full, but the visitor lacks the permissions to access the full version. 5.3
    • Resizing GIF images in ImageMagick is now significantly faster than before and yields much smaller file sizes. 5.3
    • Improved the PHP-API for database changes via PIPs. 5.3
    • Resolved several issues encountered with the FormBuilder-API. 5.3
    • Upgrading from 5.2 no longer discards the credentials provided for the package servers for 5.3. 5.3
    • Improved the behavior for failed cronjobs to better account for temporary problems. 5.3

    Until the end of the year, we are offering all interested parties the migration of existing forums to our managed hosting offering "WoltLab Cloud" at no additional cost.

    Offer Conditions

    • Ordered between December 1, 2020 through December 31, 2020.
    • The selected plan fits the volume of the data and the number of visits to the forum. We are happy to help you choose the right plan.
    • The data migration is performed from a standard forum software supported by us.1

    1 Supported standard forum softwares: Burning Board 2.3.x/3.x/4.x, Burning Board Lite 2.1.x, IP.Board 3.4.x/4.x, Kunena 3.0.x, MyBB 1.8.x, NodeBB 0.x, phpBB 3.x, SMF 2.x, vBulletin 3.8.x-4.2.x, 5.x, WoltLab Suite Forum 5.x, WordPress 3.7+, XenForo 1.2.x-1.4.x/2.x, Xobor

    About the WoltLab Cloud

    The hassle-free solution for running your forum, we take care of installation, migration and regular updates. Thanks to the fast, stable and secure operation, you enjoy all the advantages of our software without having to worry about the technical aspects. All license costs are already included and with our simple price structure it remains predictable for you. No matter what size your forum achieves, our flexible solutions cover everything, of course 100% hosted in Germany.

    Understandable, but the currently used editor software does not allow us to offer this feature in a sane way. We do have plans to switch to a different editor or version in the future, but because of the tight integration with a lot of components, this is neither a simple nor a quickly done task. Given this background I am not able to reliably predict when we make the switch, thus for now the feature isn't there.

    We will not implement image resizing with the currently used editor software, it has too many issues that we cannot work around in a sane way. However, we do plan to switch to a different editor or version in a future release. This isn't a simple decision and rushing it would have devastating consequences considering how deep an editor is integrated into a software, starting from plugins all the way to the backend processing on the server

    We have just released new versions of our products:

    • WoltLab Suite 5.3.1
    • WoltLab Suite 5.2.10
    • WoltLab Suite 3.1.18


    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

    • Improved the layout of the list of blogs of deleted users. 5.2
    • Resolved an issue in installations using the legacy mysql extension. 5.2

    WoltLab Suite Calendar

    • Optimized a database query to provide more data for the list of events. 3.1 5.2

    WoltLab Suite Filebase

    • The version filter now supports scrolling. 5.2
    • Requiring new files to be approved prior to the publication no longer triggers two separate entries in the moderation. 5.2
    • Removed some orphaned data from a previous database modification. 5.3

    WoltLab Suite Forum

    • Skip posts with an invalid creation date when calculating the installation date. 3.1 5.2
    • Improved the performance of loading moderation actions in large threads. 3.1 5.2 5.3
    • Hide the button to mark posts as the best answer for guests. 5.2
    • Include the meta description when copying forums. 5.2
    • Improved the accessibility of edit links in the thread list. 5.2
    • Editing the global CSS/SCSS caused the forum icons to be missing in the compilation result. 5.3

    WoltLab Suite Gallery

    • Incorrect handling of rotated images when using the ImageMagick graphics library. 3.1 5.2
    • Skip some unrelated response errors when validating links to external videos. 3.1 5.2

    WoltLab Suite Core: Conversations

    • Improved the accessibility of edit links in the conversation list. 5.2

    WoltLab Suite Core: Importer

    • phpBB 3.x
      • Improved the detection of embedded attachments. 5.2
      • Workaround for invalid select options in the imported data. 5.2
    • SMF 2.x
      • Some password hashes were incorrectly recognized. 5.2

    WoltLab Suite Core: Legal Notice

    • Removed the explicit reference to certain laws for better compliance with legal regulations. 5.2 5.3

    WoltLab Suite Core

    • Hitting return inside the editor in Android no longer closes the keyboard. 3.1 5.2
    • Pasting data into the editor on Android caused the contents to be pasted twice. 3.1
    • Improved the wording of the error message for cronjobs to provide more details on the affected cronjob. 3.1 5.2
    • Restrict the list of search suggestions for guests if the site requires a general log-in. 3.1
    • Deleting the first attachment in the list of uploaded attachments could remove another attachment from the view. 3.1 5.2
    • Improved the visuals of the "Login with Google" button to comply with updated requirements. 5.2
    • Prevent the quote tooltip from being selectable on touch devices. 5.2
    • Hide the edit button for boxes on touch devices. 5.2
    • Processing some types of images during the upload could cause the browser to be stuck in an infinite loop. 5.2
    • Improved the handling of 3rd party login providers when the previous session has expired. 5.2
    • Deleting moderation queues did not remove comments attached to them. 5.2 5.3
    • Invalid settings for the registration activation method could have caused upgrades from 5.2 to fail. 5.3
    • Improved the generated stylesheet to prevent the icons sometimes not being able to load. 5.3
    • Allow embedded media to be wrapped in a link. 5.3
    • Improved the visuals of the list of related articles. 5.3

    The main issue is that serving different images types can currently only be performed in a backwards incompatible way. Using <picture> is an elegant, although incredibly verbose, solution. However, this would break existing CSS selectors in way too many cases that are beyond our control.


    Another "clever" approach is the srcset attribute, which would allow us to serve images to legacy browsers using src while providing a newer format with srcset. The only downside is that this doesn't allow for content type negotiation and Safari on iOS < 14 or macOS < 11 (Big Sur) faints if it sees webp.


    We do want to support newer formats and eventually migrate entirely to more efficient formats, but we do have to keep compatibility in mind. WoltLab Suite 5.4 will drop the compatibility with Internet Explorer 11, but unfortunately that doesn't help us here in any way, because Safari is holding us back. Looking at the historically adoption rate of iOS and macOS, we might see webp arriving after WoltLab Suite 5.4.

    Hello,


    it appears to be working right now, the link resolves just fine and displays the user list. Can you please try running the test in the admin panel again? Also, the redirect appears to be cache in your browser and thus is misleading you.

    but when I manually change the URL to omit the index.php part I now get redirected to the homepage.

    The whole url rewriting isn't anything remotely magic, in fact is is very simple and does two things:

    1. The software will tell the browser that a page like index.php?members-list/ is available via /members-list/ instead.
    2. The webserver sees requests for /members-list/ and tells PHP that index.php?members-list/ was requested by the browser.


    So when you say you are being redirected, where does it redirect you to? The "homepage" is a pretty broad term, this could mean the start page of our software or, if the forum is running in a subdirectory, the / url of your entire site.

    Hello,


    The issue appears to be that "blank page" and whatever that is (possibly a hidden error message) is holding you back. Please ask your hosting company if they can figure out what is causing the webserver to not (properly) respond to the request.

    I understand, in that case I suggest that you get in touch with your hosting company, possibly some unrelated rule is interfering with your setup. Since the regular page requests work and rewriting is just an internal process in the webserver (client asked for X, but translate this to Y), this is most likely an issue with the webserver.

    A blank page is an indicator for a suppressed error message, enabling display_errors in PHP could help. In any case, the error log of the webserver should provide you with a more detailed error message.

    Yes, it must be configured for the installation directory. You can manually try to access a page by manipulating the url of a known page.


    Navigate to the members list, the URL should read /index.php?members-list/. Now change it into /members-list/ and hit return to access the page. If the rewrites are working properly, you should be redirect to the first url, because rewrites are disabled. If you see any other page, such as a generic error page of your webserver, then the .htaccess configuration is not applied.

    Hello,


    The rewrite rule test dispatches requests to known valid locations if the rewrite rules are correctly set up. If the above rules have been placed in the directory of the Core itself, then this should work for Apache. Possible reasons why this could still fail:

    • You are not using Apache, an increasing number of webhosting softwares use nginx for their core services.
    • Apache is configured to not interpret .htaccess files at all.
    • The rewrite module for Apache is not loaded.

    You can test for the rewrite module by removing the <IfModule …> and </IfModule> lines. If the webserver starts replying with an internal server error, then the rewrite module is not available.