Announcement

Collapse
No announcement yet.

Tips or tricks needed for upgrade

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Tips or tricks needed for upgrade

    Hi All.

    Next Saturday we planned to upgrade our forum from VB4.2.1 to VB 5+ .
    We have a rather large board.. 500.000+ messages and 7700+ users. Are there some things we have to defnitly look at before uprade to VB5.

    Our forum is running on a vps, therefor we will take a snapshot of the complete vps before we start upgrading.
    We also have VBSEO running, do we have to look at that also before upgrade ?

    If we now look at a topic the url looks like >
    http://www.chauffeursforum.nl/huisre...um-regels.html

    We do need it to look like this again..

    We hope to get tips or tricks to get it over to vb5 whitout much problems.



  • #2
    Backups, backups, did I mention backups?

    Your topic urls won't translate over from vbseo, to vB5. And you won't be able to customize them like that at all.

    Comment


    • #3
      Originally posted by emp1re View Post
      We hope to get tips or tricks to get it over to vb5 whitout much problems.
      Have you checked, if vB5 already meets your requirements? There are some features in vB4 that didn't made it into vB5 yet (e.g. the calendar, the CMS...).

      Other than that, yes, a backup is very important, but that should be a known fact to most people!

      Comment


      • #4
        Hmm.. is it a good idea to make backups ?
        Therefor we also make a snapshot of our complete vps.

        So theoretically there should be no problem to upgrade to vb5..
        And if we want the urls to lool like it does now , we do need vbseo again?

        Calendar and the CMS we actualy do not use them right now, so that should not be a problem.

        Comment


        • #5
          Originally posted by emp1re View Post
          Hmm.. is it a good idea to make backups ?
          Is this a serious question? There can always something go wrong, so yes, definetly do a backup first!

          Comment


          • #6
            There is no VBSEO for VB5 and it doesn't look like there ever will be. An upgrade to VB5 will kill all your VBSEO links.

            You could remove VBSEO from your 4.x forum, use the rewrites I believe VBSEO provides to rewrite back to standard vBulletin URLs, give it a few weeks or months for Google to index the standard URLS, and then upgrade to VB5 because the VB4 URLs will auto forward to VB5 URLs. That is a lot of time and a lot of URL rewriting though.

            Comment


            • #7
              We now installed vb5 and have a working admin panel.

              However the forum is not working. We get an http 500 error.

              Settings in admincp: core url:

              http://www.chauffeursforum.nl/vb5/core

              Does anyone of you have a clou ?


              Htaccess:

              <IfModule mod_rewrite.c>
              RewriteEngine On
              RewriteBase /vb5/

              # Redirect old install path to core.
              RewriteRule ^install/ core/install/ [NC,L]

              # Main Redirect
              RewriteCond %{REQUEST_URI} !\.(gif|jpg|jpeg|png)$
              RewriteCond %{REQUEST_FILENAME} !-f
              RewriteCond %{REQUEST_FILENAME} !-d
              RewriteRule ^(.*)$ index.php?routestring=$1 [L,QSA]

              # Because admincp is an actual directory.
              RewriteRule ^(admincp/)$ index.php?routestring=$1 [L,QSA]

              </IfModule>

              <IfModule mod_deflate.c>
              AddOutputFilterByType DEFLATE application/atom+xml \
              text/javascript \
              application/javascript \
              application/json \
              application/rss+xml \
              application/vnd.ms-fontobject \
              application/x-font-ttf \
              application/xhtml+xml \
              application/xml \
              font/opentype \
              image/svg+xml \
              image/x-icon \
              text/css \
              text/html \
              text/plain \
              text/x-component \
              text/xml
              </IfModule>

              <IfModule mod_expires.c>
              ExpiresActive On
              ExpiresByType application/x-javascript A1209600
              ExpiresByType text/javascript A1209600
              ExpiresByType application/javascript A1209600
              ExpiresByType text/css A31536000
              ExpiresByType image/x-icon A2592000
              ExpiresByType image/icon A2592000
              ExpiresByType application/x-ico A2592000
              ExpiresByType application/ico A2592000
              ExpiresByType image/gif A2592000
              ExpiresByType image/jpeg A1209600
              ExpiresByType image/jpg A1209600
              ExpiresByType image/png A1209600
              ExpiresByType application/x-shockwave-flash A1209600
              ExpiresByType font/ttf A2592000
              ExpiresByType font/otf A2592000
              ExpiresByType font/x-woff A2592000
              ExpiresByType image/svg+xml A2592000
              ExpiresByType font/truetype A2592000
              ExpiresByType font/opentype A2592000
              ExpiresByType application/x-font-woff A2592000
              ExpiresByType application/vnd.ms-fontobject A2592000
              </IfModule>

              <IfModule mod_headers.c>
              Header set Connection keep-alive
              <filesmatch "\.(ico|flv|gif|swf|eot|woff|otf|ttf|svg)$">
              Header set Cache-Control "max-age=2592000, public"
              </filesmatch>
              <filesmatch "\.(jpg|jpeg|png)$">
              Header set Cache-Control "max-age=1209600, public"
              </filesmatch>
              <filesmatch "\.(eot|woff|otf|ttf|svg)$">
              Header set Cache-Control "max-age=2592000, public"
              </filesmatch>
              # css and js should use private for proxy caching https://developers.google.com/speed/...geProxyCaching
              <filesmatch "\.(css)$">
              Header set Cache-Control "max-age=31536000, private"
              </filesmatch>
              <filesmatch "\.(js)$">
              Header set Cache-Control "max-age=1209600, private"
              </filesmatch>
              </IfModule>


              Config file in /vb5:

              <?php
              /*======================================================================*\
              || #################################################################### ||
              || # vBulletin 5 Presentation Configuration # ||
              || # ---------------------------------------------------------------- # ||
              || # All PHP code in this file is �2000-2012 vBulletin Solutions Inc. # ||
              || # This file may not be redistributed in whole or significant part. # ||
              || # ---------------- VBULLETIN IS NOT FREE SOFTWARE ---------------- # ||
              || # http://www.vbulletin.com | http://www.vbulletin.com/license.html # ||
              || #################################################################### ||
              \*======================================================================*/

              /*-------------------------------------------------------*\
              | ****** NOTE REGARDING THE VARIABLES IN THIS FILE ****** |
              +---------------------------------------------------------+
              | When making changes to the file, the edit should always |
              | be to the right of the = sign between the single quotes |
              | Default: $config['admincpdir'] = 'admincp'; |
              | Example: $config['admincpdir'] = 'myadmin'; GOOD! |
              | Example: $config['myadmin'] = 'admincp'; BAD! |
              \*-------------------------------------------------------*/


              // ****** System Paths ******

              // This setting allows you to change the name of the admin folder
              $config['admincpdir'] = 'admincp';

              // ****** Cookie Settings ******
              // These are cookie related settings.
              // This Setting allows you to change the cookie prefix
              $config['cookie_prefix'] = 'bb';


              // ****** Special Settings ******
              // These settings are only used in some circumstances
              // Please do not edit if you are not sure what they do.

              // You can ignore this setting for right now.
              $config['cookie_enabled'] = true;

              $config['report_all_php_errors'] = false;
              $config['no_template_notices'] = true;

              // This setting should never be used on a live site
              $config['no_js_bundles'] = false;

              // This setting enables debug mode, it should NEVER be used on a live site
              $config['debug'] = false;

              // Assumes default location of core.
              // These are the system paths and folders for your vBulletin files
              // This setting is for where your vbulletin core folder is



              $config['core_path'] = realpath(dirname(__FILE__)) . '/core';

              $config['php_sessions'] = false;

              /*======================================================================*\
              || ####################################################################
              || # Downloaded:
              || # CVS: $RCSfile$ -
              || ####################################################################
              \*======================================================================*/



              Config file in /vb5/core/includes


              <?php
              /*======================================================================*\
              || #################################################################### ||
              || # vBulletin Core Configuration # ||
              || # ---------------------------------------------------------------- # ||
              || # All PHP code in this file is 2000-2012 vBulletin Solutions Inc. # ||
              || # This file may not be redistributed in whole or significant part. # ||
              || # ---------------- VBULLETIN IS NOT FREE SOFTWARE ---------------- # ||
              || # http://www.vbulletin.com | http://www.vbulletin.com/license.html # ||
              || #################################################################### ||
              \*======================================================================*/

              /*----------------------------------------------------------------------*\
              | ****** NOTE REGARDING THE VARIABLES IN THIS FILE ****** |
              +------------------------------------------------------------------------+
              | If you get any errors while attempting to connect to MySQL, you will |
              | need to email your webhost because we cannot tell you the correct |
              | values for the variables in this file. |
              | |
              | When making changes to the file, the edit should always be to the |
              | right of the = sign between the single quotes |
              | Default: $config['admincpdir'] = 'admincp'; |
              | Example: $config['admincpdir'] = 'myadmin'; GOOD! |
              | Example: $config['myadmin'] = 'admincp'; BAD! |
              \*----------------------------------------------------------------------*/


              // ****** DATABASE TYPE ******
              // This is the type of the database server on which your vBulletin database
              // will be located. Valid options are mysql and mysqli, for slave support add
              // _slave to the end of the database class.
              // Try to use mysqli if you are using PHP 5 and MySQL 4.1+
              // WARNING: As of PHP 5.5.0 mysql library support is depricated. So if you are using PHP >= 5.5.0 use mysqli
              $config['Database']['dbtype'] = 'mysqli';

              // ****** DATABASE NAME ******
              // This is the name of the database where your vBulletin will be located.
              // This must be created by your webhost.
              $config['Database']['dbname'] = 'forumdatabase';

              // ****** TABLE PREFIX ******
              // Prefix that your vBulletin tables have in the database.
              $config['Database']['tableprefix'] = '';

              // ****** TECHNICAL EMAIL ADDRESS ******
              // If any database errors occur, they will be emailed to the address specified here.
              // Leave this blank to not send any emails when there is a database error.
              $config['Database']['technicalemail'] = '[email protected]';


              // ****** MASTER DATABASE SERVER NAME AND PORT ******
              // This is the hostname or IP address and port of the database server.
              // If you are unsure of what to put here, leave the default values.
              //
              // Note: If you are using IIS 7+ and MySQL is on the same machine, you
              // need to use 127.0.0.1 instead of localhost
              $config['MasterServer']['servername'] = 'localhost';
              $config['MasterServer']['port'] = 3306;

              // ****** MASTER DATABASE USERNAME & PASSWORD ******
              // This is the username and password you use to access MySQL.
              // These must be obtained through your webhost.
              $config['MasterServer']['username'] = 'username';
              $config['MasterServer']['password'] = 'Password';

              // ****** MASTER DATABASE PERSISTENT CONNECTIONS ******
              // This option allows you to turn persistent connections to MySQL on or off.
              // The difference in performance is negligible for all but the largest boards.
              // If you are unsure what this should be, leave it off. (0 = off; 1 = on)
              $config['MasterServer']['usepconnect'] = 0;



              // ****** SLAVE DATABASE CONFIGURATION ******
              // If you have multiple database backends, this is the information for your slave
              // server. If you are not 100% sure you need to fill in this information,
              // do not change any of the values here.
              $config['SlaveServer']['servername'] = '';
              $config['SlaveServer']['port'] = 3306;
              $config['SlaveServer']['username'] = '';
              $config['SlaveServer']['password'] = '';
              $config['SlaveServer']['usepconnect'] = 0;



              // ****** PATH TO ADMIN & MODERATOR CONTROL PANELS ******
              // This setting allows you to change the name of the folders that the admin and
              // moderator control panels reside in. You may wish to do this for security purposes.
              // Please note that if you change the name of the directory here, you will still need
              // to manually change the name of the directory on the server.
              $config['Misc']['admincpdir'] = 'admincp';
              $config['Misc']['modcpdir'] = 'modcp';

              // Prefix that all vBulletin cookies will have
              // Keep this short and only use numbers and letters, i.e. 1-9 and a-Z
              $config['Misc']['cookieprefix'] = 'bb';

              // ******** FULL PATH TO FORUMS DIRECTORY ******
              // On a few systems it may be necessary to input the full path to your forums directory
              // for vBulletin to function normally. You can ignore this setting unless vBulletin
              // tells you to fill this in. Do not include a trailing slash!
              // Example Unix:
              // $config['Misc']['forumpath'] = '/home/users/public_html/forums';
              // Example Win32:
              // $config['Misc']['forumpath'] = 'c:\program files\apache group\apache\htdocs\vb3';
              $config['Misc']['forumpath'] = '';

              // ******** FRONTEND (SITE) URL ******
              // On a few systems it may be necessary to input the base url.
              // This should be the same setting as $config['baseurl'] in the frontend config file
              // You do not need to fill this in unless instructed by vBulletin Support.
              // Do not include a trailing slash.
              // Example: $config['Misc']['baseurl'] = 'http://www.mysite.comt/forums';
              $config['Misc']['baseurl'] = 'http://www.chauffeursforum.nl/vb5';

              // ****** USERS WITH ADMIN LOG VIEWING PERMISSIONS ******
              // The users specified here will be allowed to view the admin log in the control panel.
              // Users must be specified by *ID number* here. To obtain a user's ID number,
              // view their profile via the control panel. If this is a new installation, leave
              // the first user created will have a user ID of 1. Seperate each userid with a comma.
              $config['SpecialUsers']['canviewadminlog'] = '1,51';

              // ****** USERS WITH ADMIN LOG PRUNING PERMISSIONS ******
              // The users specified here will be allowed to remove ("prune") entries from the admin
              // log. See the above entry for more information on the format.
              $config['SpecialUsers']['canpruneadminlog'] = '1,51';

              // ****** USERS WITH QUERY RUNNING PERMISSIONS ******
              // The users specified here will be allowed to run queries from the control panel.
              // See the above entries for more information on the format.
              // Please note that the ability to run queries is quite powerful. You may wish
              // to remove all user IDs from this list for security reasons.
              $config['SpecialUsers']['canrunqueries'] = '1,51';

              // ****** UNDELETABLE / UNALTERABLE USERS ******
              // The users specified here will not be deletable or alterable from the control panel by any users.
              // To specify more than one user, separate userids with commas.
              $config['SpecialUsers']['undeletableusers'] = '1,51';

              // ****** SUPER ADMINISTRATORS ******
              // The userids specified below will have permission to access all areas of vBulletin 5.
              // Note that this is different to vB3 & vB4 where they only had extra permissions in the
              // Admin Control Panel. Be very careful who you grant this super power to.
              // The name of this setting has changed from superadministrator to superadmins.
              // This is to avoid the accidental granting of this permission when using older config files.
              $config['SpecialUsers']['superadmins'] = '1,51';

              // ****** CACHE CONFIGURATION *****
              // Here you can configure different methods for caching items.
              // The following are the cacheing classes that can be used.
              // vB_Cache_Db - This setting stores the data in the database
              // vB_Cache_APC - This setting stores the data in APC
              // vB_Cache_Memcached - This stores the data in memcache
              // vB_Cache_Memory - This setting uses php's memory while a page is being generated.
              // Each cache area can use its own cache type.
              $config['Cache']['class'][0] = 'vB_Cache_Db'; //regular cache
              $config['Cache']['class'][1] = 'vB_Cache_Memory'; //fastest cache
              $config['Cache']['class'][2] = 'vB_Cache_Db'; //largest cache and longest life.

              // Cache options are
              // vB_Cache_Memory fastest but doesn't survive a page load.
              // vB_Cache_Db significant speed improvement and available to everyone.
              // vB_Cache_Filesystem good performance, reduces traffic and load on db server. Not available to everyone-
              // your web server must be able to write to the file system.
              // vB_Cache_Memcached excellent performance but usually only available to dedicated or virtual hosted sites.
              // vB_Cache_APC excellent performance but only available to those with APC installed, and on a single web server.
              // vB_Cache_XCache excellent performance but only available to those with XCache installed, and on a single web server.

              // ******** FILESYSTEM CACHE CONFIGURATION ******
              //If you use filesystem cache you MUST uncomment the line below.
              //set the path to somewher writeable by the web server process. This location must already exist. Please put
              // this somewhere outside the document root. Otherwise you have just created a serious security issue.
              //Don't include the final '/'

              //$config['Cache']['fileCachePath'] = '/valid/writeable/for/my/webserver';


              // ****** DATASTORE CACHE CONFIGURATION *****
              // Here you can configure different methods for caching datastore items.
              // You may need to clear this cache after installing/upgrading. You can do this either
              // in the control panel (Maintenance) or by restarting the web server.
              // vB_Datastore_Filecache - to use includes/datastore/datastore_cache.php
              // vB_Datastore_APC - to use APC
              // vB_Datastore_XCache - to use XCache
              // vB_Datastore_WinCache - to use WinCache
              // vB_Datastore_Memcached - to use a Memcache server, more configuration below
              // $config['Datastore']['class'] = 'vB_Datastore_Filecache';
              //if you use Filecache you can accept the default location, or better
              // to uncomment the next line and set a location
              // $config['Misc']['datastorepath'] = '/valid/writeable/for/my/webserver';
              // or if you have set $config['Cache']['fileCachePath' above you can do nothing and
              // it will use that location.

              // ******** DATASTORE PREFIX ******
              // If you are using a PHP Caching system (APC, XCache, eAccelerator, WinCache) with more
              // than one set of forums installed on your host, you *may* need to use a prefix
              // so that they do not try to use the same variable within the cache.
              // This works in a similar manner to the database table prefix.
              // $config['Datastore']['prefix'] = '';

              // It is also necessary to specify the hostname or IP address and the port the server is listening on
              /*
              $config['Datastore']['class'] = 'vB_Datastore_Memcached';
              $i = 0;
              // First Server
              $i++;
              $config['Misc']['memcacheserver'][$i] = '127.0.0.1';
              $config['Misc']['memcacheport'][$i] = 11211;
              $config['Misc']['memcachepersistent'][$i] = true;
              $config['Misc']['memcacheweight'][$i] = 1;
              $config['Misc']['memcachetimeout'][$i] = 1;
              $config['Misc']['memcacheretry_interval'][$i] = 15;
              */
              //If you are using Memcache you should can set a prefix. This is needed only if the memcache server is shared. If dedicated you don't need it.
              $config['Cache']['memcacheprefix'] = '';
              // ****** The following options are only needed in special cases ******

              // ****** MySQLI OPTIONS *****
              // When using MySQL 4.1+, MySQLi should be used to connect to the database.
              // If you need to set the default connection charset because your database
              // is using a charset other than latin1, you can set the charset here.
              // If you don't set the charset to be the same as your database, you
              // may receive collation errors. Ignore this setting unless you
              // are sure you need to use it.
              // $config['Mysqli']['charset'] = 'utf8';

              // Optionally, PHP can be instructed to set connection parameters by
              // reading from the file named in 'ini_file'. Please use a full path to
              // the file.
              // Example:
              // $config['Mysqli']['ini_file'] = 'c:\program files\MySQL\MySQL Server 4.1\my.ini';
              $config['Mysqli']['ini_file'] = '';

              // ******** IMAGE PROCESSING OPTIONS ********
              // Images that exceed either dimension below will not be resized by vBulletin.
              // If you need to resize larger images, alter these settings.
              $config['Misc']['maxwidth'] = 2592;
              $config['Misc']['maxheight'] = 1944;

              // ******** SPECIAL SETTINGS ********
              // The following are settings/permissions that are not normally used but
              // are here for reference. Please be careful using them. Do not enable or
              // uncomment without understanding what they do first.

              // This allows you to disable modifications and extensions to the software.
              // If your site is not functioning well after installing or using a third
              // party modification, please enable this.
              // define("DISABLE_HOOKS", true);

              // This allows you to shut down all mail that is being sent by vBulletin.
              // This is useful for test environments
              // define("DISABLE_MAIL", true);

              // This allows you to enter debug mode, which is for support or development
              // to help understand how pages are built. This should NEVER be enabled in
              // a live environment.
              // $config['Misc']['debug'] = true;

              // This enables debug logging. The debuglogger is controlled from the
              // file core/includes/xml/logger.xml. This is safe to run on a live
              // environment, assuming the log location is secure, however it may
              // impact peformance to have the logging on.
              // $config['Misc']['debuglogging'] = true;

              // The ports in this array will not be appended to generated urls
              // This is useful if you run vB on a non-standard port, e.g. with Varnish in front
              // $config['Misc']['backendports'] = array();

              /*======================================================================*\
              || ####################################################################
              || # Downloaded: 00:00, Thur Oct 15th 2015
              || # CVS: $RCSfile$ - $Revision: 73941 $
              || ####################################################################
              \*======================================================================*/

              Comment


              • #8
                Please use the default .htaccess supplied with 5.0.4 (but edit to supply your RewriteBase).

                I see vB4 at your site right now.

                Please don't PM or VM me for support - I only help out in the threads.
                vBulletin Manual & vBulletin 4.0 Code Documentation (API)
                Want help modifying your vbulletin forum? Head on over to vbulletin.org
                If I post CSS and you don't know where it goes, throw it into the additional.css template.

                W3Schools &lt;- awesome site for html/css help

                Comment


                • #9
                  Originally posted by emp1re View Post

                  We hope to get tips or tricks to get it over to vb5 whitout much problems.

                  Yeah don't.

                  Comment

                  Related Topics

                  Collapse

                  Working...
                  X