Help! I Messed up my Site with WPBlackList 2.61

  • I emailed Farook. I’m sure it’s an easy fix. I installed WPBlackList 2.61 on another of my WordPress blogs and it works great. So I did something wrong for sure.
    I was logged in when I uploaded the files, don’t know if that matters. Anyway…here’s my site:
    https://www.ncs-tech.org
    It displays at the top:
    Database error: [Table ‘ncstech_wordpress.blacklist’ doesn’t exist]
    SELECT * FROM blacklist WHERE regex_type = ‘option’
    And when I try to log in I get:
    Warning: Cannot modify header information – headers already sent by (output started at /home/ncstech/public_html/wp-includes/wp-db.php:80) in /home/ncstech/public_html/wp-login.php on line 257
    Warning: Cannot modify header information – headers already sent by (output started at /home/ncstech/public_html/wp-includes/wp-db.php:80) in /home/ncstech/public_html/wp-login.php on line 258
    Warning: Cannot modify header information – headers already sent by (output started at /home/ncstech/public_html/wp-includes/wp-db.php:80) in /home/ncstech/public_html/wp-login.php on line 259
    Warning: Cannot modify header information – headers already sent by (output started at /home/ncstech/public_html/wp-includes/wp-db.php:80) in /home/ncstech/public_html/wp-login.php on line 260
    Warning: Cannot modify header information – headers already sent by (output started at /home/ncstech/public_html/wp-includes/wp-db.php:80) in /home/ncstech/public_html/wp-login.php on line 261
    Any idea how I can fix this, while I wait for Farook?
    How can I uninstall WPBlacklist in the interim?
    Thanks, kj

Viewing 12 replies - 1 through 12 (of 12 total)
  • Thread Starter kjarrett

    (@kjarrett)

    Ok, I deleted all the files and can log in now.
    Will try a reinstall.
    -kj-

    Those warnings are a sign of whitespace.

    Thanks Moshu, but what is whitespace?
    -kj-

    This should help:
    https://faq.wordpress.net/view.php?p=7

    I was too slow, again ??
    https://faq.wordpress.net/view.php?p=7

    Thread Starter kjarrett

    (@kjarrett)

    Thanks guys. All I did was upload the WPBlacklist files from the archive. Nothing else. Did the same thing on another WordPress blog and it worked flawlessly. So … where is the whitespace that is causing the problem, and why wouldn’t it have affected my other WordPress blog the same way? Possibly some sort of corruption when I FTP’d it?
    -kj-

    Could be that… find the file that is first mentioned in the error and check that one.
    All the other files mentioned are knock-on errors – it’s the first that matters.

    justinbaeder

    (@justinbaeder)

    Just curious…why are you installing wp blacklist? This feature is built into 1.2.1 Mingus, right?

    I’m having this problem too.
    only occurs when trying to post a comment. i get an error filled page instead of redirecting back to the posted comment.
    however, the comment post fine.
    i’ve read up, and deleted all the white space (checked it anyway, there wasn’t any…)
    i looked at wp-config, wp-comments, wp-comments-post, wp-comments-reply, wp-comments-popup, and one other include that blacklist uses.
    anything else i might try?
    so far the only way to get it working is to deactivate blacklist (something i REALLY don’t want to do.)
    and justinbaeder:
    how is 1.2 Mingus got a blacklist already installed? please explain!

    Moderator James Huff

    (@macmanx)

    Kjarrett, check for unnecessary whitespace in wp-login.php.

    I checked everywhere for white space and found none.
    The temporary solution was to remove the Blacklist plug, and use Kitten’s Spamminator instead for now.
    but i’d love to solve this problem. Why would blacklist be fine for a time, and then suddenly render some of WP useless?
    i don’t see no white space.
    F.

    Moderator James Huff

    (@macmanx)

    Check your blacklist for blank lines for ‘/’ characters.

Viewing 12 replies - 1 through 12 (of 12 total)
  • The topic ‘Help! I Messed up my Site with WPBlackList 2.61’ is closed to new replies.