Bad Behavior

[4evrblu]

I use a wordpress plugin called Bad Behavior which is clearly a WP specific item. However, I think the question I have could be answered here.

The plugin is activated in the Wordpress Administration area, and it is suppose to write to your database for that blog. Here is what you are suppose to see when you look at the database:

With bad behavior installed and activated

* Browse bad_behavior
* Browse wp_categories
* Browse wp_comments
* Browse wp_linkcategories
* Browse wp_links
* Browse wp_options
* Browse wp_podpress_statcounts
* Browse wp_podpress_stats
* Browse wp_post2cat
* Browse wp_postmeta
* Browse wp_posts
* Browse wp_recentlinks
* Browse wp_usermeta
* Browse wp_users

This is what I see in my blog for http://bluestravels.com

However, for http://totalphysiqueonline.com I see this:

* Browse wp_categories
* Browse wp_comments
* Browse wp_linkcategories
* Browse wp_links
* Browse wp_options
* Browse wp_podpress_statcounts
* Browse wp_podpress_stats
* Browse wp_post2cat
* Browse wp_postmeta
* Browse wp_posts
* Browse wp_recentlinks
* Browse wp_usermeta
* Browse wp_users

bad_behavior is nowhere to be found in my totalphysique db

Yet, it is working. It is operating and blocking spam. Moreover, when you do a backup of the database, you can see a handful of references to it in the database.

Can anyone tell me what they think is going on here? I need to know because the bad_behavior datafield grows to huge sizes making backups of the db take forever.

Thanks

[longneck]

are you running the same version of bad behavior on both sites?

[4evrblu]

are you running the same version of bad behavior on both sites?

Well, yes and no. LOL

I initially installed the same version, 2.07, when I first installed the plugin. So, initially, yes. Then, when 2.08 came out, I made sure I upgraded it in one, but I didn't in the other.

The bluestravels.com site is still running 2.07, whereas totalphysique was running 2.07 for several weeks, and now it runs 2.08

[longneck]

sounds like a bug to me. the plug-in probably has to declare which tables it owns so that it gets listed properly, and that's not happening.

but that's just a guess because i'm not familiar with wordpress at all.

[4evrblu]

Thats not a bad guess actually.

I will run this idea by the creater of the plugin if I can.