vBulletin 3.6.11

As promised last week, today sees the release of a maintenance version for vBulletin 3.6.x.

vBulletin 3.6.11 contains a selection of bug fixes, details of which can be found in the bug tracker. Additionally, a change has been made to prevent users from setting their password to their username. See below for more information.

The security fixes included in the vBulletin 3.6.10 PL releases are also included in vBulletin 3.6.11.


Username=Password Disallowed

In this release, users will no longer be allowed to set their username and passwords to the same value. Users who already have a password that is the same as their username will be forced to change their password on their next login. Additionally, a tool has be added to the Admin Control Panel to email affected users with a new password. Please be aware of these potential compatibility changes when upgrading.


Upgrading from Previous Versions

3.6.11 is a maintenance release. We recommend that all customers running prior versions of vBulletin 3.6 upgrade to benefit from bug fixes and stability improvements.

Full instructions for upgrading vBulletin are available here.


PHP and MySQL Requirements

Please note that vBulletin 3.6.x requires at least PHP 4.3.3 and MySQL 4.0.16 or later.

However, we recommend that vBulletin 3.6.x is run on PHP 5.2.6 with APC (or a similar opcode cache) and MySQL 5.0.51 for best performance and stability.


End of Life for PHP 4

PHP 4 has now reached its end of life. We strongly recommend that customers update their servers to PHP 5.2.6 if they are still running PHP 4. vBulletin 3.6.x supports PHP 5 without any problems, though you may need to disable strict mode for MySQL, see here on how to enable 'force_sql_mode'.

Note: We will continue to support PHP 4 in the vBulletin 3 series.


Download vBulletin 3.6.11

As usual, vBulletin 3.6.11 is available for all customers with valid, active licenses to download from the vBulletin Members' Area.

vBulletin Members Area

Please do not use this thread for support questions.

More...
Read more (locally) ...

​