Comments on: Bad Behavior 2.0.10

By: Another spam post, the more subtle Referrer Spam..!

Another spam post, the more subtle Referrer Spam..! — Mon, 21 Sep 2009 17:58:33 +0000

[...] also installed Bad Behaviour to further protect my blog – this nifty little and very easily installed plug-in protects [...]

By: David Russell

David Russell — Sat, 10 Nov 2007 19:57:46 +0000

Is this version compatible with the new WP-Super Cache?

By: Jim

Jim — Thu, 25 Oct 2007 01:45:13 +0000

Looks like this project has been abandoned?!?

Bummer…

By: Hilary

Hilary — Wed, 10 Oct 2007 18:31:16 +0000

Hi there. I have been using Bad Behavior for quite some time now. I have had the latest version installed since it was released and had no problems until a few weeks ago. Suddenly, my my dashboard began taking about 30 seconds to load, publishing posts took about 15 seconds, and commenting also took a while. I disabled all of my plugins then re-enabled them one by one until the lag went away. Unfortunately, it was Bad Behavior that caused the lag.

Any ideas on why? Or what I can do? I’d like to continue using it. Thanks!

By: FurrTrap

FurrTrap — Thu, 04 Oct 2007 19:33:21 +0000

I’ve stopped the wp-cron.php blocks by whitelisting my server IP address to bad behavior. No more wp-cron entries in the BB table.

All looks OK now.

By: Noyb

Noyb — Sat, 29 Sep 2007 21:29:07 +0000

Might be an idea to put out a new minor release of Bad Behavior – the way hooks work has changed in MediaWiki 1.11, so Bad Behavior needs to be updated (it’s not currently working with 1.11).

By: Jim

Jim — Mon, 24 Sep 2007 19:22:34 +0000

Yeah, Bad Behavior 2.0.10 is suddenly behaving very badly. It started, by my reckoning, a couple of days ago. I finally had to deactivate it on all my WordPress installations because it seemed to be blocking most php functions as they relate to talking to the database.

By: Web Maestro

Web Maestro — Mon, 24 Sep 2007 16:39:05 +0000

I’m having trouble with Bad Behavior 2.0.10 and WordPressMU v 1.2.1. When Bad Behavior is enabled, all access to /wp-admin/ is blocked (although the blog front-end appears to run normally).

I tried fixing the problem by upgrading to wordpress-mu-1.2.5a, but it didn’t help (FWIW, I ended up downgrading back to 1.2.1 to return to a previous version of WordPress that I know ‘worked’, and haven’t re-upgraded, so we’re temporarily back at WPMU-1.2.1).

As far as I am aware, my sys ops have assured me that no changes to the server occurred, which would have resulted in this problem. That said, the firewall was upgraded, but I am assured that no outbound access is affected. But we have 100s of other servers behind that firewall which have not been adversely affected.

Removing Bad Behavior from the /wp-content/mu-plugins/ folder restores WP-Admin access. Moving it to /wp-content/plugins/ and activating it in a bog by blog basis also causes /wp-admin/ access to fail for those blogs which have it enabled.

Any ideas?

Here’re some specs

PHP: 5.2.0
Zend Engine v2.2.0
httpd: 1.3.37 (Unix)
mysql: 5.2.7
SunOS 5.10 Generic_118855-19 i86pc i386 i86pc

By: Phil J Leitch

Phil J Leitch — Sun, 23 Sep 2007 19:32:22 +0000

I am having trouble with BB v2.0.10 and MW v1.11.0.

Is this line correct to add to localsettings.php ?

include( ‘./extensions/Bad-Behavior/bad-behavior-mediawiki.php’ );

In the BB file I downloaded the bad-behavior-mediawiki.php file is located outside of the Bad-Behavior directory?

Thanks.

By: FurrTrap

FurrTrap — Thu, 20 Sep 2007 18:50:43 +0000

It appears the BB 2.0.10 and WordPress 2.2.3 don’t get on too well in my server environment. BB blocks my server IP address for all attempts to get wp-cron.php. The HTTP return codes are 200, but my server IP is listed in the BB database table.

Any ideas what’s happening and how to fix it up?

Thanks.