• Resolved DavidSortOf

    (@davidsortof)


    Hi, I just updated Semalt Blocker, and when I logged off, I got a wierd message. So I attempted to log in, and got the same message:

    Notice: Undefined index: domains in /home/[username]/[site]/wp-content/plugins/semalt/semalt.php on line 32

    Warning: Cannot modify header information – headers already sent by (output started at /home/[username]/[site]/wp-content/plugins/semalt/semalt.php:32) in /home/[username]/[site]/wp-includes/pluggable.php on line 1178

    What’s the best way to deal with that?

    https://www.ads-software.com/plugins/semalt/

Viewing 15 replies - 1 through 15 (of 26 total)
  • Thread Starter DavidSortOf

    (@davidsortof)

    And I now see that Semalt Blocker is only compatible up to 4.0.1, and I’m running 4.1.1. Please help though, as I’m dead in the water.

    Thread Starter DavidSortOf

    (@davidsortof)

    Ah. I see, I’ll just delete it using FTP.

    Thread Starter DavidSortOf

    (@davidsortof)

    But do I need to do anything with pluggable.php?

    Thread Starter DavidSortOf

    (@davidsortof)

    Done.

    Thread Starter DavidSortOf

    (@davidsortof)

    Hi, so far so good with the latest update and WP 4.1.1. Change the compatibility info?

    Thread Starter DavidSortOf

    (@davidsortof)

    A bit more info. On another one of my sites, also in WP 4.1.1, I get the following code on the WP login page, above the normal username/password fields, and logging in works (Noting this because clearly something is wrong):

    Warning: Cannot modify header information - headers already sent by (output started at /home/[username]/[site].com/wp-content/plugins/semalt/semalt.php:29) in /home/[username]/[site].com/wp-includes/pluggable.php on line 949
    
    Warning: Cannot modify header information - headers already sent by (output started at /home/[username]/[site].com/wp-content/plugins/semalt/semalt.php:29) in /home/[username]/[site].com/wp-includes/pluggable.php on line 950
    
    Warning: Cannot modify header information - headers already sent by (output started at /home/[username]/[site].com/wp-content/plugins/semalt/semalt.php:29) in /home/[username]/[site].com/wp-includes/pluggable.php on line 951
    
    Warning: Cannot modify header information - headers already sent by (output started at /home/[username]/[site].com/wp-content/plugins/semalt/semalt.php:29) in /home/[username]/[site].com/wp-includes/pluggable.php on line 954
    
    Warning: Cannot modify header information - headers already sent by (output started at /home/[username]/[site].com/wp-content/plugins/semalt/semalt.php:29) in /home/[username]/[site].com/wp-includes/pluggable.php on line 955
    
    Warning: Cannot modify header information - headers already sent by (output started at /home/[username]/[site].com/wp-content/plugins/semalt/semalt.php:29) in /home/[username]/[site].com/wp-includes/pluggable.php on line 956
    
    Warning: Cannot modify header information - headers already sent by (output started at /home/[username]/[site].com/wp-content/plugins/semalt/semalt.php:29) in /home/[username]/[site].com/wp-includes/pluggable.php on line 957

    Also, kdunham’s post is very disconcerting, and I agree that this is a huge snafu, in that, as he says “many might have this problem, and not even realize it.” So I’ll just deactivate on both my sites until this is confirmed tested on 4.1.1, and the Google error is confirmed fixed.

    Thank You!

    Plugin Author Alex Moss

    (@alexmoss)

    Hi David, can you please fill out this form and get in touch with me over email to solve this? Please confirm you’re also using v1.1.2. Thanks

    Thread Starter DavidSortOf

    (@davidsortof)

    Done. And yes, I’m using v1.1.2.

    Thanks,

    David

    Plugin Author Alex Moss

    (@alexmoss)

    I’ve been able to test on another site and now updated to 1.1.3. This is live on peadig.com and have tested with a couple of sites.

    Can you confirm this works for you now?

    Thread Starter DavidSortOf

    (@davidsortof)

    Sadly, though the Google Redirect Issue seems to be fixed on one of my sites, this issue, which I’m having one one site, is worse with the 1.1.3 update:

    Now, I get a whole string of similar messages when I log off of WordPress, and when I load the log-on page, I get this:

    Notice: Undefined index: domains in /home/[username]/[site].com/wp-content/plugins/semalt/semalt.php on line 55
    
    Warning: Cannot modify header information - headers already sent by (output started at /home/[username]/[site].com/wp-content/plugins/semalt/semalt.php:55) in /home/[username]/[site].com/wp-login.php on line 424
    
    Warning: Cannot modify header information - headers already sent by (output started at /home/[username]/[site].com/wp-content/plugins/semalt/semalt.php:55) in /home/[username]/[site].com/wp-login.php on line 437
    
    Warning: Cannot modify header information - headers already sent by (output started at /home/[username]/[site].com/wp-content/plugins/semalt/semalt.php:55) in /home/[username]/[site].com/wp-includes/pluggable.php on line 918
    
    Warning: Cannot modify header information - headers already sent by (output started at /home/[username]/[site].com/wp-content/plugins/semalt/semalt.php:55) in /home/[username]/[site].com/wp-includes/pluggable.php on line 919
    
    Warning: Cannot modify header information - headers already sent by (output started at /home/[username]/[site].com/wp-content/plugins/semalt/semalt.php:55) in /home/[username]/[site].com/wp-includes/pluggable.php on line 920
    [Site Name]

    Worse, when I attempt to log on, I get this:

    ERROR: Cookies are blocked due to unexpected output. For help, please see this documentation or try the support forums.

    And I cannot log in.

    The main difference between the two sites is that this one uses the Twenty Thirteen theme.

    Thanks,

    David

    Thread Starter DavidSortOf

    (@davidsortof)

    But, switching to the Twenty Thirteen theme on my other site doesn’t create the problem. : (

    Plugin Author Alex Moss

    (@alexmoss)

    Are they on the same server? Same versions of WordPress? Very odd

    Thread Starter DavidSortOf

    (@davidsortof)

    Yep, sitting side-by-side on the same server, and both on WP 4.1.1.

    Plugin Author Alex Moss

    (@alexmoss)

    The issue above is just a PHP warning and, although present, should not affect anything else on the site. Have you any caching plugins installed? If so please purge all caches.

    Thread Starter DavidSortOf

    (@davidsortof)

    Nope, no caching plug-ins. I also tried deactivating the other plug-ins, but that didn’t work.

    Also, just in case this info helps anyone, per our conversation over email, I deleted the blank line in semalt.php, and that didn’t work either.

    Weird that it only happens with one of my websites similarly configured, and specifically with the Semalt Blocker update of around last Thursday.

Viewing 15 replies - 1 through 15 (of 26 total)
  • The topic ‘Installed update, cannot log in!’ is closed to new replies.