[buddypress-trac] [BuddyPress Trac] #8734: Introduce simple "Private Site" toggle

buddypress-trac noreply at wordpress.org
Sun Oct 9 17:06:12 UTC 2022


#8734: Introduce simple "Private Site" toggle
-----------------------------+-----------------------
 Reporter:  dcavins          |       Owner:  (none)
     Type:  feature request  |      Status:  assigned
 Priority:  normal           |   Milestone:  11.0.0
Component:  Core             |     Version:  10.4.0
 Severity:  normal           |  Resolution:
 Keywords:  has-patch        |
-----------------------------+-----------------------
Changes (by prbot):

 * keywords:  needs-patch => has-patch


Comment:

 ''This ticket was mentioned in
 [https://github.com/buddypress/buddypress/pull/25 PR #25] on
 [https://github.com/buddypress/buddypress/ buddypress/buddypress] by
 [https://github.com/imath imath].''
 The main idea is to unset the `buddypress()->pages` when the user hasn't
 the WP Cap mapped to a new `bp_read` one. As a result BP Globals like
 `current_component`, `current_action` and `action_variables` are not set
 and we end up into a `! is_buddypress()` area for not logged in members
 when the community visibility option is set to `members`. Activity RSS
 feed are then not set. I believe if we use this scenario, we'll need to
 edit the BP Rest API endpoints to use the `bp_current_user_can( 'bp_read'
 )` into the permissions_check methods.

 A benefit of this is the site admin can easily customize the default
 content displayed to not logged in members using the Block Editor for the
 corresponding BP Pages.

 Trac ticket: https://buddypress.trac.wordpress.org/ticket/8734

-- 
Ticket URL: <https://buddypress.trac.wordpress.org/ticket/8734#comment:17>
BuddyPress Trac <http://buddypress.org/>
BuddyPress Trac


More information about the buddypress-trac mailing list