No announcement yet.

vBulletin 3.6 Beta 2 Released

  • Filter
  • Time
  • Show
Clear All
new posts

  • vBulletin 3.6 Beta 2 Released

    vBulletin 3.6 Beta 2

    A week has past since the public release of vBulletin 3.6 Beta 1 and the time is right to proceed to the next stage. vBulletin 3.6 Beta 2 contains a number of fixes and tweaks to the Beta 1 code and we recommend that anyone currently running Beta 1 should upgrade to Beta 2.

    The first round of bugs found in 3.6 Beta 1 has for the most part been simple and quick to fix, so we are hopeful that this will not be a particularly long beta process. However, there are a number of bugs awaiting feedback - please check the bug tracker regularly to see if the developers require further input or feedback on bugs you have reported.

    New Stuff

    Admin Message System
    New for 3.6 Beta 2 is the Admin Message System. This allows messages to be inserted during upgrades (or product installations) which will appear as a 'nag screen' in the Admin Control Panel until addressed.

    This allows us to alert administrators to steps they should take following upgrades, such as rebuilding forum counters or checking for updated templates.

    Arbitrary Infractions
    The infraction system now has the ability for a user to enter an arbitrary point value and expiration date when giving an infraction - provided the user has the appropriate permission to do so.

    The Usual Important Stuff

    This is beta software. If you are not fully at home with backing-up and restoring your forum, dealing with bugs and regular upgrades, do not install this beta version.
    • Beta software is unsupported and you install beta versions at your own risk.
    • Some minor bugs remain unresolved at this time, so beta software should not be on production sites.
    • You should always back up your database fully before attempting to install beta software.
    • If you choose to install this version, you should be aware that we plan to release new beta versions in rapid succession as bugs are fixed and holes are plugged. Do not install this beta version if you are not willing or able to keep up-to-date with new releases.
    • The ImpEx import system does not support the 3.6 code yet, and will not support it until the release of 3.6.0 (stable).
    Installation / Upgrade
    If you are accustomed to the install and upgrade procedure used by vBulletin 3.5 then the 3.6 install and upgrade process will be familiar to you.
    Please refer to an earlier release announcement for full instructions.

    Hacking / Plugins
    While there have not been extensive changes to the underlying architecture of vBulletin 3.6 from 3.5, it is possible that certain hooks may have changed. Therefore you should check with the author of whatever plugins and products to attach to your vBulletin installation to inquire about their compatibility with vBulletin 3.6. Plugin authors should be assured that we do not anticipate major code changes between the Beta 1 code and the final 3.6.0 code, so plugins written for or adapted to 3.6 compatibility should still work with the final code.

    Javascript / AJAX Problems
    Many of the Javascript files for vBulletin 3.6 have changed. However, if templates are reverted or adapted correctly there should be no issue with cached old Javascript files, as we have implemented a system that should force clients to reload Javascript files after an upgrade. If you discover what you believe to be a Javascript problem, please ensure that you are not using cached files by doing a ctrl+F5 hard refresh before reporting it as a bug.

    Reporting Bugs
    Please use the vBulletin 3.6 Bug Tracker to report any bugs you find in vBulletin 3.6.

  • #2
    Templates Changed Since Beta 1

    What does 'Requires Revert' mean?

    The strict definition of 'Requires Revert? Yes' is that the template has been changed in a way that would mean that by keeping an old version of the template, functionality would be lost.

    For example, if we add a new feature then that feature may need certain elements of certain templates may need to be altered. Keeping an old customized version would mean that the new feature would not work.

    In terms of what you need to do, there's a simple checklist:
    • If you have not customized the template, you need not do anything. The old template will be automatically replaced with the new version during the upgrade process.
    • If you have customized the template, you will need to do one of the following things:
      1. The easiest thing to do is to revert the template. This means that your customized version will be deleted and the new master template will automatically take its place.
      2. Alternatively, you can use the template compare system to look at what is new in the template and apply the changes to your customized template. This requires careful attention.

    Added condition around the forum name so it doesn't show blank.
    Several changes to add a custom infraction option.

    Requires Revert: Yes


    Changed conditionals to support infractions not being removed when the relevant post/thread is deleted.

    Requires Revert? Yes


    Added a small bit of spacing between the signature and edit/reply buttons so that they do not overlap in some browsers (firefox).

    Requires Revert? No


    Added a missing closing tag.

    Requires Revert? No (unless you want full XHTML Compliance)


    Added warning about the deletion of a first post removing the thread as well.

    Requires Revert? No


    Added spacing around the text in the fieldset explaining infraction reversal.

    Requires Revert? No
    Last edited by Kier; Tue 13 Jun '06, 5:53am.


    • #3
      You can discuss this release here:


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