Viewing 3 replies - 1 through 3 (of 3 total)
  • Thread Starter StorkWEB

    (@storkweb)

    Also on line 69

    Hello, great spot, thanks for that, much appreciated!

    I’ll update and push the fix out shortly.

    On my systems the bug didn’t manifest as an error, but just a PHP warning in the logs, which is due to WordPress taking the decision to require at least one additional parameter on the prepare statement, to mitigate against erroneous code when evaluating user submitted data.

    There’s no security issue here as the table name variable is hard-coded, however I should have added the empty string to prevent the warning.

    Thanks again for taking the time to point this out!

    Bug Status: Closed.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Bug’ is closed to new replies.