Bad Behavior / Bad Behaviour

Known Issues

This page documents known issues in Bad Behavior 2.2.

If you are having an issue not listed, please ensure that you have the latest 2.2.x release of Bad Behavior.

• IPv6 address ranges cannot be whitelisted; the whitelist accepts single IPv6 addresses only. This limitation will be addressed in a future release of Bad Behavior.
• The Display Statistics option is database intensive. Disable this option to improve performance on high traffic sites.
• Bad Behavior’s reverse proxy address handling is not IPv6-aware. If you have a chain of two or more reverse proxies and your internal network is IPv6, do not use Bad Behavior at this time. This issue will be addressed in a future release of Bad Behavior.
• MediaWiki: Database reads use the master instead of replication slaves. If this causes performance issues for your wiki, disable logging. This issue will be addressed in a future version of Bad Behavior.
• WordPress: Selection boxes next to log entries in the administrative page have no effect. This issue will be addressed in a future 2.2 point release of Bad Behavior.
• WordPress: When running on a multisite installation, Bad Behavior uses one database table per site in the network, and each site is able to configure Bad Behavior independently. In a future release Bad Behavior will allow for the network administrator to centralize Bad Behavior’s logging and configuration.

If you are having an issue for which you received a technical support key, visit this page and enter the key that you received.