Skip to:

Opened 13 years ago

Closed 11 years ago

#3098 closed defect (bug) (wontfix)

Accounts with ”blocked” or ”inactive” roles are still active/accessible

Reported by: pjnu's profile pjnu Owned by:
Milestone: Priority: normal
Severity: normal Version: 1.2.8
Component: Forums Keywords: dev-feedback close


I’m trying to temporarily disable a user account temporarily but that simply isn’t happening. When I go to wp-admin/ms-users.php , click Edit, and select Blocked or Inactive, the user is still able to freely login.

If this is true, the only way I can block access is to delete the account. Can someone help me fix this weird issue? Thanks.

Discussion thread:

Change History (9)

#1 @DJPaul
13 years ago

If you disable BuddyPress, does the problem go away?

#2 @r-a-y
13 years ago

The problem appears to come from bbPress as the roles "blocked" and "inactive" do not exist natively in Wordpress, they are from bbPress.

The forum bridge code in bp-forums-bbpress.php has something to do with this.


Also, single WP doesn't have a native way to set users to spam in the WP admin dashboard unless you use multisite. Sounds like single WP should also offer similar functionality for this.

#3 @r-a-y
13 years ago

WP roles appear to be saved in the wp_options table under the "wp_user_roles" option_name.

The bbPress roles are not removed when BuddyPress is deactivated.

#4 @DJPaul
13 years ago

  • Component changed from Core to Forums
  • Keywords dev-feedback added; security roles removed
  • Milestone changed from Awaiting Review to 1.3

Thanks for investigating. This is a bit messy because if it's an existing (external) bbPress install, and BuddyPress removes those roles, we would break stuff in bbPress. Maybe BuddyPress can update the roles when the forums component is deactivated and bbPress had been installed by BuddyPress.

#5 @r-a-y
13 years ago

Sounds like a plan!

#6 @DJPaul
13 years ago

  • Milestone changed from 1.3 to Awaiting Review

I'm taking this out of scope for 1.3 as it's a tricky problem and upon further consideration, I can't think of a foolproof way of doing this. Need some more input from jjj.

#7 @DJPaul
13 years ago

  • Milestone changed from Awaiting Review to Future Release

(This issue should clear itself as people migrate to the bbPress plugin)

#8 @chrisclayton
12 years ago

  • Keywords close added
  • Severity set to normal

I believe this gets resolved in 1.6 with the capabilities page. (can't find related ticket).

#9 @r-a-y
11 years ago

  • Milestone Future Release deleted
  • Resolution set to wontfix
  • Status changed from new to closed

Another bbPress 2 takeover ticket!

Note: See TracTickets for help on using tickets.