[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 (bug)                         |      Status:  new
 Priority:  high                                 |   Milestone:  2.0
Component:  Administration                       |     Version:
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch 2nd-opinion needs-testing  |
-------------------------------------------------+------------------

Comment (by imath):

 Replying to [comment:3 boonebgorges]:
 > Is this the only reason why we don't currently do it? I could swear we
 used to add users to the blog at the time of registration.
 At the beginning i thought too :) Then i went back on 1.2.7 to check the
 registration process, because i was remembering using the add_to_blog
 usermeta for one of my plugin and i thought i had this idea watching
 BuddyPress code. But no. It seems on a multisite config, users have never
 been added to a blog during registration process.
 When i've found the trouble with Community Profile and the specific config
 "BuddyPress not activated on network but on a child blog" my first idea
 was to use add_to_blog usermeta for all config as it would ease a lot the
 signup patch i'm working on. But i thought if BuddyPress never used this,
 there might be a good reason, so i wasn't so sure at all that  changing
 this to config where BuddyPress is network activated was a good idea.
 a. in this "regular multisite" config, profile fields are set in the
 network admin, the community profile is available there too, so does
 activity and group administration, and i'm afraid that having the members
 on the regular admin would confuse super administrators, because they
 would search for the Profile field submenu or the community profile and
 they would only find "Edit or remove-from-blog actions".
 b. Regular administrator (without the capacity of managing network users)
 may be surprised to see this change too like "wow how come all this
 members arrived in my administration ?", so they could batch remove users
 from the blog and that may be problematic...
 That's why i've searched (again ;) ) a hardest way to avoid changing
 anything to the signup process.
 On the other hand, i agree it would ease everything!! So i'm in favor but
 a bit "sur la pointe des pieds" ;)
 > I don't understand this suggestion. Tabs on what? users.php?
 Sorry, actually the patch is adding a new view to the users.php WP List
 Table called members (that's what i've called a tab), the big overhead
 comes from the fact that i've tried to have in the "All" view : users of
 the blog + members.
 So i was saying that only having the members view added would be enough if
 we prefer not to go in the "add_to_blog + repare" way. This view is only
 available to "can manage network users" admins and for the specific case
 where BuddyPress is not network activated.

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