vBulletin 4.2 - Readme

Member's Area • Community Forums • Technical Support • Documentation

# vBulletin 4.2 - Readme

## What's new in vBulletin 4.2?

vBulletin 4.2 includes a variety of new features to make owning and administrating a vBulletin Forum easier and more enjoyable. These features include:

- Activity Stream - Up to the minute streams of the content you choose. Supports Articles, Threads, Visitor Messages, Social Groups, Albums and more. Activity Streams show as a main community wide stream that is filterable by the end user so they only see the content they want to see. Activity Streams are also available on the personal profile of users so friends can keep up with the activity of each other quickly and easily. For more information see the JIRA entry*. For the documentation on the Activity Stream, visit the vBulletin.com CMS.
- Navigation Manager - Gain full control over your community's navigation bar and tabs. Use the Navigation Manager to create new tabs, links, and sub-menus for your site. This allows you to highlight the parts that are important to your community. Addon Developers can easily tie into the Navigation Manager giving you complete control over the links they provide without always resorting to plugins or editing templates. For more information see the JIRA entry*. For the Documentation on the Navigation Manager see the vBulletin.com CMS.
- Various Minor Features For more information see the JIRA entry*.
  - Members who have Visited Today
  - Cron-based Batch Email Sending
  - UserCP Reputation Display
  - Reputation Notification
  - User Profile Reputation Display
  - Who has Read a Thread
  - Doublepost Prevention
  - Enhanced Reputation Checks
  - Reverse Proxy Support (JIRA*)

Top

## vBulletin4 Installation and Upgrades

### Installing a new vBulletin 4 Community

1. Open the 'upload/includes/' folder. In this you will find config.php.new. You need to rename this to config.php and then open it in a text editor.

   We recommend using Wordpad on Windows and TextEdit on OS X.

2. The config.php file is commented throughout, so you should be able to work out what values to enter for the variables yourself.
   The values for the config.php file are described in detail here.

3. When you have finished, save the file in the ASCII TEXT file format. Make sure you are not saving in an RTF or UTF8 format.

4. Using your FTP client upload the entire contents of the 'upload/' folder to your web server. You must upload these files into your 'public_html' or web root directory. If you don't have a public_html directory look for a 'www' directory or ask your hosting provider where you should upload your files.

   You can see a video tutorial on using FileZilla (download), a popular FTP client, to upload files on our community site.

5. When this is done, point your browser at http://www.example.com/install/install.php (where www.example.com/ is the URL of your vBulletin)

6. The install will ask for your Customer Number to login.

7. Once you are logged in you can proceed to follow the instructions on the screen. The installation wizard is automated and will only stop when it needs more information from you. If you wish to see what it is doing, click on the details button. This will expand the wizard and show every step as it completes.

8. When the installation wizard is complete, it will ask if you want to go to the Admin Control Panel. Before proceeding to the Admin Control Panel, you must delete the 'install/install.php'file from your webserver. You may then enter the control panel and start working on your new vBulletin!

9. The entire installation process should take no more than five minutes after uploading the files.

10. For a complete description of how to install vBulletin 4, see the installation section of the vBulletin Manual.

You can view a video tutorial on the installation process here on our community site.

Top

### vBulletin4 Upgrades

Before starting any upgrade to a new version of vBulletin the first step that should be done is to take complete a database backup. You can find more information about backing up here: Database Backup

You can view video tutorials on creating database backups here: phpMyAdmin, cPanel, SSH Command Line

After backing up it may be a good idea to also disable your plugins, especially between major versions of vBulletin. This allows you to test your new upgrade without conflicts from addons. You can do this in a few ways:

- Disable from the config.php file: define("DISABLE_HOOKS",1);
- Disable from the AdminCP: AdminCP > Settings > Options > Plugin/Hook System
- Disable one by one via the Product Manager: AdminCP > Plugins & Products > Manage Products

Make sure to backup your includes/config.php file. There is no need to edit this file when doing upgrades unless the Upgrade Script tells you to do so.

Below you will find the quick step guides for upgrading from each version. For a complete description of how to upgrade from a previous version of vBulletin to the latest version, see the upgrade section of the vBulletin Manual.

Top

#### Upgrading from vBulletin 4.x.x

1. Close your board via the Admin Control Panel.

2. Delete install/install.php from your upload directory

3. Upload all remaining files from the 'upload/' folder in the zip.

4. Open your browser and point the URL to your forums, e.g. http://www.example.com/install/upgrade.php (where www.example.com/ is the URL of your vBulletin). Make sure to upload the files into your previous installation directory as appropriate (e.g. /forums/). The Upgrade Wizard will determine your vBulletin version and jump forward to the appropriate upgrade step.

   Some steps can take a long time to process. Please be patient.

5. If any errors occur, copy the error and please contact support. DO NOT continue with the upgrade. Doing so may cause irreversible damage to the database.

6. Follow the instructions on the screen. Make sure you proceed until you are redirected to your Admin Control Panel. Here, you can reopen your board.

