Bad Behavior 2.1 development releases on Flatpress
- Posted by David at 15:35:02
- Open Source, Flatpress, Bad Behavior
Current mood: 
Bad behavior (also known as BB2) which is a great anti-spam-robot plugin has a new branch in development.
I’ve finally had some time to poke into the code and it’s actually easier to get working with flatpress now
But the installation is quite a bit different this time so read the instructions below carefully!
Note: This post will be updated if needed until the 2.1 development branch is going stable.
UPDATE: 2010-07-09 with instructions for version 2.1.3
[Read More...]Bad Behavior 2.0.35
- Posted by David at 20:46:57
- Open Source, Flatpress, Bad Behavior
Current mood: 
A new version is out agian, this time with a fix for SQL-problems, so it doesn’t affect Flatpress users.
However, upgrading can be worth it anyway as the blacklist also is updated.
Bad Behavior 2.0.34 and Flatpress
- Posted by David at 18:45:10
- Open Source, Flatpress, Bad Behavior
Current mood: 
Version 2.0.34 is out. Flatpress integration works as earlier mentioned installation instructions, but you will need to take a look at the HTML tags in the error message (defined in the banned.inc file) if you care for validating code.
Bad Behaviour 2.0.33 on Flatpress
- Posted by David at 18:31:58
- Open Source, Flatpress, Bad Behavior
Current mood:
Compared to the previous version it’s the common tests that are updated to fix an issue with the web crawler used by the Corel Content Distribution Network as it uses an strange HTTP header.
The previously mentioned installation instructions for Flatpress is still valid.
Bad Behavior 2.0.32 and Flatpress
- Posted by David at 19:12:06
- Open Source, Flatpress, Bad Behavior
Current mood:
Bad Behavior is now up to version 2.0.32 and while the basic installation instructions for flatpress still is valid, a couple of changes in the core makes patching for flatfile logging a bit more tricky.
So I’ve redone the diff file to make life easier for all Flatpress users
So to summarise: Unless you use the flatfile logging the update to 2.0.32 is a simple drop-in replacement. The flatfile logging alternative needs the patch to be done again.