Support » Plugin: Wordfence Security » [Plugin: Wordfence Security] Null MySQL error

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author Wordfence


    We do check that tables have been created in our activation hook and create the tables if they don’t exist. The check is also done every time you upgrade Wordfence through a mechanism outside the activation hook because it’s unreliable. Did you manually delete the Wordfence tables? That’s the only way I can see that you’d get this error.

    Ben Lobaugh (blobaugh)


    Jetpack Engineer

    WF did NOT create the tables on install/activation. This is because your DB connector code has a bug in it that does not allow valid values for DB authentication. See the following for the code fix . This is another reason to use the built in database object rather than creating your own 😉

    Later on your code is not verifying that the tables have been successfully created. You should probably add a check to ensure the tables have been created/updated on activation/update and disable the plugin with a message to the user about how to fix it if they are not available.

    Plugin Author Wordfence


    OK that makes sense. So the connection failed to get set up and the schema was never created. I’ve upped the priority on this fix.

    Thanks very much for your detailed bug reports!


Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘[Plugin: Wordfence Security] Null MySQL error’ is closed to new replies.