Quote:
|
It is impossible to have maintain a clean, heavily used site without these protections.
|
I don't think it's true that you can't have a clean/heavily used site without the Bad Behavior type plugin. I don't think all high traffic blogs or php based sites run Bad Behavior.
Not saying it's a bad plugin, but your statements are just a bit over reaching :)
You're right though, after reading the "how to" on how to get Bad Behavior working with "any" PHP script, it seems pretty straightforward.
http://www.homelandstupidity.us/soft...-bad-behavior/ Quote:
|
By default Bad Behavior can provide protection to any PHP script out of the box, but it cannot provide logging. If you are willing to live without Bad Behavior’s detailed logs, simply install the Bad Behavior folder somewhere on your server, and then call require_once("/path/to/Bad-Behavior/bad-behavior-generic.php"); from your PHP script. I recommend placing this function call in a common piece of PHP code which is loaded from all parts of your PHP-based software, so that it can provide protection to all parts of your software.
|
If I had a thumbnails worth of PHP skills, I'd try porting it to pligg myself.
I may test out the "non-logging" version they describe to see if I can get it working though.
Can anybody name a common piece of PHP code in pligg that is used by almost all of the pages? I can test adding the bad behavior call to that page.