Bad Behavior 2.0.34
December 6th, 2009 by Michael Hampton
Bad Behavior 2.0.34 has been released. It is a maintenance release and is recommended for specific users of WordPress identified below.
Please note: The 2.0 series of Bad Behavior is receiving limited updates, including unblocks, bug fixes and security fixes only. Future development will be to the 2.1 development tree.
MediaWiki and WordPress users who have not updated in the last year or so should take note of special upgrade instructions below.
Who should upgrade?
WordPress users who use the W3 Total Cache plugin should upgrade to ensure that users are not blocked inappropriately due to flaws in W3 Total Cache.
What’s new?
New in this release (since 2.0.33):
- On some WordPress installations which use the W3 Total Cache plugin, W3 Total Cache could inappropriately store the error page which Bad Behavior serves to illegitimate requests. When this happens, the cached error page would be served to subsequent legitimate requests. Bad Behavior 2.0.34 contains a workaround which forces W3 Total Cache to not cache these error pages. (To be clear, W3 Total Cache is still broken and needs an update, but this resolves the immediate problem.)
Authors of caching plugins should consider following the “standard” set by WP Super Cache: check for a constant DONOTCACHEPAGE which can be set by other plugins; and checking to ensure that non-cacheable error responses are never cached, regardless of which plugin generates them.
Support
Thank you to everyone who has chosen to make a financial contribution toward further development of Bad Behavior. Your contributions ensure that I can prioritize Bad Behavior development and make more frequent and timely releases, like this one.
Download
Special Upgrade Instructions
Users of MediaWiki and WordPress upgrading from version 2.0.20 or earlier should follow these special directions (from 2.0.21 or later, upgrade normally):
For MediaWiki: Before installing this version of Bad Behavior, manually remove (e.g. using FTP or ssh) any old versions you may have, including the lines added to LocalSettings.php. Then install the new version fresh, following the installation instructions for MediaWiki.
For WordPress: If updating to this version through the automatic updater fails, manually remove (e.g. using FTP or ssh) any old versions you may have installed. Then upload and install the new version fresh, following the installation instructions for WordPress. After doing so, future automatic updates should proceed normally.
For other platforms: No changes to your upgrade procedures should be necessary.
José Luís Says
Thanks for this new version. Do you have any ETA on a solution to avoid overwriting whitelist on plugin updates?
Dec 6th, 2009 at 1:03 pm
ariston | 101 ways to build links Says
Hi there,
Still newb in blogging and I think this is an awesome plugin(a must for heavily traffic sites)… but first, I need more traffic on my site! =)
btw, found the link on my WP dashboard!
Dec 12th, 2009 at 5:07 pm
Álvaro Degives-Más Says
José Luís, what I have is a text file stored above the webserver root (i.e. above “www” or “public_html”) containing pointers I jotted down for upgrades, including any BB whitelists. The thing with upgrade wipe-outs is that there’s no canonical storage place / method for customization; i.e. it’s a fairly generic issue, not at all exclusive to BB.
Dec 14th, 2009 at 1:06 am
Frederick Townes Says
W3TC now supports Bad Behavior in v0.8.5.2
Mar 14th, 2010 at 12:09 pm
Judy Says
there is a conflict with this plugin and the Paypal api when using wp-ecommerce. any thoughts about that? order status and details are not updated with it activated, but go right through when deactivated. thanks.
Sep 29th, 2010 at 2:19 pm
Michael Hampton Says
You need to complain to PayPal about that; it’s their fault. In the meantime you can use the URL whitelist feature in the 2.1 development series to work around the problem.
Sep 29th, 2010 at 8:18 pm