Skip to:

Opened 20 months ago

Last modified 10 months ago

#4469 new enhancement

Mark as Spammer

Reported by: Jagusti Owned by:
Milestone: Future Release Priority: normal
Severity: normal Version: 1.6
Component: Members Keywords: needs-patch
Cc: sillybean, mercijavier@…


The user experience for marking spam accounts is degraded in version 1.6:

  • The number of steps to mark a user as a spammer has increased. Each click-step requires a page reload, which further slows down the administrative process.
  • There are no other Capabilities currently presented, so it seems premature to have a single option in that screen to spam users.
  • The option 'This user is a spammer' is described as a Capability, which, metaphorically, seems broken. Being a spammer seems more like an account role or status.

By comparison, it is a lot easier to delete accounts. However, spam accounts are common in BuddyPress, so having an Admin Bar menu option to Mark as Spammer is more useful and expedient.


  1. Revert to pre-1.6, with Mark as Spammer directly available from AdminBar when in User Profile. Changeset [1801] has historical method of marking users as spammers.
  2. Include option directly under Edit Member, or as a menu flyout option under a new Account Status submenu.
    • So: AdminBar > Edit Member > Set Account Status > {(Not) Spammer | Delete}.
    • Replicate this in the Account Settings tab (changing Delete Account to Account Status, and present Mark (Not) Spammer and Delete actions).

Change History (7)

comment:1 DJPaul20 months ago

  • Milestone changed from Awaiting Review to 1.7

Yes, 1.6 was a step backwards in this regard.

comment:2 sillybean19 months ago

  • Cc sillybean added

comment:3 mercime19 months ago

  • Cc mercijavier@… added

comment:4 sillybean19 months ago

I've written a quick plugin to restore this link in the admin bar. (I also threw in a function to add a "Spammer" link to the activity stream.) Grab it here:

This plugin restores an action that, according to the inline docs, was deliberately removed and moved to settings in 1.6. I haven't been following BP development, so I don't know what the plan is/was for that, or whether restoring the action has any adverse effects. I need to get up to speed before submitting a patch.

comment:5 DJPaul18 months ago

  • Keywords needs-patch added

comment:6 johnjamesjacoby17 months ago

  • Milestone changed from 1.7 to 1.8

Is probably worth while to put more effort into this (and the settings component as a whole) in 1.8.

comment:7 boonebgorges10 months ago

  • Milestone changed from 1.8 to Future Release
Note: See TracTickets for help on using tickets.