Hei ! Guest  

Posts by tunhj1

  • Update: WoltLab Suite 5.2.3 / 3.1.12 / 3.0.23

    Quote from Nyheter og oppdateringer

    We have just released new versions of our products:

    • WoltLab Suite 5.2.3
    • WoltLab Suite 3.1.12
    • WoltLab Suite 3.0.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.

    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.

    Compatibility with PHP 7.4

    This update introduces compatibility with PHP 7.4 for the WoltLab Suite 3.0.x and 3.1.x series.

    Notable Changes

    The list below includes only significant changes, minor fixes or typos are generally left out. Some changes have been applied in 3.1 or 5.2 in earlier updates and are not listed separately.

    WoltLab Suite Blog

    • Compatibility with PHP 7.4. 3.1 3.0
    • Improper encoding of values yielded incorrect data for enriched search results. 3.1

    WoltLab Suite Calendar

    • Imported events use the custom location name if the imported event from iCal does not expose coordinates. 5.2
    • The end data was sometimes uneditable. 3.1 3.0
    • Greatly increased the range for the maximum number of repeated event dates. 3.0
    • Skip invalid dates in imported iCal exports. 3.0

    WoltLab Suite Filebase

    • Custom boolean options did not show their value if the user selected "no". 5.2

    WoltLab Suite Gallery

    • The generated HTML of the album and image bbcode was sometimes invalid. 5.2
    • Watermarks have been incorrectly applied to thumbnails of video links. 3.1
    • The page location was incorrect for nested categories. 3.1 3.0
    • An incorrect number of images were reported inside the album bbcode. 3.1 3.0

    WoltLab Suite Forum

    • Empty RSS feeds could raise an exception. 5.2
    • Moved the reaction button on mobile devices back into the message menu due to several incompatibilities. 5.2
    • Threads could be hidden from the thread list if the thread starter is a guest and the current user blocks other users. 5.2
    • Custom boolean options did not show their value if the user selected "no". 5.2
    • The list of unresolved threads yielded inaccurate results for guests. 3.1
    • Incorrect logging of threads that are moved to the trash bin. 3.0
    • External links could break the user group permission form. 3.0

    WoltLab Suite Core: Conversations

    • Incorrect update of usernames when merging a user with another. 3.0
    • Leaving a draft conversation yielded an error. 5.2 3.1 3.0

    WoltLab Suite Core: Importers

    • SMF 2.x
      • Added support for legacy attachment filenames. 3.0
    • MyBB 1.x
      • Incorrect recognition of quotation marks inside font bbcodes. 3.1 3.0
    • vBulletin 5.x
      • Broader support for different [attach] types. 3.1
      • BBCodes in signatures had not been converted. 3.1
      • Improved the support for pixel based font sizes. 3.1

    WoltLab Suite Core

    • Improved the compatibility with code that relies on legacy message handling. 5.2
    • The system check now validates the availibility of graphics processing libraries. 5.2
    • Improved the styling of messages for Google AMP. 5.2
    • Backspacing the empty editor in iOS Safari yielded unexpected HTML. 5.2
    • The number of pending notification and the favicon where sometimes not updated when the browser tab is running in the background. 5.2
    • Mentioning a user group would yield only a single notification. 5.2
    • Improved the reaction UI for large touch devices (iPad Pro 12.9"). 5.2
    • Chromium based browsers did not properly outdent nested lists in the editor. 5.2
    • The upgrade from 3.1 to 5.2 failed in MySQL >= 8.0.19. 5.2
    • Adding or editing users could silently fail due to validation errors in the signature text. 3.1
    • Converting text lines into code in the WYSIWYG editor using Firefox could cause extra blank lines. 3.1
    • User mentiones had a trailing whitespace that caused a small gap between mentiones and the adjacent text. 3.1
    • Compatibility with PHP 7.4. 3.1 3.0
    • The Facebook login no longer requests legacy scopes that could cause issues. 3.0
    • Upgraded the GitHub login due to changes to their API endpoints. 5.2 3.1 3.0
    • Resizing the browser window would not always rebuild the dimensions of a dialog. 3.0
    • Rebuilding users could causes issues with signatures from newly registered users. 3.0
    • Reject access tokens of banned users. 3.1 3.0
    • HTML entities were encoded twice in the anchor links of the user profile tabs. 3.1 3.0
    • Error logs would sometimes be removed after a delay due to an incorrect time comparison. 5.2 3.1 3.0

    kilde: Please login to see this link.

  • For Developers: Changes to Our Public Repositories

    Quote from Nyheter og oppdateringer

    We're changing the way we use our branches in all of our repositories, paving the way for an accelerated release cadence. These changes will become effective on Wednesday, February 19th, 2020. We highly recommend that you adjust your build processes, in particular all sorts of artifacts, to reflect these changes.

    The New Branch Schema

    Old branches have been tracked in version branches, such as 2.1 or 3.0, for a long time already. However, the current and next version have faced some inconsistencies over the past years, residing in different branches with sometimes unclear rules on when they are migrated into version branches. This has historically lead to some confusion with 3rd party developers that had issues tracking down the correct branch to apply and/or suggest their changes.

    The new schema puts up clear rules on this:

    • Stable version will always reside in version branches, regardless of their age.
    • master is always the development branch that eventually becomes the next stable version.
    • Upon reaching the stable version .0, the master branch is transfered into the appropriate version branch.
    • The next branch has become obsolete, as it is now represented by the master branch.

    Effective Changes: An Example

    The Core's repository (Please login to see this link.) will serve as an example for the aforementioned changes:

    TreeBeforeAfter
    Version 2.1.x2.12.1
    Version 3.0.x3.03.0
    Version 3.1.xmaster3.1
    Version 5.2.xnext5.2
    (Next version)---master

    Timeline

    These changes will enter into force on Wednesday, February 19th, 2020.

    kilde: Please login to see this link.