vBulletin 2.3.0 Release Candidate
vBulletin 2.3.0 includes several bug-fixes although none of these are security related.
Backing up forums
Please be sure to check your backups, that they are complete before continuing with an upgrade. We had reports that PHP was causing time out errors when creating the back up SQL, and this was causing for incomplete or corrupted backups. The safest way to do a backup is to use the mysqldump utility through telnet, as it will not suffer from any such problems.
Installation / Upgrade Instructions
These are available in the Members Area.
Functionality Changes / New Features
Template Changes (from 2.2.9)
New Templates (from 2.2.9)
Removed Templates (from 2.2.9)
Bug Fixes (from 2.2.9)
Files changed (from 2.2.9)
PLEASE NOTE
Those members of the vBulletin team who are still running vB2 on their boards have been running this version for the last few days and I am confident that no further bugs will arise, but in keeping with recent releases I am declaring this version a Release Candidate. If no bugs are found in the next few days I will upgrade the status of vB 2.3.0 to 'Stable'.
In conclusion...
The private beta for vBulletin 3 will be starting very soon now, and if no major bugs are found during the private beta we hope to release a public beta to all licenced customers who want it within a matter of weeks rather than months. For the time being we recommend that you upgrade to vBulletin 2.3.0, which we hope will be the final release for the vBulletin 2 range.
vBulletin 2.3.0 includes several bug-fixes although none of these are security related.
Backing up forums
Please be sure to check your backups, that they are complete before continuing with an upgrade. We had reports that PHP was causing time out errors when creating the back up SQL, and this was causing for incomplete or corrupted backups. The safest way to do a backup is to use the mysqldump utility through telnet, as it will not suffer from any such problems.
Installation / Upgrade Instructions
These are available in the Members Area.
Functionality Changes / New Features
- One of the biggest changes for vBulletin 2.3.0 is that all calls to PHP's mail() function are now routed via a central vbmail() function in functions.php. This was done so that people with non-standard server setups can easily modify the way email is sent from their vBulletin installation.
- We have also corrected a small bug that would assign all users to usergroupid=2 (registered users) after they changed their email address regardless of their original usergroup.
Template Changes (from 2.2.9)
- forumdisplaybit - added s=$session[sessionhash] to member.php links
- searchresultbit_threadonly - added s=$session[sessionhash] to member.php links
- subscribe_threadbit - added s=$session[sessionhash] to member.php links
- username_loggedout - added s=$session[sessionhash] to member.php links
- faq3 - removed width/height from edit.gif <img> tag
- standarderror - removed $bburl from vb_bullet.gif image path
- showgroups - removed moderators table (now uses showgroups_group template instead)
- showgroups_bit - extended so it can be used for standard usergroups AND moderators
- showgroups_group - extended so it can be used for standard usergroups AND moderators
- editpost_attachment - replaced attachmentid with postid
- mailform - added <input type="hidden" name="url" value="$url">
New Templates (from 2.2.9)
- showgroups_moderatedforums - used to allow showgroups_bit to be used for ALL groups
- showgroups_forumheader - used to allow showgroups_group to be used for ALL groups
- showthread_pollresults_cantvote - used to notify member that they can not vote on a poll
Removed Templates (from 2.2.9)
- showgroups_adminbit - no longer required (functionality provided by showgroups_bit)
Bug Fixes (from 2.2.9)
- Splitting threads can create empty thread [b]Full Details[/b]
- Empty passwords possible via UserCP [b]Full Details[/b]
- Subscribed threads sometimes invisible in UserCP [b]Full Details[/b]
- Splitting and moving new thread does not update lastpost on forumhome [b]Full Details[/b]
- Edit post dies not check for all caps [b]Full Details[/b]
- Search index not properly updated on edit post [b]Full Details[/b]
- Update thread info does not reflect changed usernames [b]Full Details[/b]
- Email validation not sent to certain users [b]Full Details[/b]
- Buddy/Ignore list editing broken with names containing apostrophes [b]Full Details[/b]
- Banned users can bypass the ban [b]Full Details[/b]
- Slow attachment queries optimized [b]Full Details[/b]
- Bypassing Registration Adult/Coppa [b]Full Details[/b]
- Redirect is wrong after emailing user [b]Full Details[/b]
- Members getting email notification after thread moved to private forum [b]Full Details[/b]
- Unexpected behaviour after editing template and changing templateset [b]Full Details[/b]
- Replacement variables are parsed twice (default + custom) [b]Full Details[/b]
- Numerous template issues [b]Full Details[/b]
Files changed (from 2.2.9)
- Main Directory: calendar.php, editpost.php, member.php, member2.php, memberlist.php, misc.php, newreply.php, newthread.php, online.php, postings.php, private.php, private2.php, register.php, report.php, search.php, sendtofriend.php, showgroups.php, showthread.php
- Admin Directory: admin/email.php, admin/functions.php, admin/global.php, admin/misc.php, admin/template.php, admin/user.php, admin/vbulletin.style
- Mod Directory: mod/moderate.php
- And the usuals (all for just the version number): admin/upgrade1.php, admin/install.php
PLEASE NOTE
Those members of the vBulletin team who are still running vB2 on their boards have been running this version for the last few days and I am confident that no further bugs will arise, but in keeping with recent releases I am declaring this version a Release Candidate. If no bugs are found in the next few days I will upgrade the status of vB 2.3.0 to 'Stable'.
In conclusion...
The private beta for vBulletin 3 will be starting very soon now, and if no major bugs are found during the private beta we hope to release a public beta to all licenced customers who want it within a matter of weeks rather than months. For the time being we recommend that you upgrade to vBulletin 2.3.0, which we hope will be the final release for the vBulletin 2 range.
Comment