Tweet
vBulletin 2.0.0 RELEASE CANDIDATE 3
We are proud to announce that the third release candidate for vBulletin 2.0 is now in the members area. The main change from RC2 is a fix for a major security issue. We will not divulge any details at this time, so that you can be sure to upgrade to the secure RC3. However, details will be posted on BugTraq in a few weeks time, so be sure to upgrade as soon as possible!
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.
New Installation Instructions
For fresh installations, you must run the install.php file in the admin directory. Before you do this, take the config.php.new file, edit it to contain your details, then upload it as config.php to the server.
Then you can run through the install.php script in much the same way as old install scripts.
Upgrade instructions:
>From 1.1.x:
Upload all the files, then run the upgrade1.php scrint in the admin area. When you are done, be sure to delete install.php and all the upgradex.php scripts.
>From beta 1:
Upload all the files, then run the upgrade2.php script in the admin area. Then run upgrade3.php. Then run upgrade4.php. Then run upgrade5.php. Then run upgrade6.php. Then run upgrade7.php. Then run upgrade8.php. When you are done, be sure to delete install.php and all the upgradex.php scripts.
>From beta 2:
Upload all the files, then run the upgrade3.php script in the admin area. Then run upgrade4.php. Then run upgrade5.php. Then run upgrade6.php. Then run upgrade7.php. Then run upgrade8.php. When you are done, be sure to delete install.php and all the upgradex.php scripts.
>From beta 3:
Upload all the files, then run the upgrade4.php script in the admin area. Then run upgrade5.php. Then run upgrade6.php. Then run upgrade7.php. Then run upgrade8.php. When you are done, be sure to delete install.php and all the upgradex.php scripts.
>From beta 4/4.1:
Upload all the files, then run the upgrade5.php script in the admin area. Then run upgrade6.php. Then run upgrade7.php. Then run upgrade8.php. When you are done, be sure to delete install.php and all the upgradex.php scripts.
> From beta 5:
Upload all the files, then run the upgrade6.php script in the admin area. Then run upgrade7.php. Then run upgrade8.php. When you are done, be sure to delete install.php and all the upgradex.php scripts.
> From release candidate 1:
Upload all the files, then run the upgrade7.php script in the admin area. Then run upgrade8.php. When you are done, be sure to delete install.php and all the upgradex.php scripts.
> From release candidate 2:
Upload all the files, then run the upgrade8.php script in the admin area. When you are done, be sure to delete install.php and all the upgradex.php scripts.
Changed Templates
Note: Upgrading will not overwrite any of your custom templates.
- priv_forwardmultiple,priv_sendprivmsg,priv_sendtobuddies (added javascript validation for PM length - should prevent all this messing around with using the 'back' button and getting a blank message
- postbit -> altered to use new templates postbit_buddy and postbit_search instead of having 'hard-coded' buttons.
- showthread_polloptions, modifyoptions, showthread_threadrate, showthread - fixed a few sessions issues
- modifyoptions_stylecell (fixed typo)
- privmsg - fix link for "search" icon
- newthread, newreply, editpost - also have javascript validation of message length
New templates:
- postbit_buddy and postbit_search
You can view the new templates from in the control panel by clicking on the 'view original' next to your custom template.
Changelog
Enhancements/New Features:
- Settings can now have textarea entry fields
- optimise queries for show last poster /last post from home page
- priv_forwardmultiple,priv_sendprivmsg,priv_sendtobuddies (added javascript validation for PM length - should prevent all this messing around with using the 'back' button and getting a blank message
Bug fixes:
- Fixed major security issue. Details will be available when all customers have had a chance to upgrade.
- privmsg - fix link for "search" icon
- Fix automatic sessionhash removal bug
- Fix minor vulnerability in CP entry routines
- postbit -> altered to use new templates postbit_buddy and postbit_search instead of having 'hard-coded' buttons.
In conclusion...
We have emptied the bugs forum again to get a fresh start. If you want threads moved back into the 'live' area, just let a moderator know, and they will do that for you.
We are very near to declaring version 2.0 stable for general use. If you do know of any outstanding bugs, please let us know as soon as possible.
Anyway, get to that members area!
John
To discuss this, please post here:
We are proud to announce that the third release candidate for vBulletin 2.0 is now in the members area. The main change from RC2 is a fix for a major security issue. We will not divulge any details at this time, so that you can be sure to upgrade to the secure RC3. However, details will be posted on BugTraq in a few weeks time, so be sure to upgrade as soon as possible!
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.
New Installation Instructions
For fresh installations, you must run the install.php file in the admin directory. Before you do this, take the config.php.new file, edit it to contain your details, then upload it as config.php to the server.
Then you can run through the install.php script in much the same way as old install scripts.
Upgrade instructions:
>From 1.1.x:
Upload all the files, then run the upgrade1.php scrint in the admin area. When you are done, be sure to delete install.php and all the upgradex.php scripts.
>From beta 1:
Upload all the files, then run the upgrade2.php script in the admin area. Then run upgrade3.php. Then run upgrade4.php. Then run upgrade5.php. Then run upgrade6.php. Then run upgrade7.php. Then run upgrade8.php. When you are done, be sure to delete install.php and all the upgradex.php scripts.
>From beta 2:
Upload all the files, then run the upgrade3.php script in the admin area. Then run upgrade4.php. Then run upgrade5.php. Then run upgrade6.php. Then run upgrade7.php. Then run upgrade8.php. When you are done, be sure to delete install.php and all the upgradex.php scripts.
>From beta 3:
Upload all the files, then run the upgrade4.php script in the admin area. Then run upgrade5.php. Then run upgrade6.php. Then run upgrade7.php. Then run upgrade8.php. When you are done, be sure to delete install.php and all the upgradex.php scripts.
>From beta 4/4.1:
Upload all the files, then run the upgrade5.php script in the admin area. Then run upgrade6.php. Then run upgrade7.php. Then run upgrade8.php. When you are done, be sure to delete install.php and all the upgradex.php scripts.
> From beta 5:
Upload all the files, then run the upgrade6.php script in the admin area. Then run upgrade7.php. Then run upgrade8.php. When you are done, be sure to delete install.php and all the upgradex.php scripts.
> From release candidate 1:
Upload all the files, then run the upgrade7.php script in the admin area. Then run upgrade8.php. When you are done, be sure to delete install.php and all the upgradex.php scripts.
> From release candidate 2:
Upload all the files, then run the upgrade8.php script in the admin area. When you are done, be sure to delete install.php and all the upgradex.php scripts.
Changed Templates
Note: Upgrading will not overwrite any of your custom templates.
- priv_forwardmultiple,priv_sendprivmsg,priv_sendtobuddies (added javascript validation for PM length - should prevent all this messing around with using the 'back' button and getting a blank message
- postbit -> altered to use new templates postbit_buddy and postbit_search instead of having 'hard-coded' buttons.
- showthread_polloptions, modifyoptions, showthread_threadrate, showthread - fixed a few sessions issues
- modifyoptions_stylecell (fixed typo)
- privmsg - fix link for "search" icon
- newthread, newreply, editpost - also have javascript validation of message length
New templates:
- postbit_buddy and postbit_search
You can view the new templates from in the control panel by clicking on the 'view original' next to your custom template.
Changelog
Enhancements/New Features:
- Settings can now have textarea entry fields
- optimise queries for show last poster /last post from home page
- priv_forwardmultiple,priv_sendprivmsg,priv_sendtobuddies (added javascript validation for PM length - should prevent all this messing around with using the 'back' button and getting a blank message
Bug fixes:
- Fixed major security issue. Details will be available when all customers have had a chance to upgrade.
- privmsg - fix link for "search" icon
- Fix automatic sessionhash removal bug
- Fix minor vulnerability in CP entry routines
- postbit -> altered to use new templates postbit_buddy and postbit_search instead of having 'hard-coded' buttons.
In conclusion...
We have emptied the bugs forum again to get a fresh start. If you want threads moved back into the 'live' area, just let a moderator know, and they will do that for you.
We are very near to declaring version 2.0 stable for general use. If you do know of any outstanding bugs, please let us know as soon as possible.
Anyway, get to that members area!
John
To discuss this, please post here:
Comment