• Resolved ablears

    (@ablears)


    Hi, today I saw the following in the error log.

    INSERT INTO wp_wfHoover (owner, host, path, hostKey) VAKUES which of course resulted in

    WordPress database error You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near ‘VAKUES

    The odd thing is a recursive grep for ‘VAKUES’ in the Wordfence plugin folder didn’t find anything. It also looks OK in lib/wordfenceURLHoover.php:

    ./lib/wordfenceURLHoover.php: $sql = "INSERT INTO " . $this->table . " (owner, host, path, hostKey) VALUES ";

    This is with Wordfence 6.3.21 on WordPress 4.8.3 (php 7.1.9-1+0~20170902060604.8+jessie~1.gbpebe5d6).

Viewing 2 replies - 1 through 2 (of 2 total)
  • Hi,
    That’s a little bit strange, I suggest checking the exact time when this error is logged in the error log file and compare it with the last modified timestamp on
    “wordfenceURLHoover.php” file.

    It could be that there was a mismatch happened when a script ran on the whole files on your server replacing certain characters with another ones? Can you recognize any other instances of L becoming K within your files on the server?

    Thanks.

    Thread Starter ablears

    (@ablears)

    Hello

    I zipped the wordfence folder that was generating the error, took it to my dev machine and compared it to the forced reinstall version that worked. They were identical. I can’t make sense of that. Also, the file wasn’t changed on the server by an errant search and replace – my recursive grep would have found it, or when I opened the file directly. Date modified for wordfenceURLHoover.php was 2/11/2017 11:04, same as the rest of the files.

    I guess this is one of those outliers where we won’t find a solution. None of it makes sense!

Viewing 2 replies - 1 through 2 (of 2 total)

The topic ‘Wordfence MySQL error’ is closed to new replies.