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

[buddypress-trac]

#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:  needs-patch      |
-----------------------------+-----------------------

Comment (by imath):

 Hi @dcavins

 Thanks a lot for your work and for the patch. I've tested the patch, it
 behaves as you described. Although efficient, I believe redirecting the
 user to the login screen when they have no access to the community area is
 not very user friendly or not very welcoming.

 Many thanks for your feedbacks @johnjamesjacoby I'll share a PR just after
 I've posted this comment that is following most of your suggestions
 (except: I've left new installs as "open" communities, but I agree we can
 consider it).

 You'll see in the PR that we can use a different approach, leaving users
 to use the WordPress Block Editor to set the content of the page displayed
 to the not logged in member. In short if the current user does not have
 the mapped WP cap to a new `bp_read` cap, BuddyPress globals are not set
 and no community content or RSS feeds are generated. We stay in a regular
 WP Post.

 If this post has no content, we can display a default one inviting the
 user to log in or register/request a membership.

 NB: the `private` post status was a bad idea (I can say it was bad as I
 was the first one to have it!) as you need to be at least an Editor to
 view pages having this post status. I wonder why WordPress made this
 choice in the first place...

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