[buddypress-trac] [BuddyPress Trac] #5367: WP Admin BuddyPress profile when BuddyPress is not network activated
buddypress-trac
noreply at wordpress.org
Mon Feb 3 18:31:01 UTC 2014
#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):
Thanks for your reply
Replying to [comment:1 boonebgorges]:
> Your last_activity trick seems like a huge amount of additional overhead
to account for an edge case.
That's the other disadvantage of this way, i agree + needs a refresh to
take in account #5128
> Is there some reason why we don't already `add_user_to_blog()` for new
users, as you suggest in your add-to-blog.diff patch? Doesn't it make
sense for us to be doing this in *all* cases, not just in the particular
config here?
Well, we could use the add_to_blog usermeta in registration process. But
- only the new signups would be concerned not all the members, so we would
need a tool to "repare", or repare progressively by using
{{{add_user_to_blog()}}} if logged in user is not a member of the blog
- having this usermeta for all cases makes sense, but it would confuse
Administrator as they may be used to find their members in network admin
users screen and there only.
- the problem for the "Community Profile" only appears on this particular
config as BuddyPress is not network activated.
We could, avoid the additional overhead by not trying to have an
exhaustive 'All' tab, and by only adding the tab named "Members".
--
Ticket URL: <https://buddypress.trac.wordpress.org/ticket/5367#comment:2>
BuddyPress Trac <http://buddypress.org/>
BuddyPress Trac
More information about the buddypress-trac
mailing list