No announcement yet.

Quick Overview: Upgrading vBulletin Connect

This topic is closed.
This is a sticky topic.
  • Filter
  • Time
  • Show
Clear All
new posts

  • Quick Overview: Upgrading vBulletin Connect

    Note: Always perform a test upgrade before upgrading your live site. This will limit the disruption caused for your end users.

    Now that you've been using vBulletin Connect for a while, a new version has become available and you're thinking "How do I upgrade this?" That is what this tutorial is for. We will step you through upgrading vBulletin and making sure that your site has as little downtime as possible.

    Tools needed to upgrade vBulletin Connect on your server
    A moderate knowledge of HTML and CSS will be beneficial in customizing your site but is not necessary for basic customizations.


    A couple of definitions before we get started:
    • %yourdomain% should be replace with the domain name you are using for your site.
    • %forumroot% refers to the directory where vBulletin Connect is installed. If you install vBulletin Connect in the public_html or www directory, this value would be empty.
    Upgrading from previous versions of vBulletin 5 Connect
    1. Turn your vBulletin Connect site off so that users do not try to add content while you are updating the software. You can do this in the AdminCP under Settings -> Options -> Turn Your vBulletin On or Off.
    2. Using the tools provided by your hosting provider, make a backup of your current database.
    3. Using your SFTP client, upload the new files to your server. When prompted tell it to overwrite all files in the current transfer queue.
    4. With your web browser run the Upgrade Wizard. The location will be https://%yourdomain/%forumroot%/install/upgrade.php
    5. When the Upgrade Wizard is complete, you will need to delete the install folder within /core/ on your server to proceed.
    6. Log into your site and review the upgrade.
    7. When everything appears satisfactory, turn your site back on in the AdminCP under Settings -> Options -> Turn Your vBulletin On or Off.
    Upgrading via the Command Line Interface
    If you have a larger site, then you may want to run the upgrade scripts from the Command Line Interface (CLI). vBulletin can support this. After you have prepared your files using the steps above then you can log into your command line interface, usually SSH. From your SSH terminal, change into the %forumroot%/core/install directory. Then run the upgrade utility with this command line:
    php -f upgrade.php
    Upgrading from vBulletin 4.2.5 Publishing Suite

    Preparing for your upgrade
    If you are using an older version of vBulletin. It is recommended that you download and upgrade to the vBulletin 4.2.5 Publishing Suite before proceeding to vBulletin 5. This will make sure your system is at the most compatible level to be converted. Please follow these tips for the best migration:
    1. Uninstall all third-party addons in the AdminCP under Plugins & Products -> Product Manager.
    2. Leave the vBulletin Blog and vBulletin CMS products installed.
    3. All other Products are incompatible.
    4. Download your logo to be reused.
    5. Read why we recommend using a test server for the initial upgrade (below)
    6. Make a backup of your database to store locally.
    7. Delete all vBulletin 4.X files. Maintain your attachment, customavatar, and signaturepics directories in their current locations.
    8. Follow the Upgrade Steps below.

    Using a Test Server for the Initial Upgrade
    vBulletin Connect is more than an upgrade from older versions of vBulletin. It reimagines how a lot of the system functions to achieve various goals. These goals include standardized functionality across content creation, mobile device support, modularity, security, and updating programming standards. This requires a different code structure than previous versions of vBulletin and comes with a new database structure. When upgrading to vBulletin Connect, the process is more of a migration of data rather than the generally simply upgrades. For this reason we recommend upgrading a test copy first. This will allow your older version of vBulletin to remain live while you test and verify that the ugprade was successful. It will also give you and your team time to familiarize yourself with the new software so you can provide support to your end-users.

    You can read how to utilize a test server in our online manual here:

    Upgrade to vBulletin 5.
    Now that you have prepared your vBulletin 4.2.5 data to be upgraded to vBulletin Connect you can follow these steps.
    1. After Purchasing, download vBulletin Connect from the your Member's Area.
    2. Unzip the downloaded package on your local machine. Depending on your hosting provider and internet connection this can take some time.
    3. In your vBulletin files there will be a directory called upload. Enter it.
    4. Rename config.php.bkp to config.php (mv config.php.bkp config.php)
    5. Enter the /upload/core/includes directory.
    6. Rename to config.php (mv config.php)
    7. Edit config.php and change these values to match your information.
      • $config['Database']['dbname'] = 'databasename';
      • $config['Database']['tableprefix'] = '';
      • $config['Database']['technicalemail'] = '[email protected]';
      • $config['MasterServer']['servername'] = 'localhost'; // may be referred to as a host name
      • $config['MasterServer']['port'] = 3306;
      • $config['MasterServer']['username'] = 'username';
      • $config['MasterServer']['password'] = 'password';
      • Make sure that all values are to the right of the equal sign (=) and between the single quotes ('). If you do not know these values they can be obtained from your hosting provider.
      • No other values need to be changed in this file for a basic installation of vBulletin Connect.
    8. Using your SFTP Client, upload the contents of the upload directory (including all sub-directories and files) to your server. Place these files in the directory where you want to install vBulletin. If upgrading from vBulletin 3 or 4, this directory should be empty.
    9. If you store file attachments and custom avatars in the file system (both recommended), then you will need to copy these to your new directory as well.
    10. Rename htaccess.txt to .htaccess (the leading period is required). If you are using Filezilla, you can do this by right-clicking on the file and choosing rename on the context menu. This can also be done from the Windows Command Line before uploading the files to the server.
    11. Load the Upgrade Wizard in your browser. The URL should be https://%yourdomain%/%forumroot%/install/upgrade.php
    12. The Upgrade Wizard will ask for your Customer ID. This can be found in your Member's Area after logging in.
    13. Process all the steps in the Wizard. Some steps make take a long time.

    Upgrading from Older Versions of vBulletin
    For the best upgrade scenarios, we recommend that you first upgrade to vBulletin 4.2.5 and then follow the steps above.

    After Upgrading

    During the upgrade process from vBulletin 3 and vBulletin 4, the search index is not created. This improves upgrade times significantly. After upgrading, you will need to rebuild your search index. Your site can be live during the search engine rebuild but there may be performance issues while indexing occurs. There are two ways to index your site for keyword based searches.
    1. Within the AdminCP at Maintenance -> General Update Tools -> Rebuild Search Index.
    2. Using the searchindex.php located in the do_not_upload directory of your download package. The file should be placed in your %forumroot% directory and then executed from the command line. When indexing is completed, the file should be deleted from your server.

    File Cleanup

    Often when we refactor functionality within the system, it requires the removal of files that become obsolete. Due to the upgrade process, these files can build up on your server. In addition to this, each version includes its own set of javascript files with unique names. While these files shouldn't cause issues, they will take up space on your server. We recommend deleting these obsolete files from your server in order to maintain a clean file set. This requires a few steps to complete.

    1. Delete rollup javascript files that do not include your version number in the file name. These will not appear in the Suspect File Version diagnostic.

    2. Use the Suspect File Version tool in the AdminCP to delete all obsolete PHP files.
    1. In the AdminCP go to Maintenance -> Diagnostics.
    2. Run the Suspect File Versions tool.
    3. It will scan the vBulletin directories and list all files not part of vBulletin.
    4. Review these files to make sure they aren't part of a customization. If they aren't needed, then delete them with your SFTP client.

    3. If you store your CSS as Files, you would want to follow these steps:
    1. Turn off Store CSS as Files (AdminCP -> Settings -> Options -> Style & Language Options).
    2. Delete the contents of the /core/clientscript/vbulletin_css directory.
      • If you store your CSS files elsewhere, delete the contents of that location.
    3. Turn on Store CSS as Files (AdminCP -> Settings -> Options -> Style & Language Options).
    Last edited by Wayne Luke; Mon 12 Oct '20, 11:24am.
    Translations provided by Google.

    Wayne Luke
    The Rabid Badger - a vBulletin Cloud demonstration site.
    vBulletin 5 API

  • #2
    Frequent Upgrade Issues

    After installing vBulletin 5, my site is unformatted and I cannot access my AdminCP

    This means that URL Rewriting is not working on your site. Possible causes include:
    • htaccess.txt has not been renamed to .htaccess (the leading period is important)
    • mod_rewrite is not installed for Apache 2.4
    • URL Rewrite is not installed for IIS 8.5+
    • The server configuration for NGINX has not been updated. See the file for your version of PHP within the do_not_upload folder.
    • AllowOverride is not allowed in the Apache configuration file.
    • You have an .htaccess in a parent folder that configures rewrites. You need to set the RewriteBase value in vBulletin's .htaccess per the comment in the file.
    You hosting provider can help you get the ability to rewrite URLS working on your site.

    The option to rename the AdminCP is missing.

    This is by design. Renaming this directory doesn't actually provide any security to your installation. If someone has access to your Administrator username and password, they can still access the AdminCP. vBulletin Connect and vBulletin Cloud both have other methods to secure the AdminCP. These include both Two-Factor Authentication and IP Blocking built into the software.

    The system states that it is not able to find the Log In Form

    Make sure that the Log In URL is set correctly in the AdminCP. In most installations, it should be the same as the Frontend URL.

    Gateway Time

    You might experience the following error:

    Step 145 - Unexpected Text:
    <html> <head><title>504 Gateway Time-out</title></head> <body> <center><h1>504 Gateway Time-out</h1></center> <hr><center>nginx</center> </body> </html>
    This error is caused by a timeout on your server. You have three options to resolve this error:
    1. Wait 5 minutes and restart the upgrade. It should pick up where it left off.
    2. Use the command line upgrade option detailed above.
    3. Have your hosting provider temporarily remove the timeout restriction while upgrading.
    Last edited by Wayne Luke; Mon 12 Oct '20, 2:14pm.
    Translations provided by Google.

    Wayne Luke
    The Rabid Badger - a vBulletin Cloud demonstration site.
    vBulletin 5 API


    • #3
      Duplicate Index Error when processing vBulletin 3.6.0 upgrade steps.

      This issue is caused by adding an index to limit only a single reputation add per post per user. You can use this query to list the duplicate entries:

      SELECT * FROM reputation r1
        INNER JOIN reputation r2
      WHERE r1.reputationid < r2.reputationid
      AND   r1.whoadded = r2.whoadded
      AND   r1.postid  = r2.postid;
      You can use this query to delete the duplicate entries:
      DELETE r1 FROM reputation r1
        INNER JOIN reputation r2
      WHERE r1.reputationid < r2.reputationid
      AND   r1.whoadded = r2.whoadded
      AND   r1.postid  = r2.postid;
      Once the duplicate entries have been deleted, you can refresh the upgrade script page and it will continue from where the error occurred.
      Translations provided by Google.

      Wayne Luke
      The Rabid Badger - a vBulletin Cloud demonstration site.
      vBulletin 5 API


      • #4
        5.0.0 Alpha 1 step 22 - Duplicate entry on updating contenttype table.

        There are a couple of things going on here that cause this error. The primary issue is that that primary key may not be an auto-increment field. The other is the the value may start at 0 on the primary key. Due to the 0, you can't simply add an auto-increment to the table and move on. You have to handle each part separately.
        The query that triggers the error is:

        INSERT INTO contenttype(class, packageid, canplace, cansearch, cantag, canattach, isaggregator)
        SELECT 'Text', packageid, '0', '1', '1', '1', '0' FROM package where class = 'vBForum';
        To resolve, you need to drop the primary key, increment the values of contenttypeid +1, add the primary key back onto the table and then add an autoincrement value on contenttypeid.
        1. Drop Primary Key: ALTER TABLE contenttype DROP PRIMARY KEY;
        2. Update contenttypeid value if the sequence starts with 0: UPDATE contenttype SET contenttypeid = contenttypeid +1;
        3. Add the auto-increment: ALTER TABLE contenttype MODIFY contenttypeid INT NOT NULL AUTO_INCREMENT;
        4. Add the primary key index: ALTER TABLE contenttype ADD PRIMARY KEY (contenttypeid);
        Translations provided by Google.

        Wayne Luke
        The Rabid Badger - a vBulletin Cloud demonstration site.
        vBulletin 5 API


        Related Topics