vBulletin 3.0.0 Release Candidate 2 Released

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • Kier
    Former Lead Developer, vBulletin
    • Sep 2000
    • 8179

    vBulletin 3.0.0 Release Candidate 2 Released

    vBulletin 3.0.0 Release Candidate 2

    The hawk-eyed amongst you will have noticed that vB3 RC1 was supposed to be released today, but was actually released three days early. The number of serious bugs found with RC1 has been very small, so we are now able to put forward Release Candidate 2, which includes fixes for all the bugs identified in RC1.

    A good portion of the bugs found with vBulletin 3 Release Candidate 1 were related to cross-browser compatability of the new templates, and efforts have been made to rectify these. One of the biggest changes has been to the postbit template, which in both RC1 and the Gamma version used <div> tags controlled by CSS to achieve its layout. Unfortunately it would appear that many browsers just aren't ready for this, so in an attempt to make the postbit template easier to edit for novice administrators and to preserve styling across the widest range of browsers, this template has been rewritten to use a simple table-based layout instead. Visually the template should appear identical to the RC1 and Gamma versions, but lots more browsers display it correctly now.

    On Sunday a bug was discovered in the Release Candidate 1 code that we felt represented a security problem, and a patch release was issued. This issue affects only RC1 and only users who registered on the board after RC1 was installed. This bug has been eliminated completely for RC2 and we would recommend that any board running RC1 should upgrade to RC2 as soon as possible.

    List of Bugs Fixed
    • Changed postbit and bbcode_* templates to use <table> tags rather than <div> tags for increased cross browser compatibility. (This should also fix several related bugs.)
    • Fixed possible security issue relating to logging in. Note: some users may need to request a new password in order to be able to login.
    • Readded no-cache header setting, which was mistakenly left out. (Link)
    • Forced sending of no-cache headers in the admin control panel. (Link)
    • Fixed situation where "Edit Avatar" didn't show when it was supposed to. (Link)
    • Fully removed references to $vboptions['abspath'] (Link)
    • Fixed issue causing '//' to be displayed in the URL after being redirected. (Link)
    • Fixed fatal error when using certain forum jump options. (Link)
    • Admin editing member's post can result in signature not being shown (Link)
    • Last post info bleeds into adjacent cells (Mozilla, Opera) (Link)
    • Inability to set unlimited attachment count (Link)
    • Assorted style issues.
    • Assorted language issues.
    • Click here to view the full list.
    Installation / Upgrade Instructions

    To install vBulletin 3, or to upgrade from a previous version of vBulletin, download the zip file from the members' area, unzip the contents and upload the contents of the 'upload' folder to the forums directory on your web server, overwriting all existing files.

    Open the 'includes/config.php.new' file in a text editor and alter the contents to match the settings for your own web server. Finally rename this file as 'config.php'.

    Next follow the appropriate instructions below (replacing the text in red with the address of your own forums):

    Installing a fresh version

    Using your browser, navigate to http://your.forums.site/forums/install/install.php and follow the on-screen instructions.

    Upgrading from a previous version

    We strongly recommend that you back up your database by following the instructions in step one, here. Then, using your browser, navigate to http://your.forums.site/forums/install/upgrade.php and follow the on-screen instructions.
  • Kier
    Former Lead Developer, vBulletin
    • Sep 2000
    • 8179

    #2
    You can discuss this release here:

    Comment

    widgetinstance 262 (Related Topics) skipped due to lack of content & hide_module_if_empty option.
    Working...