[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:  has-patch        |
-----------------------------+-----------------------

Comment (by imath):

 David’s patch is very efficient I agree. My problem with it is, it’s
 throwing the user to the login page without more explanation and I believe
 (I can be wrong, of course), as Admin users often request more & easy
 customization, we should enjoy the post content of the corresponding page
 to let them use block widgets (BP Login form for instance) and any other
 block to attract users to engage into their private community. So it seems
 to satisfy both potential needs.

 Disabling the community restriction can still be done easily in my patch
 filtering into the mapping caps function, remapping {{{bp_read}}} to
 {{{exist}}}

 Another option, can be to leave the legacy parser do the parsing job to
 set constants then add a hook to let plugin shortcircuit a potential reset
 of this constant if the user is not loggedin. I believe it could satisfy
 Admin users need for « a better UI than the login form to welcome new
 members » and plugin authors ones 😅

 Another option could be to use a specific directory to welcome these users
 using templates from template packs…

 @sbrajesh we need to care a lot about plugins & themes, we think about
 them almost each time we’re adding a new feature, end users don’t see a
 difference between BuddyPress and BuddyPress plugins/themes, it just
 doesn’t work for them and they don’t have time to find what is wrong, they
 move to another community software. That’s why we always put complicated
 backcompat code and why we are now using the feature as a plugin model to
 try to prevent potential issues with plugins (unfortunately not many
 plugin authors are testing them, but that’s another story 😇)

 That being said, many thanks to you and @shawfactor for contributing to
 this ticket 😍

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