Support » Plugin: wpForo Forum » Version 1.9 – Server Error 503

  • Resolved andreasbln

    (@andreasbln)


    After updating to version 1.9, I get a server error
    503 and my web server is offline. To get the server up and running, I had to import the backup from version 1.8.4.

    There are loads of PHP errors in the log like this one

    Got error ‘PHP message: WordPress Database Error Table – _wpforo_logs’ doesn’t exist

    wp, WP-> main, do_action_ref_array (‘wp’), WP_Hook-> do_action, WP_Hook-> apply_filters, wpForo-> init, do_action (‘wpforo_before_init’), WP_Hook-> do_action, WP_Hook-> apply_filters, wp initFilters, wp initFilters

    Unfortunately I can no longer debug the error because when wpForo is active, I no longer have access to my WordPress (Error 503).

Viewing 11 replies - 1 through 11 (of 11 total)
  • Plugin Support gVectors Support

    (@gvectorssupport)

    @andreasbln,

    Please deactivate the wpForo plugin (do not use the Uninstall button), delete it, then find and install the plugin again. If it doesn’t help please register and open a new support topic in wpForo.com community for deeper support.

    Once again, don’t use the Uninstall button. Just use the Deactivate button. The uninstall button will delete all forum information.

    I have also the same problem

    here is what I got,
    ———————————————————-
    Problems Found in Database
    Table name _____________________ Problem description
    Table: wplo_wpforo_logs ________ Doesn’t exists
    ———————————————————-

    and the [Solve database problems] button doesn’t solve the issues as well

    I tried creating the table with the script as below

    SET AUTOCOMMIT = 0;
    CREATE TABLE IF NOT EXISTS wplo_wpforo_logs(
    logid BIGINT UNSIGNED NOT NULL AUTO_INCREMENT,
    sessionid VARCHAR (255) NOT NULL,
    key VARCHAR (255) NOT NULL,
    value MEDIUMTEXT NOT NULL,
    PRIMARY KEY (logid),
    KEY sessionid_key (sessionid, key)
    ) ENGINE=InnoDB DEFAULT CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci

    SET AUTOCOMMIT = 1;

    but,

    MySQL said:
    #1064 – You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near ‘SET
    AUTOCOMMIT = 1’ at line 8

    FYI, my hosting provides MyISAM type of the DBMS, while in script is InnoDB

    I tried change InnoDB with MyISAM, but there again the message as above (#1064)

    ps.
    deactivating and deleting and then installing the wpForo doesn’t help.

    • This reply was modified 1 year, 5 months ago by formviewflow.
    • This reply was modified 1 year, 5 months ago by formviewflow.
    Plugin Author forum

    (@blackraz)

    Hi Dear @formviewflow
    Please try this code without AUTOCOMMITS;

    only this part of the code

    CREATE TABLE IF NOT EXISTS wplo_wpforo_logs(
    logid BIGINT UNSIGNED NOT NULL AUTO_INCREMENT,
    sessionid VARCHAR (255) NOT NULL,
    key VARCHAR (255) NOT NULL,
    value MEDIUMTEXT NOT NULL,
    PRIMARY KEY (logid),
    KEY sessionid_key (sessionid, key)
    ) ENGINE=InnoDB DEFAULT CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci;

    as you suggested, but still have some errors:

    Error
    Static analysis:

    3 errors were found during analysis.

    A comma or a closing bracket was expected. (near “NOT NULL” at position 147)
    Unexpected beginning of statement. (near “logid” at position 199)
    Unrecognized statement type. (near “KEY” at position 208)
    SQL query:

    CREATE TABLE IF NOT EXISTS wplo_wpforo_logs( logid BIGINT UNSIGNED NOT NULL AUTO_INCREMENT, sessionid VARCHAR (255) NOT NULL, key VARCHAR (255) NOT NULL, value MEDIUMTEXT NOT NULL, PRIMARY KEY (logid), KEY sessionid_key (sessionid, key) ) ENGINE=InnoDB DEFAULT CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci

    MySQL said: Documentation

    #1064 – You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near ‘VARCHAR (255) NOT NULL,
    value MEDIUMTEXT NOT NULL,
    PRIMARY KEY (logid),
    KE…’ at line 4

    Plugin Author forum

    (@blackraz)

    try this one

    CREATE TABLE IF NOT EXISTS `wplo_wpforo_logs`(
    `logid` BIGINT UNSIGNED NOT NULL AUTO_INCREMENT,
    `sessionid` VARCHAR (255) NOT NULL,
    `key` VARCHAR (255) NOT NULL,
    `value` MEDIUMTEXT NOT NULL,
    PRIMARY KEY (`logid`),
    KEY `sessionid_key` (`sessionid`, `key`)
    ) ENGINE=InnoDB DEFAULT CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci;

    • This reply was modified 1 year, 5 months ago by forum.
    • This reply was modified 1 year, 5 months ago by forum.
    • This reply was modified 1 year, 5 months ago by forum.
    • This reply was modified 1 year, 5 months ago by forum.
    • This reply was modified 1 year, 5 months ago by forum.

    I tried also with this variation:

    SQL query:

    CREATE TABLE IF NOT EXISTS wplo_wpforo_logs(
    logid BIGINT UNSIGNED NOT NULL AUTO_INCREMENT,
    sessionid VARCHAR (255) NOT NULL,
    key VARCHAR (255) NOT NULL,
    value MEDIUMTEXT NOT NULL,
    PRIMARY KEY (logid),
    KEY sessionid_key (sessionid, key)
    ) ENGINE=INNODB DEFAULT CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci

    MySQL said: n
    #1071 – Specified key was too long; max key length is 1000 bytes

    Plugin Author forum

    (@blackraz)

    @formviewflow
    try this one

    CREATE TABLE IF NOT EXISTS `wplo_wpforo_logs`(
    `logid` BIGINT UNSIGNED NOT NULL AUTO_INCREMENT,
    `sessionid` VARCHAR (255) NOT NULL,
    `key` VARCHAR (255) NOT NULL,
    `value` MEDIUMTEXT NOT NULL,
    PRIMARY KEY (`logid`),
    KEY `sessionid_key` (`sessionid`(20), `key`(160))
    ) ENGINE=InnoDB DEFAULT CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci;

    very well, @blackraz
    succeeded in creating the log table

    there are minor warnings:
    Warning: #1286 Unknown storage engine ‘InnoDB’
    Warning: #1266 Using storage engine MyISAM for table ‘wplo_wpforo_logs’

    now in Debug –> Table tab just show ” No Problems Found in Database ”

    thank you for your kind help on this.

    • This reply was modified 1 year, 5 months ago by formviewflow.
    • This reply was modified 1 year, 5 months ago by formviewflow.

    FYI, my webserver config is as follow

    Web Server Apache
    PHP Version 7.3.24
    MySQL Version 10.2.33

    • This reply was modified 1 year, 5 months ago by formviewflow.
    Thread Starter andreasbln

    (@andreasbln)

    Ok, I’ll wait until there is a working update, which you can install even without SQL knowledge or run the risk of shooting down your WordPress and losing your work for years just because updates were not thought through properly.

    Plugin Author gVectors Team

    (@gvectors-team)

    Nice!
    Thank you for the update, @andreasbln.
    We’ve also updated the post with the script and created a new sticky topic.

Viewing 11 replies - 1 through 11 (of 11 total)
  • The topic ‘Version 1.9 – Server Error 503’ is closed to new replies.