You can view a video tutorial on the upgrade process here on our community site. While the video shows an upgrade from vBulletin 3.X to 4.x, it is still applicable for later upgrades as well.

Top

#### Upgrading from vBulletin versions 3.6.0 through 3.8.7.

When upgrading to vBulletin 4.X from vBulletin 3.X, there are a few incompatibilities that can affect your upgrade and functionality.

- vBulletin 4.x.x uses a new Template and Stylevar engine. This means your previous styles are not compatible with vBulletin 4.x.x. When you upgrade, they will be disabled and a newstyle will be created and set as the default style.
- Any plugins and products you have installed will need to be upgraded as well. Most vBulletin 3.X products are not compatible with vBulletin 4.
- It is recommend that you upgrade a secondary development installation first.

1. Close your board via the Admin Control Panel.

2. Delete install/install.php from your upload directory

3. Upload all remaining files from the 'upload/' folder in the zip.

4. Open your browser and point the URL to your forums, e.g. http://www.example.com/install/upgrade.php (where www.example.com/ is the URL of your vBulletin). Make sure to upload the files into your previous installation directory as appropriate (e.g. /forums/). The Upgrade Wizard will determine your vBulletin version and jump forward to the appropriate upgrade step.

   Some steps can take a long time to process. Please be patient.

5. If any errors occur, copy the error and please contact support. DO NOT continue with the upgrade. Doing so may cause irreversible damage to the database.

6. Follow the instructions on the screen. Make sure you proceed until you are redirected to your Admin Control Panel. Here, you can reopen your board.

You can view a video tutorial on the upgrade process here on our community site.

Top

#### Upgrading from older versions of vBulletin

When upgrading from older versions there are several upgrade scripts that need to be run. These need to be run in a specific order.

1.1.x to 2.2.0 - Those upgrade scripts are available here: http://members.vbulletin.com/getupgrade.php
You need to upload these scripts to the "admin" directory of a vB2 folder. You need to run them manually in sequence: admin/upgrade##.php

2.2.0 to 2.2.9 - These upgrade scripts are included with any vB2 zip file 2.2.9 or greater. You need to run them manually in sequence: admin/upgrade##.php

2.2.9 to 3.6.x - Upload the files for 3.6.x and run the "install/upgrade.php" script. It will automatically take you through all appropriate upgrade scripts up to 3.6.x.

3.6.x up - Upload your vBulletin 4.2.X files and follow the steps at Upgrading from version vBulletins 3.5.4 through 3.8.7.

When the upgrade scripts are complete, the system may tell you to delete some files, and then redirect you to the Admin Control Panel. You should log in to this and proceed to the Maintenance section of the control panel, where you should run the General Update tools. The Rebuild Search Index and Rebuild Statistics will take a quite a long time to run on larger boards.

If you need more assistance in upgrading your older version please create a new thread in the vBulletin.com Forums*.

Top

#### Using the Command Upgrade Tools

Starting with vBulletin 4.0.9, you can run the upgrade script from the command line and remove the overhead of your browser and HTTP calls. The command line interface is designed to specifically help big boards with the upgrade process and to eliminate the time caused by HTTP interaction. you will need to run the upgrade as the user that the webserver runs under. This will prevent permission problems from occurring later if you store CSS as files. To run this interface go to your install directory and execute:

    sudo -u <user> php -f upgrade.php

You can view a video tutorial on command line upgrades on our community site.

Top

#### After Your Upgrade

After the upgrade of your vBulletin System, there may be additional steps that need to be completed in your Admin Control Panel. These will be listed as News Items and have links to address them. These steps may require updating counters, rebuilding indexes and so forth. Please make sure to follow the instructions on the screen carefully and process all steps listed on your Admin Control Panel home page.

##### Out of Date Templates

Out of date templates occur when you have customized your vBulletin Templates to apply HTML effects to the page or modify functionality. When you perform the upgrade, vBulletin will import a new version of the default templates. The system will then attempt to merge any changes into your customized templates. Most of the time the merge is successful. However occasionally, the merge will fail due to conflicts. When this happens your customized template will be listed as out of date as a warning to you. You will need to compare your custom template with the new default and manually apply any necessary changes. For more information about this process please see our article on Template Merging and 3-Way Comparison.

##### Out of Date Phrases

There are times when phrasing needs to be updated to fix errors, grammar or wording. When this happens it can result in customized phrases becoming out of date. To resolve this, you would need to use the Find Out of Date Phrases tool to compare your customized phrases with the new ones. Most of the time, you'll be able to continue using your customized phrases. However if they result in an error or bug, you should revert them and recustomize them from the beginning. For more information on Out of Date phrase see the vBulletin Manual.

Top

## Importing into vBulletin (ImpEx)

vBulletin Solutions provides a series of import modules called ImpEx. These modules will allow you to import a variety of other systems into your new vBulletin Community. Please read the documentation completely before attempting an import.

