vBulletin 2.2.2
vBulletin 2.2.2 is a very minor release of vBulletin, including a handful of bug fixes. Unless you are experiencing problems, there is no particular need to upgrade, although staying up to date is always a good idea!
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. More detailed instructions are in the vBulletin online manual:
Upgrade instructions:
>From 1.1.x: and 2.0 betas and release candidates:
Please email me at [email protected] for full information. Please be sure to include your vBulletin customer number and password, and the URL of the forum you are upgrading.
> From 2.0.0
Upload all the files except install.php, then load up the following web pages (in this order, one at a time):
When you are done, be sure to delete all the upgradex.php scripts.
> From 2.0.1
Upload all the files except install.php, then load up the following web pages (in this order, one at a time):
When you are done, be sure to delete all the upgradex.php scripts.
> From 2.0.2
Upload all the files except install.php, then load up the following web pages (in this order, one at a time):
When you are done, be sure to delete all the upgradex.php scripts.
> From 2.0.3
Upload all the files except install.php, then load up the following web pages:
When you are done, be sure to delete all the upgradex.php scripts.
> From 2.2.0
Upload all the files except install.php, then load up the following web pages:
When you are done, be sure to delete all the upgradex.php scripts.
> From 2.2.1
Upload all the files except install.php, then load up this web page:
When you are done, be sure to delete all the upgradex.php scripts.
Changed Templates
Note: Upgrading will not overwrite any of your custom templates. If you have customized any template that is listed as 'modified' below, we seriously recommend using the 'revert' option to return them to the default template, then re-applying your customizations.
New templates
Modified templates
You can view the new templates from in the control panel by clicking on the 'view original' next to your custom template.
Changelog
Bug Fixes
In conclusion...
Get to that members area!
John
To discuss this, please post here:
<< changing error_activateaccount and error_activateaccount_change to email_activateaccount and email_activateaccount_change, respectively --tubedogg >>
vBulletin 2.2.2 is a very minor release of vBulletin, including a handful of bug fixes. Unless you are experiencing problems, there is no particular need to upgrade, although staying up to date is always a good idea!
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. More detailed instructions are in the vBulletin online manual:
Upgrade instructions:
>From 1.1.x: and 2.0 betas and release candidates:
Please email me at [email protected] for full information. Please be sure to include your vBulletin customer number and password, and the URL of the forum you are upgrading.
> From 2.0.0
Upload all the files except install.php, then load up the following web pages (in this order, one at a time):
When you are done, be sure to delete all the upgradex.php scripts.
> From 2.0.1
Upload all the files except install.php, then load up the following web pages (in this order, one at a time):
When you are done, be sure to delete all the upgradex.php scripts.
> From 2.0.2
Upload all the files except install.php, then load up the following web pages (in this order, one at a time):
When you are done, be sure to delete all the upgradex.php scripts.
> From 2.0.3
Upload all the files except install.php, then load up the following web pages:
When you are done, be sure to delete all the upgradex.php scripts.
> From 2.2.0
Upload all the files except install.php, then load up the following web pages:
When you are done, be sure to delete all the upgradex.php scripts.
> From 2.2.1
Upload all the files except install.php, then load up this web page:
When you are done, be sure to delete all the upgradex.php scripts.
Changed Templates
Note: Upgrading will not overwrite any of your custom templates. If you have customized any template that is listed as 'modified' below, we seriously recommend using the 'revert' option to return them to the default template, then re-applying your customizations.
New templates
- error_mergewithself
- error_activatedthanks
Modified templates
- printthread - add support for page splitting ($pagenav)
- modifyavatar_custom - replace some JS
- error_resetexpired - fixed html typo
- faq1,faq2,faq3 - typos
- error_moderateuser - typo
- head_newpm - fix some JS
- email_activateaccount - reminder to click link only once
- email_activateaccount_change - reminder to click link only once
- error_moderateuser - typos
- error_resetexpired - correct closing html tag
- error_wrongpassword - correcting an URL
- searchintro - typo
- modifyoptions - minor HTML change
- postbit_attachmentimage, postbit_signature - removing extra <br>
You can view the new templates from in the control panel by clicking on the 'view original' next to your custom template.
Changelog
- Printthread.php now supports multiple-page navigation, as large threads can add a nasty drain to your server. More of a bug fix really... Ensure that you revert your printthread template, or add $pagenav to your existing one to make this work properly.
Bug Fixes
- Problem with Forum Jump on 'standarderror' template
- Activation Codes not working
- Birthday problem when adding users through Admin CP
- Highlighting of terms does not carry from page to page
- Link to 'forgot your password?' is wrong from Admin CP
- Error in User CP regarding private messages
- Attachment moderation link in Mod CP is incorrect
- Database backup via Admin CP ignores 'isnull' instruction
- showgroups.php missing a column for moderators
- .png files are ignored when mass-adding smilies
- showgroups.php has no 's' after group name
- Netscape problem with avatar upload
- Guests can view other guests' threads despite "can view others' threads" being set to no
- Lost password problems
- Syntax error in Netscape 4.x
- Deleting/pruning threads exceeds max execution time
- Quoting problem
- Attachment moderation override
- "Find User" finds 0 users but does not say so
- Admin CP spelling errors
- Stange 'next page' with sticky threads
- Merging a thread with itself deletes it
- * in url breaks auto-parsing
- Problem using [ and ] in custom vB Code
- Mass-email problem
- DB error in private2.php
In conclusion...
Get to that members area!
John
To discuss this, please post here:
<< changing error_activateaccount and error_activateaccount_change to email_activateaccount and email_activateaccount_change, respectively --tubedogg >>
Comment