vBulletin 3.5 RC2 Released

[Kier]

vBulletin 3.5 Release Candidate 2

Release Candidate 2 brings vBulletin 3.5 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 is a Release Candidate?

A release candidate differs from a beta release in that there are no known bugs. However, this does not mean that there aren't any bugs. A release candidate represents a version of the software that we believe is ready for release, but requires some more testing before we're sure.

How many release candidates will there be?

We can't accurately answer this question, due to the nature of release candidate software. After RC1 is released we will wait a while to see if any new problems are discovered. If bugs are found, they will be fixed and after a period of time we will release the fixed version as RC2. The cycle then begins again - if bugs are found they will be bundled into an RC3 release. However, if no bugs are found, or the bugs found are extremely minor and require only trivial fixes, the current RC version will be renamed 3.5.0 and released. This is the 'gold' or 'stable' release.

For previous major releases like this one, we have usually required three release candidates.

Notes:

This release is almost entirely bug fixes. The only two changes of note are fairly minor:

• The eAccelerator datastore method has been removed due to issues inherent to eAccelerator itself. If you are using this method, you will be seemlessly converted back to the standard database method. (More technical details are provided within class_datastore.php.)
• Product IDs can now be 25 characters long.

As this is still not considered a stable release, the same caveats from previous beta releases still apply:

• Pre-release software is unsupported. You should install pre-release versions at your own risk.
• You should always back up your database fully before attempting to install pre-release software.
• If you choose to install this version, you should be aware that there may be a new version released within a very short period of time. Do not install this version if you are not willing or able to keep up-to-date with new releases.
• ImpEx does not support the 3.5 code yet, and will not support it until the release of 3.5.0 (stable).

Installation / Upgrade

These use the same process as all previous vBulletin 3 releases. Please refer to an earlier release announcement for full instructions.

Changed Files

As this is still not a stable release, full changed file lists will not be provided.

Bug Reports

You may report bugs by clicking here. Before reporting a bug, please attempt to recreate the bug on a default, uncustomized style (especially if your errors are JavaScript related). Additionally, if you have used the plugins/products system at all, please attempt to recreate the issue with the plugins system disabled!

Discussion

To discuss this release, please post in this thread.

[Kier]

Note:
You need to only look through this post for templates you have customized. You do not need to take any action to ensure that your uncustomized templates are the latest versions.

If you find a template you have customized in this list, you will likely want to include the changes made here. However, this is not always required. Under each change listed here, you will see "requires revert?" This refers to whether the changes are mandatory (yes). If the changes are mandatory, things will break if you do not incorporate the changes made. It is strongly recommended that you revert and recustomize any templates that say they require a revert.

Additionally, you may wish to use the "Find Updated Template" feature in the control panel to find templates that have been changed since your last edit to them.

-----------------------------------------------------

modifyoptions

Find this:

$vbphrase[enable_private_messaging]</label><input type="hidden" name="set_options[showemail]" value="1" />

Replace with this:

$vbphrase[enable_private_messaging]</label><input type="hidden" name="set_options[receivepm]" value="1" />

Requires revert? Yes




headinclude

Commas added to meta keywords:

Changed

<meta name="keywords" content="$foruminfo[title_clean] $vboptions[keywords]" />

to

<meta name="keywords" content="$foruminfo[title_clean], $vboptions[keywords]" />

and

<meta name="keywords" content="$threadinfo[title] $vboptions[keywords]" />

to

<meta name="keywords" content="$threadinfo[title], $vboptions[keywords]" />

Requires revert? No, just adheres to some standards.




search_forums

If you have enabled fulltext searching and Boolean Mode and you're using MySQL < 4.0, a notice about boolean search will be displayed to administrators. This notice was added to remind you that boolean search doesn't work with MySQL 3.23 in case you didn't notice the warning when you enabled Fulltext mode. The boolean option will no longer be displayed but that doesn't require a template modification.

Requires Revert? No.




MEMBERINFO

Added a conditional to display instant messaging information as text when Im Icons are disabled in General Settings.

Requires Revert? No.




showthread_quickreply

Added alt text to the increase/decrease size icons.

Requires revert? No.

[Freddie Bingham]

This change was included into the package in the members' area at approximately 3:20 PM EDT.

There is a small problem in RC2 wit Fulltext searching that will force you to use the natural language search if you are on MySQL 4.0.1 or greater. This is the reverse of what we were shooting for (forcing only natural language for MySQL 3.23, MySQl 4.0.0). To rectify this, please download the RC2 package again and replace search.php

OR

Change line 118 of search.php

from:

if ($mysqlversion['version'] > '4.0.1') 

to:

if (version_compare($mysqlversion['version'], '4.0.1', '<'))