Burning Board 4.1.0 Beta 3 Download

  • Burning Board 4.1 is the modern, user-friendly and secure forum software. Try out one of the most easy and intuitive forum software for free and experience it's awesome features.

    System Requirements

    WoltLab Burning Board 4.1 requires the following components to install and use it:

    Webserver with PHP 5.3.2+
    MySQL 5.1.17+
    20 MB free disk space
    Current Webbrowser (Chrome 39+, Firefox 34+, Internet Explorer 10+, Safari 8+)

    Installation Guide

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

    Updating from Burning Board 4.1.0 Beta 2

    Please read the next post for instructions to update from Burning Board 4.1.0 Beta 2.

    Updating from Burning Board 4.0

    The version explicitly does not support updating from previous versions of our software. Update support will be added with future releases.

    Compatibility with other WoltLab® products

    This release is not compatible with Community Blog 2.0, Community Calendar 2.0, Community Gallery 2.0 and WoltLab Filebase 2.0. We'll release compatibility updates with a future update.

    Usage and Support

    This evaluation version is not suitable for productive use, any use of this version in an productive environment is at your own risk. Updating from Burning Board 4.1 Beta 3 to future versions is not guaranteed. You may use this version until April 30th 2015, if you wish to continue past this date, a valid Burning Board 4.1 license is required.

    We're looking forward to hear your feedback and reports of possible issues in the Burning Board 4.1.x forum.

    Notice for Developers

    We have added two new features to the editor API regarding the autosave component, please read this post.

    Download WoltLab Burning Board 4.1 Beta 3

  • Please be aware that the list below does not cover every single change, while it does provide details on important changes, minor fixes (e.g. typos) are left unnoticed.

    Burning Board 4.1.0 Beta 3

    • Notifications triggered by guests did not show up properly
    • Label groups requiring a selection could block the ability to add new RSS feeds
    • Fixed an issue related to non-ignorable forums
    • Changing the board type from board to category/external link was broken
    • Fixed an issue when rebuilding data

    User Conversation System 2.1.0 Beta 2

    • Fixed an issue when rebuilding data

    Importer 2.1.0 Beta 3

    • Exporting user ranks from Burning Board 4.x failed

    Infraction System 2.1.0 Beta 3

    • Some internal changes

    WoltLab Community Framework 2.1.0 Beta 3

    • Redactor (WYSIWYG-editor)
      • Code-BBCode is now visually rendered and provides a complete UI to add and manage them
      • Drafts saved in the background will automatically be discarded if the content has been edited by someone else (currently applies to post editing only)
      • New 'prompt' mode will ask before restoring a saved draft in order (currently applies to creating new conversations only)
      • Resolved a bunch of reported issues
      • Content will now automatically be saved every 15 seconds in the background (previously: 60 seconds), a short notice will appear only once every 2 minutes
    • SSL certificates are now properly validated if using a HTTP-proxy server
    • Fixed an issue with image titles improperly sanitized within the ImageViewer
    • Update servers now have a opt-in API which will reduce the time and effort required to update the package list if it was unchanged
    • API for taggable items now support options and permissions
    • Plugin-Store: Improved search for purchased items
    • Minimum avatar dimensions increased to 96 × 96 Pixel (previously: 48 × 48 Pixel)
    • Resolved some issues when rebuilding data
    • Fixed ACP smiley upload
  • This is a notice for developers only, end-users can safely disregard this post.

    WCF 2.1 Beta 3 adds two additional attributes related to the autosave feature, both control the restore behavior:

    • data-autosave-prompt="true" will explicitly ask if saved content should be restored
    • data-autosave-last-edit-time="<timestamp>" will cause the editor to discard saved content if it is older than the given timestamp

    The check for lastEditTime is useful if you have a content type which can be expected to be edited by multiple people (e.g. forum posts). It attempts to circumvent the race condition taking place if user A starts editing but never submits it and the same content is edited afterwards by user B. If user A now attempts to edit the same content again the editor would load the draft - which is based upon the state before user B edited it - where the origin is out-of-sync.

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!