Announcement

Collapse
No announcement yet.

vBulletin and php 7

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts
    Wayne Luke
    vBulletin Technical Support Lead

  • Wayne Luke
    replied
    Yes. It is part of your MySQL configuration. I linked to the MySQL documentation on it above.

    Leave a comment:

  • sexypbobb
    Member

  • sexypbobb
    replied
    I got a dedicated server. Would i be able to update this variable myself like i mentioned in my previous post?
    sexypbobb
    Member
    Last edited by sexypbobb; Wed 27 Nov '19, 9:24pm.

    Leave a comment:

  • sexypbobb
    Member

  • sexypbobb
    replied
    Is there a command I can run on phpmyadmin for MySQL? Something like
    --innodb-large-prefix[={OFF|ON}

    ?
    sexypbobb
    Member
    Last edited by sexypbobb; Wed 27 Nov '19, 5:39pm.

    Leave a comment:

  • Wayne Luke
    vBulletin Technical Support Lead

  • Wayne Luke
    replied
    Your hosting provider needs to step in here. a 250 byte string can take between 250 and 1000 bytes to index. We can't change this. They need to set the variables so that longer keys are allowed.

    Leave a comment:

  • sexypbobb
    Member

  • sexypbobb
    replied
    I checked phpMyadmin. The tables are MyISAM

    Leave a comment:

  • Wayne Luke
    vBulletin Technical Support Lead

  • Wayne Luke
    replied
    You really can't get around this without changing variables on the server. You have to force newer software to work with vBulletin 3.8.11. On older servers, vBulletin 3.8.X would use MyISAM tables. They wouldn't have this problem. In MySQL 5.6, the default table engine was switched to INNODB which does this have this problem. If you set your database server to use MyISAM as the default engine, then you should be able to install the software without changing any other variables for MySQL. I can't make any guarantees on that though. If that doesn't work, you can try MySQL 5.5 if the hosting provider allows it.

    The fact of the matter is you're using software that is 15 years old (vBulletin 3 was released in 2004) and was not developed for modern servers. While we have patched and fixed bugs to try and update it, the architecture hasn't changed and new versions of Server software are also updating and patching issues. The software has been end of life for over a year now. Issues like this are going to become more prevalent going forward as hosting companies update their servers. For instance, PHP 7.1 reaches end of life in 5 days (December 1st, 2019). This means that hosting providers will start upgrading to more secure versions of PHP.

    If this is a new community, why the aversion to vBulletin 5? You have a license. It will work better on newer servers, has hundreds of new features, is easier to customize, modern, works on mobile devices, etc...

    Leave a comment:

  • sexypbobb
    Member

  • sexypbobb
    replied
    I appologise. Im not a newbie with this stuff but im also not an expert

    Leave a comment:

  • sexypbobb
    Member

  • sexypbobb
    replied
    Which mysql version is really the best where i dont have to edit variables? I have had this 3.8 version installed on other servers in the past and never had a problem with mysql tho i dont remember which version i was using

    Leave a comment:

  • sexypbobb
    Member

  • sexypbobb
    replied
    When I delete the tables with the install script it loops into creating them again

    Leave a comment:

  • sexypbobb
    Member

  • sexypbobb
    replied
    I have 5.6.43 and it aint working. I get the error at the noticecriteria table creation point

    Leave a comment:

  • Wayne Luke
    vBulletin Technical Support Lead

  • Wayne Luke
    replied
    MySQL 5.7.X is probably the limit. 8.0 includes new reserved words that will cause problems with vBulletin 3.8.11 and 4.2.5. I haven't tested a 3.8.11 install recently.

    Leave a comment:

  • sexypbobb
    Member

  • sexypbobb
    replied
    Which MySQL version do you recommend? Anything above 5.7.7?

    Leave a comment:

  • Wayne Luke
    vBulletin Technical Support Lead

  • Wayne Luke
    commented on 's reply
    This will not make vBulletin 3.8.11 compatible with any version of PHP higher than PHP 7.1.X.
  • Wayne Luke
    vBulletin Technical Support Lead

  • Wayne Luke
    replied
    Originally posted by sexypbobb View Post
    MySQL Error : Specified key was too long; max key length is 1000 bytes
    This is due to using UTF-8 and InnoDB. Each character of the varchar will take 2-4 bytes of storage. There is a variable to work around this in MySQL 5.6.3 through 5.7.7. After 5.7.7, this value is turned on by default. I believe the value is removed in 8.0.

    https://dev.mysql.com/doc/refman/5.6...b_large_prefix

    This requires updating the configuration files of the MySQL server. Your hosting provider or server administrator can help with this issue.

    Leave a comment:

  • sexypbobb
    Member

  • sexypbobb
    replied
    This error on step 3


    Database error in vBulletin :

    Invalid SQL:

    CREATE TABLE noticecriteria (
    noticeid INT UNSIGNED NOT NULL DEFAULT '0',
    criteriaid VARCHAR(250) NOT NULL DEFAULT '',
    condition1 VARCHAR(250) NOT NULL DEFAULT '',
    condition2 VARCHAR(250) NOT NULL DEFAULT '',
    condition3 VARCHAR(250) NOT NULL DEFAULT '',
    PRIMARY KEY (noticeid,criteriaid)
    );

    MySQL Error : Specified key was too long; max key length is 1000 bytes
    Error Number : 1071
    Request Date : Wednesday, November 20th 2019 @ 06:54:36 PM
    Error Date : Wednesday, November 20th 2019 @ 06:54:39 PM
    Script : http://www.philbobb.com/community/in...nstall.php?do=
    Referrer : https://www.philbobb.com/community/i...3&emptydb=true
    IP Address : IPADDRESS
    Username :
    Classname : vB_Database_MySQLi
    MySQL Version : 5.6.43
    Server : 142.4.7.253
    User Agent :

    Leave a comment:

Related Topics

Collapse

Working...
X