Mario Oyorzabal Salgado writes in to say that he’s ported Bad Behavior to Coppermine Photo Gallery, a popular photo gallery script.
While I don’t run Coppermine and so I haven’t been able to test it myself, the code looks fairly straightforward, and it appears the installation is about the same as other plugins for Coppermine. Check the README and/or README-ES files included with his distribution for more information on how to install it.
Download Bad Behavior for Coppermine Photo Gallery!
It appears he’s also made an http:BL plugin for Coppermine, published at the same place, which you may also find useful.
Bad Behavior 2.0.13 has been released. It is a maintenance release and is recommended for all users.
Who should upgrade?
Users of MediaWiki who are seeing spurious blank lines in wiki pages should upgrade. Users of any type of software which receives trackbacks and pingbacks (such as blogs) should upgrade.
What’s new?
New in this release (since 2.0.12):
- A bit of code relating to MediaWiki has been disabled. This code attempted to measure Bad Behavior’s run time and insert it into wiki pages as an HTML comment while they were being rendered. This code inadvertently inserted blank lines into the output and has been disabled until it can be fixed.
- MediaWiki users receiving fatal errors regarding
wfQuery did not install the extension properly and should consult the installation directions and/or the README.txt file.
- A bug in Bad Behavior’s user agent blacklist code caused blacklist matches to become case-insensitive, when they should have been case-sensitive. Among other things, this caused pingbacks and trackbacks sent from WordPress blogs to fail. This has been fixed.
Download
Download Bad Behavior now!
Support
If you find Bad Behavior useful, please consider making a financial contribution to its further development.
Bad Behavior 2.0.12 has been released. It is a maintenance release and is recommended for all users.
Who should upgrade?
All users who use the digg.com social bookmarking service should upgrade to ensure that Bad Behavior-protected pages can be submitted to the service.
Users of Akamai Dynamic Site Accelerator, Dynamic Site Accelerator Enterprise and Web Application Accelerator should upgrade. (I only know of one such user, and I e-mailed you already. If you use these services, and I didn’t e-mail you, please e-mail me.)
What’s new?
New in this release (since 2.0.11):
- IP addresses for the digg.com service have been added to Bad Behavior’s internal whitelist. Upon submitting a story to digg.com, it attempts to load the submitted URL using the PEAR HTTP_Request class, but with a fake HTTP user agent, causing Bad Behavior to block the requests. This problem was reported to digg and the company has failed to respond or to resolve the problem. The IP addresses have been whitelisted due to user demand. If you use digg, please let them know that this is not acceptable to you.
- Users deploying Bad Behavior with Akamai Dynamic Site Accelerator, Dynamic Site Accelerator Enterprise, or Web Application Accelerator found that Internet Explorer users were being blocked by Bad Behavior. This issue was traced to Akamai’s use of the HTTP/1.1 transfer coding feature in its proxy servers. This issue has been fixed.
Download
Download Bad Behavior now!
Support
If you find Bad Behavior useful, please consider making a financial contribution to its further development.
