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!

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

Done.

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

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

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.

Hi Again — Just to close this out, I figured it out by viewing the source, copying all the css code that referenced borders (border-top and border-bottom, etc. Four instances?), pasting it into my theme’s css of course, changing the “1px” to “2px,” and adding !important, but I didn’t like how it looked, so I’m just sticking with Nirmal’s slick design.

Thanks!

Thanks TJ Kelly, that’s where I put it. But following @puda, I used this, which seems to be working for me, too:

SetEnvIfNoCase Referer buttons-for-website.com spambot=yes
Order allow,deny
Allow from all
Deny from env=spambot

Are these two different ways of accomplishing the same thing? Or are there any differences we should be aware of?

Ok I learned it’s either before or after the WordPress block. Thanks all!

Or, at the very top, before
# BEGIN WordPress
?

@puda, @tj Kelly, & All —

My htaccess file has this inside it:

# BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteRule ^index\.php$ - [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
</IfModule>

# END WordPress

Where do I put puda’s fix? Right between
RewriteRule . /index.php [L]
and
</IfModule>?

@tj Kelly, thanks much!

Unfortunately, a couple of days later, the buttons-for-website.com referrals continued. Weird that they stopped right away after installing the plug-in, but then returned. Makes me think htaccess is the way to go. No idea how to do that, but I’ll ask my hosting service.

Hi — Like many of us on this thread, I don’t use this plug-in, but got referral traffic from buttons-for-website.com, and this seems to be the definitive thread for this issue.

I just recently launched my site, and since watching the stats I’ve been getting exactly 1 referral from buttons-for-website.com, accociated with a page view from Brazil, every day.

At taghaboy’s suggestion, I activated Semalt Blocker (btw when you install it, it becomes “Semalt Redirect Manager” for some reason), and poof, no more daily referrals from buttons-for-website.com.

I’m a n00b, and this just seemed like the easiest thing to try. This works by re-directing.

But how is this strategy different from puda’s htaccess fix? I guess, problem solved, so no need to over-think, but would it be better to do puda’s fix?

Thanks much!

Hi Nirmal, thanks for checking, and good to hear it checks on 4.1.

On my side, I took out the css workaround above, but I still couldn’t change the menu text color using the settings panel. Not sure what the cuprit is with my site, but since it’s working for me, I’ll use it like this, since I really like how the responsive menu is working.

Thanks much,

David

Ok got it: Just need to change the permalink structure (Settings > Permalinks) to Custom, specifically /blog/%postname%/

Thanks, Dvorak Designs! : )

Of course, now I have to re-do a few links, and probably re-publish the few posts I have, but from here on in, this should do the trick!