Forum Replies Created

Viewing 3 replies - 1 through 3 (of 3 total)
  • The tip from the other thread (https://ww.wp.xz.cn/support/topic/database-error-table-tablename-wp_blc_links-doesnt-exist/) helped. I rolled back (with WP Rollback) to 1.11.10, he created the database tables and then I updated back to 1.11.11 and it works (for now).

    I’m running BLC version 1.11.11 according to the plugin-list and MySQL-Version 5.6.19.

    I’ve the same problem. It seems to be something about an illegal collation setting. Here is the installation log from BLC:

    [ ] CREATE TABLE IF NOT EXISTSwp_blc_filters(idint(10) unsigned NOT NULL AUTO_INCREMENT,namevarchar(100) NOT NULL,paramstext NOT NULL, PRIMARY KEY (id) ) DEFAULT CHARACTER SET utf8mb4 COLLATE utf8_general_ci
    Database error : COLLATION ‘utf8_general_ci’ is not valid for CHARACTER SET ‘utf8mb4’
    [ ] CREATE TABLE IF NOT EXISTS wp_blc_instances ( instance_id int(10) unsigned NOT NULL AUTO_INCREMENT, link_id int(10) unsigned NOT NULL, container_id int(10) unsigned NOT NULL, container_type varchar(40) NOT NULL DEFAULT ‘post’, link_text text NOT NULL DEFAULT ”, parser_type varchar(40) NOT NULL DEFAULT ‘link’, container_field varchar(250) NOT NULL DEFAULT ”, link_context varchar(250) NOT NULL DEFAULT ”, raw_url text NOT NULL, PRIMARY KEY (instance_id), KEY link_id (link_id), KEY source_id (container_type, container_id), KEY parser_type (parser_type) ) DEFAULT CHARACTER SET utf8mb4 COLLATE utf8_general_ci
    Database error : COLLATION ‘utf8_general_ci’ is not valid for CHARACTER SET ‘utf8mb4’
    [ ] CREATE TABLE IF NOT EXISTS wp_blc_links ( link_id int(20) unsigned NOT NULL AUTO_INCREMENT, url text CHARACTER SET utf8 COLLATE utf8_bin NOT NULL, first_failure datetime NOT NULL DEFAULT ‘0000-00-00 00:00:00’, last_check datetime NOT NULL DEFAULT ‘0000-00-00 00:00:00’, last_success datetime NOT NULL DEFAULT ‘0000-00-00 00:00:00’, last_check_attempt datetime NOT NULL DEFAULT ‘0000-00-00 00:00:00’, check_count int(4) unsigned NOT NULL DEFAULT ‘0’, final_url text CHARACTER SET latin1 COLLATE latin1_general_cs NOT NULL, redirect_count smallint(5) unsigned NOT NULL DEFAULT ‘0’, log text NOT NULL, http_code smallint(6) NOT NULL DEFAULT ‘0’, status_code varchar(100) DEFAULT ”, status_text varchar(250) DEFAULT ”, request_duration float NOT NULL DEFAULT ‘0’, timeout tinyint(1) unsigned NOT NULL DEFAULT ‘0’, broken tinyint(1) unsigned NOT NULL DEFAULT ‘0’, warning tinyint(1) unsigned NOT NULL DEFAULT ‘0’, may_recheck tinyint(1) NOT NULL DEFAULT ‘1’, being_checked tinyint(1) NOT NULL DEFAULT ‘0’, result_hash varchar(200) NOT NULL DEFAULT ”, false_positive tinyint(1) NOT NULL DEFAULT ‘0’, dismissed tinyint(1) NOT NULL DEFAULT ‘0’, PRIMARY KEY (link_id), KEY url (url(150)), KEY final_url (final_url(150)), KEY http_code (http_code), KEY broken (broken) ) DEFAULT CHARACTER SET utf8mb4 COLLATE utf8_general_ci
    Database error : COLLATION ‘utf8_general_ci’ is not valid for CHARACTER SET ‘utf8mb4’
    [ ] CREATE TABLE IF NOT EXISTS wp_blc_synch ( container_id int(20) unsigned NOT NULL, container_type varchar(40) NOT NULL, synched tinyint(2) unsigned NOT NULL, last_synch datetime NOT NULL DEFAULT ‘0000-00-00 00:00:00’, PRIMARY KEY (container_type,container_id), KEY synched (synched) ) DEFAULT CHARACTER SET utf8mb4 COLLATE utf8_general_ci
    Database error : COLLATION ‘utf8_general_ci’ is not valid for CHARACTER SET ‘utf8mb4’

    • This reply was modified 6 years, 3 months ago by Sicarius. Reason: trying to make the code more readable
Viewing 3 replies - 1 through 3 (of 3 total)