vBulletin 3.6 Release Candidate 2 Released

[Marco van Herwaarden]

As posted at vbulletin.com: vBulletin 3.6 Release Candidate 2 Released
(please read the original thread for the template changes and other detail info)

vBulletin 3.6 Release Candidate 2

Release Candidate 2 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.