Tweet
vBulletin 2.0.0 RELEASE CANDIDATE 1
The fifth and final BETA version of vBulletin 2.0.0 was released into the members area this time last week. We are now proud to announce that the final furlong in the release of version 2.0 with this, the first release candidate. If all goes well, the next version should be the final!
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. 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. 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. 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. 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. 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.
We are aware that in previous vBulletin template sets, there has been a problem with Netscape not displaying table borders, and individual tables within the pages not having a width="xx" attribute set.
This is no longer the case.
All templates now have their content encased in tables with Netscape-compliant borders, and a table width attribute set. These attributes are controllable through the new styles control panel.
In order to benefit from these new features, it it strongly recommended that you revert as many of your custom templates back to the default and then re-customize them, or at least carefully study the default templates, and make the appropriate changes to your custom templates.
For those that have already customized their templates heavily, our apologies, but be consoled by the assurance that the template set in this release will not be changing in any significant way before the final release.
- forumdisplay_announcementsonly (now has daysprune selector to prevent 'losing' old threads.)
- icq (changed old online.miriablablabla address to new wwp.icq.com)
- postbit_attachmentimage - added $postid to variable for performance reasons
- postbit_attachment - added $postid to variable for performance reasons
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_searchnametooshort - error when you do not enter enough characters to do a partial username match on
- privsent_nomessages - used instead of privfolder_nomessages on tracking page to avoid layout error
Changelog
Enhancements/New Features:
- (?) Added inheritance to moderator email settings.
- Update thread info now updates thread.postuserid correctly.
- Optimized query that displays attachments.
- Optimized query that determines if you have voted in a poll.
- new button images for PM functions
- templates now have NS compliant table borders, controllable through styles CP
- all content-tables now have their width controlled via the styles CP
- all posting templates now have tabindex properties for input areas
- NEW admin/moderator CP style enhancements - further customization available by editing forums/cp.css
Bug fixes:
- (feature?) fixed search so that partial matches on the username require more than 3 characters.
- fixed bug in postings.php when merging threads (SQL error).
- fixed bug for new registrations and custom user fields not being ordered correctly.
- fixed bug where error_searchinvalidterm wasn't always being displayed when it should've been.
- fixed bug causing template sets not to be separated correctly.
- fixed bug where calendar entries with quotes in them couldn't be edited correctly.
- fixed icq/aim/yahoo displays in announcements.
- fixed a few typos.
- fixed bug with reply to pms beginning with 'Re'.
- fixed bug for birthdays before 1970 on Win32 systems or before 1902 on any system.
- fixed bug where sticky threads stay sticky after moving to another forum
- fixed layout error in PM tracking system
- fixed thread name not displayed in mod control panel->validate posts
- fixed bug with / in search highlight
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.
As you may know, the free spell checking service is being discontinued. We are looking into the alternatives at the moment, and we will have something final sorted out for the final release.
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
The fifth and final BETA version of vBulletin 2.0.0 was released into the members area this time last week. We are now proud to announce that the final furlong in the release of version 2.0 with this, the first release candidate. If all goes well, the next version should be the final!
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. 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. 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. 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. 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. 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.
We are aware that in previous vBulletin template sets, there has been a problem with Netscape not displaying table borders, and individual tables within the pages not having a width="xx" attribute set.
This is no longer the case.
All templates now have their content encased in tables with Netscape-compliant borders, and a table width attribute set. These attributes are controllable through the new styles control panel.
In order to benefit from these new features, it it strongly recommended that you revert as many of your custom templates back to the default and then re-customize them, or at least carefully study the default templates, and make the appropriate changes to your custom templates.
For those that have already customized their templates heavily, our apologies, but be consoled by the assurance that the template set in this release will not be changing in any significant way before the final release.
- forumdisplay_announcementsonly (now has daysprune selector to prevent 'losing' old threads.)
- icq (changed old online.miriablablabla address to new wwp.icq.com)
- postbit_attachmentimage - added $postid to variable for performance reasons
- postbit_attachment - added $postid to variable for performance reasons
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_searchnametooshort - error when you do not enter enough characters to do a partial username match on
- privsent_nomessages - used instead of privfolder_nomessages on tracking page to avoid layout error
Changelog
Enhancements/New Features:
- (?) Added inheritance to moderator email settings.
- Update thread info now updates thread.postuserid correctly.
- Optimized query that displays attachments.
- Optimized query that determines if you have voted in a poll.
- new button images for PM functions
- templates now have NS compliant table borders, controllable through styles CP
- all content-tables now have their width controlled via the styles CP
- all posting templates now have tabindex properties for input areas
- NEW admin/moderator CP style enhancements - further customization available by editing forums/cp.css
Bug fixes:
- (feature?) fixed search so that partial matches on the username require more than 3 characters.
- fixed bug in postings.php when merging threads (SQL error).
- fixed bug for new registrations and custom user fields not being ordered correctly.
- fixed bug where error_searchinvalidterm wasn't always being displayed when it should've been.
- fixed bug causing template sets not to be separated correctly.
- fixed bug where calendar entries with quotes in them couldn't be edited correctly.
- fixed icq/aim/yahoo displays in announcements.
- fixed a few typos.
- fixed bug with reply to pms beginning with 'Re'.
- fixed bug for birthdays before 1970 on Win32 systems or before 1902 on any system.
- fixed bug where sticky threads stay sticky after moving to another forum
- fixed layout error in PM tracking system
- fixed thread name not displayed in mod control panel->validate posts
- fixed bug with / in search highlight
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.
As you may know, the free spell checking service is being discontinued. We are looking into the alternatives at the moment, and we will have something final sorted out for the final release.
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
Comment