problem to install

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • MrCriticalRx
    New Member
    • Jan 2016
    • 27
    • 5.1.x

    problem to install

    help
  • Mark.B
    vBulletin Support
    • Feb 2004
    • 24287
    • 6.0.X

    #2
    You need to ensure you have configured /core/includes/config.php with the database details and credentials.

    Here are the instructions for a manual installation of vB5, please be sure to carry out EVERY step:

    1. Download the newest vB5 release from the members' area. https://members.vbulletin.com

    2. Unzip the files and go to the "upload" folder.

    3. You need to rename this file:

    htaccess.txt

    To:

    .htaccess
    (Note the 'dot' at the start)

    4. You need to rename this file:

    /config.php.bkp

    To:

    /config.php

    Then, you need to rename this file:

    /core/includes/config.php.new

    To:

    /core/includes/config.php

    Then, in that file, you need to complete the following fields:

    $config['Database']['dbname'] = 'forum';
    Change forum to whatever your database name is.

    $config['Database']['technicalemail'] = '[email protected]';
    Change the email address to your own.

    $config['MasterServer']['username'] = 'root';
    Change root to the database username

    $config['MasterServer']['password'] = '';
    Enter the database password inside the '' marks.

    All other fields should be left as default, unless your database is on a separate server, in which case this will need changing:

    $config['MasterServer']['servername'] = 'localhost';

    5. Upload all files to your server/webspace/whatever and browse to yourforumpath.com/core/install/install.php.

    6. Enter your customer number and the installation will proceed.

    7. Delete the /core/install directory after the installation has finished.
    MARK.B
    vBulletin Support
    ------------
    My Unofficial vBulletin 6.0.0 Demo: https://www.talknewsuk.com
    My Unofficial vBulletin Cloud Demo: https://www.adminammo.com

    Comment

    • MrCriticalRx
      New Member
      • Jan 2016
      • 27
      • 5.1.x

      #3
      now An error has occurred with your database. Please contact vBulletin Support for assistance.

      Module: install, Step 3 Database Error:1709

      Index column size too large. The maximum column size is 767 bytes.

      Query:
      CREATE TABLE node ( nodeid INT UNSIGNED NOT NULL AUTO_INCREMENT PRIMARY KEY, routeid INT UNSIGNED NOT NULL, contenttypeid SMALLINT NOT NULL, publishdate INTEGER, unpublishdate INTEGER, userid INT UNSIGNED , groupid INT UNSIGNED, authorname VARCHAR(100), description VARCHAR(1024), title VARCHAR(512), htmltitle VARCHAR(512), parentid INTEGER NOT NULL, urlident VARCHAR(512), displayorder SMALLINT, starter INT NOT NULL DEFAULT '0', created INT, lastcontent INT NOT NULL DEFAULT '0', lastcontentid INT NOT NULL DEFAULT '0', lastcontentauthor VARCHAR(100) NOT NULL DEFAULT '', lastauthorid INT UNSIGNED NOT NULL DEFAULT '0', lastprefixid VARCHAR(25) NOT NULL DEFAULT '', textcount mediumint UNSIGNED NOT NULL DEFAULT '0', textunpubcount mediumint UNSIGNED NOT NULL DEFAULT '0', totalcount mediumint UNSIGNED NOT NULL DEFAULT '0', totalunpubcount mediumint UNSIGNED NOT NULL DEFAULT '0', ipaddress CHAR(15) NOT NULL DEFAULT '', showpublished SMALLINT UNSIGNED NOT NULL DEFAULT '0', oldid INT UNSIGNED, oldcontenttypeid INT UNSIGNED, nextupdate INTEGER, lastupdate INTEGER, featured SMALLINT NOT NULL DEFAULT 0, CRC32 VARCHAR(10) NOT NULL DEFAULT '', taglist MEDIUMTEXT, inlist SMALLINT UNSIGNED NOT NULL DEFAULT '1', protected SMALLINT UNSIGNED NOT NULL DEFAULT '0', setfor INTEGER NOT NULL DEFAULT 0, votes SMALLINT(5) UNSIGNED NOT NULL DEFAULT '0', hasphoto SMALLINT NOT NULL DEFAULT '0', hasvideo SMALLINT NOT NULL DEFAULT '0', deleteuserid INT UNSIGNED, deletereason VARCHAR(125), open SMALLINT NOT NULL DEFAULT '1', showopen SMALLINT NOT NULL DEFAULT '1', sticky TINYINT(1) NOT NULL DEFAULT '0', approved TINYINT(1) NOT NULL DEFAULT '1', showapproved TINYINT(1) NOT NULL DEFAULT '1', viewperms TINYINT NOT NULL DEFAULT 2, commentperms TINYINT NOT NULL DEFAULT 1, nodeoptions INT UNSIGNED NOT NULL DEFAULT 138, prefixid VARCHAR(25) NOT NULL DEFAULT '', iconid SMALLINT NOT NULL DEFAULT '0', public_preview SMALLINT NOT NULL DEFAULT '0', INDEX node_lastauthorid(lastauthorid), INDEX node_lastcontent(lastcontent), INDEX node_textcount(textcount), INDEX node_ip(ipaddress), INDEX node_pubdate(publishdate, nodeid), INDEX node_unpubdate(unpublishdate), INDEX node_parent(parentid), INDEX node_nextupdate(nextupdate), INDEX node_lastupdate(lastupdate), INDEX node_user(userid), INDEX node_oldinfo(oldcontenttypeid, oldid), INDEX node_urlident(urlident), INDEX node_sticky(sticky), INDEX node_starter(starter), INDEX node_approved(approved), INDEX node_ppreview(public_preview), INDEX node_showapproved(showapproved), INDEX node_ctypid_userid_dispo_idx(contenttypeid, userid, displayorder), INDEX node_setfor_pubdt_idx(setfor, publishdate), INDEX prefixid (prefixid, nodeid), INDEX nodeid (nodeid, contenttypeid), INDEX contenttypeid_parentid (contenttypeid, parentid), INDEX node_featured(featured), INDEX node_inlist(inlist), INDEX created(created), INDEX totalcount(totalcount), INDEX showpublished(showpublished) ) ENGINE = InnoDB

      Script: install
      Step: 3

      Comment

      • Wayne Luke
        vBulletin Technical Support Lead
        • Aug 2000
        • 74111

        #4
        Ask your hosting provider to enable 'innodb_large_prefix' on your MySQL installation. This should be on by default in MySQL 5.7.7 and higher.
        Translations provided by Google.

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

        Comment

        • MrCriticalRx
          New Member
          • Jan 2016
          • 27
          • 5.1.x

          #5
          i have 10.1.31-MariaDB but nothing

          Comment

          • Mark.B
            vBulletin Support
            • Feb 2004
            • 24287
            • 6.0.X

            #6
            You still need to do what was suggested above.
            MARK.B
            vBulletin Support
            ------------
            My Unofficial vBulletin 6.0.0 Demo: https://www.talknewsuk.com
            My Unofficial vBulletin Cloud Demo: https://www.adminammo.com

            Comment

            • Wayne Luke
              vBulletin Technical Support Lead
              • Aug 2000
              • 74111

              #7
              MariaDB is just a clone of MySQL with a few patches. It has the exact same settings and features. As far as vBulletin is concerned, it is MySQL. There is no difference.
              Translations provided by Google.

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

              Comment

              • MrCriticalRx
                New Member
                • Jan 2016
                • 27
                • 5.1.x

                #8
                again An error has occurred with your database. Please contact vBulletin Support for assistance.

                Module: install, Step 3 Database Error:1709

                Index column size too large. The maximum column size is 767 bytes.

                Query:
                CREATE TABLE node ( nodeid INT UNSIGNED NOT NULL AUTO_INCREMENT PRIMARY KEY, routeid INT UNSIGNED NOT NULL, contenttypeid SMALLINT NOT NULL, publishdate INTEGER, unpublishdate INTEGER, userid INT UNSIGNED , groupid INT UNSIGNED, authorname VARCHAR(100), description VARCHAR(1024), title VARCHAR(512), htmltitle VARCHAR(512), parentid INTEGER NOT NULL, urlident VARCHAR(512), displayorder SMALLINT, starter INT NOT NULL DEFAULT '0', created INT, lastcontent INT NOT NULL DEFAULT '0', lastcontentid INT NOT NULL DEFAULT '0', lastcontentauthor VARCHAR(100) NOT NULL DEFAULT '', lastauthorid INT UNSIGNED NOT NULL DEFAULT '0', lastprefixid VARCHAR(25) NOT NULL DEFAULT '', textcount mediumint UNSIGNED NOT NULL DEFAULT '0', textunpubcount mediumint UNSIGNED NOT NULL DEFAULT '0', totalcount mediumint UNSIGNED NOT NULL DEFAULT '0', totalunpubcount mediumint UNSIGNED NOT NULL DEFAULT '0', ipaddress CHAR(15) NOT NULL DEFAULT '', showpublished SMALLINT UNSIGNED NOT NULL DEFAULT '0', oldid INT UNSIGNED, oldcontenttypeid INT UNSIGNED, nextupdate INTEGER, lastupdate INTEGER, featured SMALLINT NOT NULL DEFAULT 0, CRC32 VARCHAR(10) NOT NULL DEFAULT '', taglist MEDIUMTEXT, inlist SMALLINT UNSIGNED NOT NULL DEFAULT '1', protected SMALLINT UNSIGNED NOT NULL DEFAULT '0', setfor INTEGER NOT NULL DEFAULT 0, votes SMALLINT(5) UNSIGNED NOT NULL DEFAULT '0', hasphoto SMALLINT NOT NULL DEFAULT '0', hasvideo SMALLINT NOT NULL DEFAULT '0', deleteuserid INT UNSIGNED, deletereason VARCHAR(125), open SMALLINT NOT NULL DEFAULT '1', showopen SMALLINT NOT NULL DEFAULT '1', sticky TINYINT(1) NOT NULL DEFAULT '0', approved TINYINT(1) NOT NULL DEFAULT '1', showapproved TINYINT(1) NOT NULL DEFAULT '1', viewperms TINYINT NOT NULL DEFAULT 2, commentperms TINYINT NOT NULL DEFAULT 1, nodeoptions INT UNSIGNED NOT NULL DEFAULT 138, prefixid VARCHAR(25) NOT NULL DEFAULT '', iconid SMALLINT NOT NULL DEFAULT '0', public_preview SMALLINT NOT NULL DEFAULT '0', INDEX node_lastauthorid(lastauthorid), INDEX node_lastcontent(lastcontent), INDEX node_textcount(textcount), INDEX node_ip(ipaddress), INDEX node_pubdate(publishdate, nodeid), INDEX node_unpubdate(unpublishdate), INDEX node_parent(parentid), INDEX node_nextupdate(nextupdate), INDEX node_lastupdate(lastupdate), INDEX node_user(userid), INDEX node_oldinfo(oldcontenttypeid, oldid), INDEX node_urlident(urlident), INDEX node_sticky(sticky), INDEX node_starter(starter), INDEX node_approved(approved), INDEX node_ppreview(public_preview), INDEX node_showapproved(showapproved), INDEX node_ctypid_userid_dispo_idx(contenttypeid, userid, displayorder), INDEX node_setfor_pubdt_idx(setfor, publishdate), INDEX prefixid (prefixid, nodeid), INDEX nodeid (nodeid, contenttypeid), INDEX contenttypeid_parentid (contenttypeid, parentid), INDEX node_featured(featured), INDEX node_inlist(inlist), INDEX created(created), INDEX totalcount(totalcount), INDEX showpublished(showpublished) ) ENGINE = InnoDB

                Script: install
                Step: 3

                Comment

                • Wayne Luke
                  vBulletin Technical Support Lead
                  • Aug 2000
                  • 74111

                  #9
                  The problem is exactly the same as before. The fix is the same as I already posted. Once that change is made, the database server needs to be rebooted for it to change effect.
                  Translations provided by Google.

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

                  Comment

                  • MrCriticalRx
                    New Member
                    • Jan 2016
                    • 27
                    • 5.1.x

                    #10
                    talking whit my suport he say
                    He revisado y soportamos innodb_large_prefix en nuestro hosting compartido, comenta eso con el soporte de vBulletin y de seguro te darán más soluciones respecto a cómo instalarlo con nosotros.

                    You have reviewed and supported innodb_large_prefix in our shared hosting, comment that with the support of vBulletin and for sure they will give you more solutions regarding how to install it with us.

                    Comment

                    • Wayne Luke
                      vBulletin Technical Support Lead
                      • Aug 2000
                      • 74111

                      #11
                      If they don't support innodb_large_prefix, you will have to find a new hosting provider. That is the only solution.
                      Translations provided by Google.

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

                      Comment

                      • MrCriticalRx
                        New Member
                        • Jan 2016
                        • 27
                        • 5.1.x

                        #12
                        nono they support it

                        Comment

                        • Wayne Luke
                          vBulletin Technical Support Lead
                          • Aug 2000
                          • 74111

                          #13
                          The error message states it is not supported on the database server you are using. If it were supported, this error wouldn't occur.
                          Translations provided by Google.

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

                          Comment

                          • MrCriticalRx
                            New Member
                            • Jan 2016
                            • 27
                            • 5.1.x

                            #14
                            which version of php requires the latest version of vbulletin

                            Comment

                            • Wayne Luke
                              vBulletin Technical Support Lead
                              • Aug 2000
                              • 74111

                              #15
                              This isn't a PHP issue. This a database issue. For PHP, we require a minimum version of 5.6.30. We require a minimum of MySQL 5.5.18 or MariaDB 10. Using MySQL 5.7 provides the best performance at this time.
                              Translations provided by Google.

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

                              Comment

                              Related Topics

                              Collapse

                              Working...