BuddyPress should use mapped meta caps

[johnjamesjacoby]

Currently BuddyPress relies on a few stub functions and is_super_admin() to handle the things a user is capable of doing. This is rather lame, and provides no ability to align the moderation needs of your site with the users that are tasked with moderator level responsibility.

In r5304, r5305, and r5309, some API's were ported from bbPress 2.0 to get this started. Please use this ticket for discussion, patches, and commits towards BuddyPress roles and capabilities for the 1.6 dev cycle.

[johnjamesjacoby]

See #3739 for original ticket.

[boonebgorges]

See also #2348, which I'm closing in favor of this ticket since it's tied to things that have already been put into the BP trunk.

[johnjamesjacoby]

(In [5329]) Find/replace on is_super_admin() to use bp_current_user_can( 'bp_moderate' ). See #3740.

[johnjamesjacoby]

(In [5330]) Audit is_super_admin and is_site_admin usage. See #3740.

[johnjamesjacoby]

(In [5332]) Add is_super_admin() check to beginning of bp_current_user_can() while in development to keep trunk working normally. See #3740.

[johnjamesjacoby]

(In [5333]) Make all core functions available on installation. Needed for adding roles and caps. See #3740.

[boonebgorges]

I think that we have done as much with this during the 1.6 cycle as we are going to. Let's talk about it early in the 1.7 cycle to see how we're going to take it further.

[boonebgorges]

(In [5656]) Reconfigures require() order for loading process during installation and upgrade.
Corrects outdated function calls and path names in installation wizard.
See #3740.
Fixes #3875. Fixes #3802. See #3865.

[boonebgorges]

I'm against doing a massive refactor of our permissions structure just to meet the requirements of this ticket, especially during what is already turning out to be a crowded milestone. But I do think that we should leave this ticket open, and refactor individual instances as we see fit (and as it will actually be beneficial).

[DJPaul]

We're closing this ticket because it has not received any contribution or comments for at least two years. We have decided that it is better to close tickets that are good ideas, which have not gotten (or are unlikely to get) contributions, rather than keep things open indefinitely. This will help us share a more realistic roadmap for BuddyPress with you.

Everyone very much appreciates the time and effort that you spent sharing your idea with us. On behalf of the entire BuddyPress team, thank you.

If you feel strongly that this enhancement should still be added to BuddyPress, and you are able to contribute effort towards it, we encourage you to re-open the ticket, or start a discussion about it in our Slack channel. Please consider that time has proven that good ideas without contributions do not get built.

For more information, see ​https://bpdevel.wordpress.com/2018/01/21/our-awaiting-contributions-milestone-contains/
or find us on Slack, in the #buddypress channel: ​https://make.wordpress.org/chat/