Skip to:

Opened 13 years ago

Closed 13 years ago

Last modified 13 years ago

#3101 closed defect (bug) (no action required)

Spammed blog removes all blog entries and spams user. Unspamming doesn't reverse table row deletes.

Reported by: bigtweet's profile bigtweet Owned by:
Milestone: 1.2.8 Priority: normal
Severity: normal Version:
Component: Blogs Keywords:


WordPress 3.1, BuddyPress 1.2.8

Anti-Splog 1.0.7

When a single blog is spammed from the Sites panel in the Dashboard,
all the blog entries for the associated user are removed from the
wp_bp_user_blogs table. The user is also spammed in wp_users table (is this a WP bug/feature?).

When a spammed blog is unspammed from the Sites panel, the entries in the wp_bp_user_blogs table are not restored.

I noticed the following queries being issued for user 13 when a single blog was spammed:
DELETE FROM wp_bp_user_blogs WHERE user_id = 13
UPDATE wp_users SET spam = 1 WHERE ID = 13

I think the DELETE should be qualified by blog id and not by user id.

Should the user be spammed here? Should I file a WP bug or is this a feature? (Once a user is spammed, they can't be unspammed from Dashboard).

Using Anti-Splog (plugin to mark blogs as spam) showed me another aspect of this potential BuddyPress bug and let me identify the places in the BP code that were issuing the queries.

What I did was to create 2 blogs in succession and force both to be spammed (tweak in Anti-Splog). This caused the following sequence of queries:

INSERT INTO wp_bp_user_blogs ( user_id, blog_id ) VALUES ( 13, 50 )
DELETE FROM wp_bp_user_blogs WHERE user_id = 13
INSERT INTO wp_bp_user_blogs ( user_id, blog_id ) VALUES ( 13, 50 )

INSERT INTO wp_bp_user_blogs ( user_id, blog_id ) VALUES ( 13, 51 )
DELETE FROM wp_bp_user_blogs WHERE user_id = 13
INSERT INTO wp_bp_user_blogs ( user_id, blog_id ) VALUES ( 13, 51 )

What is interesting to note is:

  1. There are 2 INSERTs for each blog creation (expected just 1).
  2. There is a DELETE that seems like it should be qualified by blog id instead of user id.

The queries are being generated from

The INSERTs are coming from function save()
The DELETEs are coming from function delete_blogs_for_user()

I think that only the blog being spammed should be removed from table wp_bp_user_blogs. It would be nice to have a hook that re-inserted this entry into wp_bp_user_blogs when a blog is unspammed. Without this, a blog will never again be accessible to BuddyPress.

I would like to solicit an opinion on whether spamming a user when a blog is spammed seems like a WP feature, or whether I should file a WordPress bug.



Change History (3)

#1 @andrea_r
13 years ago

Disable the anti-splog plugin.

Now go mark a blog as spam. (Yes, you can do that and it is built in.) Did the spammed blog get deleted? If not, then it was the plugin.

#2 @bigtweet
13 years ago

  • Resolution set to invalid
  • Status changed from new to closed

My apologies. It was the Anti-Splog plugin causing this problem. It turns out that the culprit was a setting called "Spam/Unspam Blog Users". Setting this to Yes exhibited the behaviour described above.

This bug can be closed. I will be opening a bug against the Anti-Splog plugin.


#3 @johnjamesjacoby
13 years ago

  • Cc scarter28m-temp@… removed
  • Component changed from Core to Blogs
  • Keywords blog spam wp_bp_user_blogs wp_users Anti-Splog removed
  • Milestone changed from Awaiting Review to 1.2.8
  • Severity set to normal
  • Version 1.2.8 deleted

Moving closed ticket out of Awaiting Review.

Note: See TracTickets for help on using tickets.