Logging functionality lost with new Bad Behavior 2.0.18
kdebaas - July 1, 2008 - 15:24
| Project: | Bad Behavior |
| Version: | 5.x-2.0-beta1 |
| Component: | Code |
| Category: | bug report |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | duplicate |
Jump to:
Description
After being swamped by comment spam attempts, I installed Bad Behaviour, to be greeted with a new, eerie silence... Thanks!
My Apache log is now showing 403 responses to those nasty comment spam bots. But when I check the Bad behavior log, with or without verbose switched on, there is nothing. Empty!
Why?
cheers
Klaas
#1
Do you have a table alias? Check your sql database, it is probaby logging them but not using an alias, so the admin interface can't find the table.
Not sure how to fix it...
#2
When downgrading to Bad Behavior 2.0.13 the module functions as expected, and a Bad Behavior log is kept. I suppose that the new functionality of being able to switch off logging altogether, that appeared in 2.0.15, is not yet implemented in the Drupal module.
#3
Same problem
#4
There is a patch in the make which addresses this.
[edit] - corrected hyperlink