vBulletin 2.0.0 RELEASE CANDIDATE 2
We are proud to announce that the second release candidate for vBulletin 2.0 is now in the members area. The main changes from release candidate 1 are cosmetic changes and minor bug fixes. As long as there are no major bugs found in RC2, I hope that the next release can be the final one!
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 install1.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 install1.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 install1.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. When you are done, be sure to delete install1.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. When you are done, be sure to delete install1.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. When you are done, be sure to delete install1.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. When you are done, be sure to delete install1.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. When you are done, be sure to delete install1.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. When you are done, be sure to delete install1.php and all the upgradex.php scripts.
Changed Templates
Note: Upgrading will not overwrite any of your custom templates.
- forumdisplay_announcementsonly - altered to support RC1 table formatting options
- calendar - altered to remove wrongly coloured top row of days
- vbcode_smilies - altered to be a separate table
- subscribe_threads / subscribe_nothreads - added JS onchange="xxx" to <select> menus for consistency.
- forumdisplay - minor change to timezone+forumjump table to fix nutscrape errors
- numbernav - missing ';' added to > on last-page link
- forumdisplaybit - now references $thread[postedby] in the "thread starter" column
calendar_enterevent
editpost
newreply
newthread
priv_forwardmultiple
priv_sendprivmsg
priv_sendtobuddies
--> all these templates have the following alterations:
- $vbcode_smilies moved to left column to prevent NS wrapping problems
- <textarea> cols="xx" attribute changed to dynamic value based on browser
- forumrules moved to bottom of page
You can view the new templates from in the control panel by clicking on the 'view original' next to your custom template.
New templates
- error_unregistereduser (NEW!) - error message displayed when trying to view the profile of an unregistered user
Changelog
Enhancements/New Features:
- Don't link unregistered users names in the "thread starter" column
- instant colour preview in styles CP (IE4+, NS6+ only)
- new global replacement { pagetextcolor } added and included in styles CP - not used in default templates, but very useful for custom style sets.
Bug fixes:
- Fixed bug where not all forums would be searchable when you were using access masks
- Fixed bug where the search engine would get confused when extra spaces were inserted
- Fixed reference to (scalar) $firstusername as an array
- Fixed bug where smilies were double parsed
- Fixed url for email registration details in CP
- polls - problems with htmlspecialchars in poll question/options fixed
- vbcode preview in CP fixed
- calendar - altered to remove wrongly coloured top row of days
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 second release candidate for vBulletin 2.0 is now in the members area. The main changes from release candidate 1 are cosmetic changes and minor bug fixes. As long as there are no major bugs found in RC2, I hope that the next release can be the final one!
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 install1.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 install1.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 install1.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. When you are done, be sure to delete install1.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. When you are done, be sure to delete install1.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. When you are done, be sure to delete install1.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. When you are done, be sure to delete install1.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. When you are done, be sure to delete install1.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. When you are done, be sure to delete install1.php and all the upgradex.php scripts.
Changed Templates
Note: Upgrading will not overwrite any of your custom templates.
- forumdisplay_announcementsonly - altered to support RC1 table formatting options
- calendar - altered to remove wrongly coloured top row of days
- vbcode_smilies - altered to be a separate table
- subscribe_threads / subscribe_nothreads - added JS onchange="xxx" to <select> menus for consistency.
- forumdisplay - minor change to timezone+forumjump table to fix nutscrape errors
- numbernav - missing ';' added to > on last-page link
- forumdisplaybit - now references $thread[postedby] in the "thread starter" column
calendar_enterevent
editpost
newreply
newthread
priv_forwardmultiple
priv_sendprivmsg
priv_sendtobuddies
--> all these templates have the following alterations:
- $vbcode_smilies moved to left column to prevent NS wrapping problems
- <textarea> cols="xx" attribute changed to dynamic value based on browser
- forumrules moved to bottom of page
You can view the new templates from in the control panel by clicking on the 'view original' next to your custom template.
New templates
- error_unregistereduser (NEW!) - error message displayed when trying to view the profile of an unregistered user
Changelog
Enhancements/New Features:
- Don't link unregistered users names in the "thread starter" column
- instant colour preview in styles CP (IE4+, NS6+ only)
- new global replacement { pagetextcolor } added and included in styles CP - not used in default templates, but very useful for custom style sets.
Bug fixes:
- Fixed bug where not all forums would be searchable when you were using access masks
- Fixed bug where the search engine would get confused when extra spaces were inserted
- Fixed reference to (scalar) $firstusername as an array
- Fixed bug where smilies were double parsed
- Fixed url for email registration details in CP
- polls - problems with htmlspecialchars in poll question/options fixed
- vbcode preview in CP fixed
- calendar - altered to remove wrongly coloured top row of days
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