WordPress.org

Release Notes

Bad Behavior 2.0 Known Issues

• Bad Behavior may be unable to protect cached pages on MediaWiki.

• When upgrading from version 2.0.19 or prior on MediaWiki and WordPress, you must remove the old version of Bad Behavior from your system manually before manually installing the new version. Other platforms are not affected by this issue.

• The basic functionality of Bad Behavior on WordPress requires version 1.2 or later. The management page for WordPress, which allows browsing Bad Behavior's logs, requires version 2.1 or later. Users of older versions should use phpMyAdmin to browse Bad Behavior's logs, or upgrade WordPress.

• On WordPress when using WordPress Advanced Cache (WP-Cache) or WP-Super Cache, Bad Behavior requires a patch to WP-Cache or WP-Super Cache in order to protect Cached pages. Bad Behavior cannot protect Super Cached pages.

  Edit the wp-content/plugins/wp-cache/wp-cache-phase1.php or wp-content/plugins/wp-super-cache/wp-cache-phase1.php file and find the following two lines at around line 34 (line 56 in WP-Super Cache):

  if (! ($meta = unserialize(@file_get_contents($meta_pathname))) )
      return true;
  

  Immediately after this, insert the following line:

  require_once( ABSPATH . 'wp-content/plugins/Bad-Behavior/bad-behavior-generic.php');
  

  Then visit your site. Everything should work normally, but spammers will not be able to access your cached pages either.

• When using Bad Behavior in conjunction with Spam Karma 2, you may see PHP warnings when Spam Karma 2 displays its internally generated CAPTCHA. This is a design problem in Spam Karma 2. Contact the author of Spam Karma 2 for a fix.