[buddypress-trac] [BuddyPress Trac] #5367: WP Admin BuddyPress profile when BuddyPress is not network activated

[buddypress-trac]

#5367: WP Admin BuddyPress profile when BuddyPress is not network activated
-------------------------+-------------------------------------------------
 Reporter:  imath        |      Owner:
     Type:  defect       |     Status:  new
  (bug)                  |  Milestone:  2.0
 Priority:  high         |    Version:
Component:               |   Keywords:  has-patch 2nd-opinion needs-testing
  Administration         |
 Severity:  normal       |
-------------------------+-------------------------------------------------
 On a multisite config, it's possible to activate BuddyPress on a child
 blog instead of on the entire network. On this kind of configuration, the
 new WP Admin BuddyPress profile won't be available for all the community
 members, but only to the one that are users of the child blog.

 === Registration process ===
 When a user is created from the WordPress Administration of the one of the
 blog of the network, he becomes a user of this blog having the role the
 administrator specified
 When a user is created from the Users Network Administration screen, he
 doesn't belong to any blog.
 When a user is created using the BuddyPress signup process, the user won't
 belong to any blog.

 When BuddyPress is on non multisite config or activated on the network, i
 think we shouldn't change anything to this process, because people are
 used to :
 - find their users in their blog on non multisite config
 - find their members in users network administration on multisite config.
 - and everything works fine for the new WP Admin BuddyPress profile

 As problem only appears on this particular config : BuddyPress is not
 activated on the network but on a child blog, i think we have 2 options to
 deal with it :

 ==== Option 1 : using the add_to_blog usermeta  ====
 I've attached the [ticketnumber]-add-to-blog.diff as a starting point of
 this option. Using it, any new activated signup will be created as a
 network member and as a user of the blog where BuddyPress is activated.
 The benefit is we don't have to touch to the WP Admin BuddyPress profile
 code, the disadvantage of this is that, the "old" members won't be in the
 blog's users list. So it will surely need a tool to "repare" this
 situation in order to batch attach BuddyPress members as users of the
 blog. Problem is "what" is a BuddyPress member? The only way i saw in next
 option is something that will be soon deprecated (great work @boone on
 #5128, i need to test it asap :) ) : the 'last_activity' user meta.

 ==== Option 2 : "trick" patch ====
 In [ticketnumber]-trick.diff, i'm editing the WP Admin BuddyPress profile
 in order to list all the BuddyPress members (last_activity exists) without
 making them users of the blog. Using it, the Community administrator will
 be able to view all the members and not only the users of his blog. The
 benefit is we don't need to change the signup process and no specific tool
 will be necessary. The disadvantage is that it will quicky need a refresh
 to stop using last_activity meta.

 What do you think ? Option 1, Option 2 or another way ?

--
Ticket URL: <https://buddypress.trac.wordpress.org/ticket/5367>
BuddyPress Trac <http://buddypress.org/>
BuddyPress Trac