The vBulletin team is proud to present vBulletin 3.5.0 Gold.
vBulletin 3.5.0 is now considered our stable and supported release, superceding the 3.0.x series. We now recommend that all customers upgrade to 3.5.0 to take advantage of the new features and improvements, although we will continue supporting 3.0.9 for the forseeable future, providing security fixes as necessary.
Since many of you have been following the unstable releases, we will not post a full change log since 3.0.9 here, but if you want to view that list you may go here.
What does 'Gold' Mean?
The official name of this release is vBulletin 3.5.0, though you may hear it referred to as the 'gold' release. This term refers to the practise of burning the final, stable version of software to a gold CD in preparation for manufacture of the CDs for sale and distribution to customers.
Changes of note since RC3
- Cookie paths and cookie domains are now selected from a drop down or a text box as an override (if you're really sure). This should help prevent invalid cookie paths/domains from being set.
- Merging a thread now merges into one of the existing threads instead of a new one, also giving an option to replace the other threads with redirection notices.
- External.php has returned to retrieving data based on the time the thread was originally posted. (An index was added to optimize this query.)
- Some additional hooks
Please see the appropriate manual sections: Installing vBulletin and Upgrading vBulletin.
Note that the process is the same as it was in the 3.0.x series, however you must redo your config.php if you are upgrading from 3.0.x!
If you have customized templates and upgrade to vBulletin 3.5, you will need to revert many of them or some areas of your board will not function!
(This is particularly true when upgrading from vBulletin 3.0.x. See this post for additional information.)
Uploading the Files
Due to a new database connection method in vBulletin 3.5.0, while uploading the files, it's a good idea to temporarily put your forums behind .htaccess protection or even temporarily rename your forums directory to prevent any visitors from generating database errors.
Consider all files to have changed since the 3.0.x series.
To discuss this release, please post in this thread.