Bad Behavior 2.2.24 has been released. This is a maintenance release for WordPress users. users of other platforms do not need to update at this time.
Changes
The following changes have been made since 2.2.23:
- WordPress: Some deprecated code has been rewritten. Thanks to Doug Joseph for reporting the issue.
Download
Notes
Just as a reminder, if you use CloudFlare, Incapsula, Amazon Elastic Load Balancer, Azure Load Balancer, Google Cloud Load Balancing, or similar services on your site, you may need to enable the Reverse Proxy option in Bad Behavior’s settings, or many of your visitors and search engines will be blocked.
Doesn’t seem like much has been happening here to be honest. Comparing the code, can only see you’ve changed MJ12bot to MJ12bot/v1.0.8 which I doubt makes much useful difference. Could you further explain that change?
The PHP Compantibilty Plug-In for has flagged Bad Behavior. This has to do with upgrading my WP site to PHP 7.3
Bad Behavior works up to PHP 7.4. I’ll check into it and see if I can fix this.
I’m using the previous version for MediaWiki, and I get the following error:
LoadBalancer.php: Invalid server index index #DB_SLAVE
…
/home/seventh/public_html/wikific/extensions/bad-behavior/bad-behavior-mediawiki.php(171): wfGetDB(string)
In the file/line in question, it says “// FIXME: Need to make this multi-DB compatible eventually
$dbr = wfGetDB(DB_SLAVE);” so does that mean there’s no way to fix this error?
What is the error message by default? How accurate is this code? Can it be reconfigured to a custom message?
“enable the Reverse Proxy option in Bad Behavior’s settings, or many of your visitors and search engines will be blocked.”
Yep! That’s why traffic was being reduced. Make it explicit, easy to not-miss in a hurry.
THanks a bunch
Hello,
Just notice that a newer version of Mediawiki is not compatible with Bad Behavior. At least 1.34+. (and currently it’s 1.35)
I was getting this error and forgot to report this. but seems it caused by mediawiki’s changes.
Please fix about this. It throws PHP fetal error about accessing non-exists field.
Thank you for making this amazing product.
Hello,
I just writing this issue 3 times thanks to bad-behavior blocks me haha
anyways, The bad-behavior isn’t working on Mediawiki 1.34+. Thanks to mediawiki changes..
Please fix issue with mediawiki. it throws php fetal error.
thanks for making amazing products.
Surprised nobody posted about this, but one of column names is “Key”, which is a reserved word and cannot be used as such. It will jam any sort of upgrade from ISO to UTF-8, for example.
Ref: dev DOT mysql DOT com/doc/refman/8.0/en/keywords.html#keywords-5-5-detailed-K even though linking will probably flag this comment as spam :/
Yeah annoying Akismet nuked my comment…
As I was trying to say before getting yeeted by the bot, I’m surprised nobody has mentioned this but one of the database columns is called “Key”, and that is a reserved word and cannot be used as such. It will immediately jam any sort of upgrade from ISO to UTF-8, for example, among other issues.
Unable to link due to anti-spam for reference but you can look that up.
Please update and change the column name to comply with mysql rules.
Thanks in advance 🙂