ImpEx is not an upgrade system and use of it in this manner is not supported. If you use ImpEx to attempt an upgrade of your community, you can cause irreparable harm to your links, content ids and more within the vBulletin system.

Here is the Online Manual for the Impex system: https://www.vbulletin.com/docs/html/impex

Make sure to view the 'After the Import' instructions here: https://www.vbulletin.com/docs/html/impex_cleanup

Top

## Language Support

vBulletin includes a Language Manager in the admin control panel. This allows you to translate the vBulletin interface into your own language or several languages, as well as being able to import language packs created others. Your users can then select the language they prefer to view the board in. We do have a Languages & Phrases forum where you can find packs donated by our customers and also receive help for creating your own: http://www.vbulletin.com/forum/forumdisplay.php?f=87*

Also, here's the forum containing downloads of the current Language Packs made available by our customers: http://www.vbulletin.com/forum/forumdisplay.php?f=96*

Please note, the Language Management System only covers the board text and not individual posts. The posts themselves will be displayed in the original language they were written in.

Top

## vBulletin 4 Download Package Contents

When you uncompress your vBulletin download you will see a variety of files and directories. Here is a description of these contents.

do_not_upload/
  This folder contains administration files. The files located in this directory are used for advanced installation instructions and support functions. Only use these files if directed to do so by a support technician, or if you know what you're doing.
  - blog - This directory contains cms component files that are used when you want to run the vBulletin Blog within a subdirectory.
  - cms - This directory contains the cms component files that are used when you want to run the vBulletin CMS within a subdirectory.
  - forum - This directory contains forum component files that are used when you want to run the vBulletin Forum within a subdirectory.
  - rewrite - This directory contains the rewrite instructions for the mod_rewrite friendly urls. It has subdirectories for Apache2 and IIS 7+ as well as additional subdirectories if you installed your components in a subdirectory.
  - tools.php - A script to help you fix (login) problems and rebuild caches for usergroups, bitfields, etc. Do not upload this to the server unless you need to use it.
  - searchshell.php - a php shell script to rebuild the search index from the console. This is quicker than the web mode in the Admin CP and useful for large forum upgrades.
  - vb_backup.sh - a bash shell script to backup the database, especially handy for nightly backups when set up as a crontab or scheduled task.
upload/
  This folder contains all the files from the vBulletin forum software that you need to upload when installing or upgrading. All the files inside this folder are required to run vBulletin, see the below installation and/or upgrade instructions on which files to modify and/or to delete after an installation or upgrade. While there are too many files to list, here is a brief overview of the main folders in this directory.
  - admincp - Contains the main entry point to the Admin Control Panel.
  - archive - A pseudo-archive for search engines that don't work with dynamic pages.
  - clientscript - Contains the Javascript and extra CSS needed for the vBulletin engine.
  - customavatars - Ships empty but provides a location for the storage of custom avatars. Use depends on your settings in the software.
  - customgroupicons - Ships empty but provides a location for the storage of custom social group icons. Use depends on your settings in the software.
  - customprofilepics - Ships empty but provides a location for the storage of custom profile images. Use depends on your settings in the software.
  - forumrunner - Contains the files necessary for the Forum Runner mobile apps to function properly.
  - images - contains all the images that the default vBulletin style needs to work properly.
  - includes - Contains the different PHP and XML files required for the vBulletin engine to work properly. Also contains the majority of the vBulletin API.
  - install - Contains the installation and upgrade wizards as well as the default style, language and settings for the software.
  - modcp - The moderation control panel. A light version of the Admin CP that gives moderators access to basic functions they need. Most functions are also duplicated via inline moderation tools in the software.
  - packages - Many different base classes that the vBulletin engine uses to know how to interact with different content types and functionality.
  - signaturepics - Ships empty but provides a location for the storage of custom signature images. Use depends on your settings in the software.
  - vb - The vBulletin Engine. Contains the classes and software necessary for the engine to work. The files here work in conjunction with the includes and packages directory to do the bulk of the processing in vBulletin.
license_agreement.html
  All customers must agree to this license agreement prior to downloading and using the vBulletin software, read it.
vb4_readme.html
  HTML version of this installation/upgrade/information file
vbulletin-smilies.pdf
  A PDF file of the smilies currently shipping with the system.

Top

## Appendix: More information

Here are some important links with more information:

- The vBulletin Online Manual - With installation and upgrade instructions, indepth feature and options information and more technical documents.
- The vBulletin Members Area^ - Download area for vBulletin, private customer support tickets area, etc.
- The vBulletin Support Forums* - Free priority support forums, latest announcements with indepth release details, etc.
- vBulletin Release Changelog^ - The changelog links to the release announcement for every version of vBulletin. Release announcements contain specific information about that release including updated files, updated templates, links to bug fix lists and more.
- vBulletin JIRA Changelog* - Similar to the above but a concise list of bugs, enhancements and other issues applied to vBulletin 4 by version.

* Registration and a valid license are required to participate in the vBulletin Community Forums and JIRA. ^ Access to the Member's Area requires a valid Customer Number and password.