Viewing 4 replies - 1 through 4 (of 4 total)
  • Hi,

    If you have access and are familiar with the process you can try running a repair on your MySQL database. If not, check with your hosting provider and they should be able to run the repair tool on your tables.

    -Brian

    Thread Starter SoN9ne

    (@son9ne)

    Thanks for your suggestion. I tried to repair the table and I get the message:

    The storage engine for the table doesn't support repair.

    The table structure is:

    CREATE TABLE IF NOT EXISTS wp_wfBlocks (
      IP binary(16) NOT NULL DEFAULT '',
      blockedTime bigint(20) NOT NULL,
      reason varchar(255) NOT NULL,
      lastAttempt int(10) unsigned DEFAULT '0',
      blockedHits int(10) unsigned DEFAULT '0',
      wfsn tinyint(3) unsigned DEFAULT '0',
      permanent tinyint(3) unsigned DEFAULT '0',
      PRIMARY KEY (IP),
      KEY k1 (wfsn)
    ) ENGINE=InnoDB DEFAULT CHARSET=utf8;

    Further investigation shows that the error is getting triggered at wordfenceClass.php line 333 in the runInstall method.

    $db->queryWriteIgnoreError("alter table $prefix"."wfBlocks add column permanent tinyint UNSIGNED default 0");

    I also notices a few tables in wordfence that are using latin1_swedish_ci instead of utf8_general_ci. Is that by design?

    These tables are:

    • wp_wfBadLeechers
    • wp_wfCrawlers
    • wp_wfHits
    • wp_wfLeechers
    • wp_wfReverseCache
    • wp_wfScanners

    I’m going to try removing the plugin and re-installing it. Hopefully this will solve the issue.

    Thread Starter SoN9ne

    (@son9ne)

    Found the issue! Luckily, there’s nothing wrong with WordFence. The issue was due to caching. I purged my caches and now I get no errors… I swear, sometimes cache is more of a problem than a solution.

    Still interested in the tables charset.

    The charset is not important, according to what I know.

    tim

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Duplicate column name 'permanent'’ is closed to new replies.