No announcement yet.

vBulletin 3.6 Release Candidate 1 Released

  • Filter
  • Time
  • Show
Clear All
new posts

  • vBulletin 3.6 Release Candidate 1 Released

    vBulletin 3.6 Release Candidate 1

    Release Candidate 1 brings vBulletin 3.6 a step closer to becoming our main supported release. Note, however, that this is still not considered a stable release, though we hope it will become so.

    What does Release Candidate mean?

    Release Candidate, or RC for short, means that we believe vBulletin 3.6 is ready to be declared a "stable" and "supported" supported release once it as undergone some additional testing. The only known bugs that may remain are trivial. Additionally, vBulletin 3.6 is now "code complete", so don't expect to see any changes except for bug fixes.

    RCs will be released until only trivial bugs are being fixed. Once this happens, the next stage is to move on to "gold" or, as it's officially known, 3.6.0.

    The Usual Important Stuff

    This is unstable/unsupported 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 version.
    • Pre-release software is unsupported and you install this version at your own risk.
    • Some minor bugs remain unresolved at this time, so pre-release 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 pre-lease versions in rapid succession as bugs are fixed and holes are plugged. Do not install this 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 3.6.0 Beta 4

    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.


    Add attachmentid to post preview.

    Requires Revert? No


    Removed a space between the infraction and report post icons.

    Requires Revert? No


    Fixed some invalid markup.

    Requires Revert? No


    Remove hardcoded text.

    Requires Revert? No


    Fixed smilie overflow with W3C compliant browsers.

    Requires Revert? No


    • #3
      You may discuss the release candidate in this thread.


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