Thank you Sam.
I am sorry, I could not assist you with your originally planned workflow. I am happy that the current work flow works though.

Regards
Brajesh

Hi Phil,
Thank you.
I do understand that your expectations are right but BuddyPress treats single item this way. You can check this by visiting a group and posting an activity and then clicking on the view link of that activity.

For single activity, group does not have an end point and it goes to user specific single page.

We do bring people to a group if there are more than 1 notifications from a group(we simply point them to groups activity stream).
In case of single activity, pointing to permalink seems reasonable to me.

If you want, I can point to the group activity stream.

Please do note that unlike Facebook, BuddyPress groups does not have single activity end point(does not handle single activity permalink).

Regards
Brajesh

Hi Mic,
I did release an update for visibility fix on another thread but missed the admin bar update. Will be adding in next iteration.

Thank you
Brajesh

Hi Rick,
Thank you.

Please put this code in your bp-custom.php

/**
 * Add user as subscriber to current blog.
 *
 * @param int $user_id user id.
 */
function buddydev_custom_add_to_blog_on_register( $user_id ) {
	// add as a subscriber to current blog.
	add_user_to_blog( get_current_blog_id(), $user_id, 'subscriber' );
}

add_action( 'user_register', 'buddydev_custom_add_to_blog_on_register' );

That will add a user to current blog on signup.

Bets Regards
Brajesh

Oops. It seems I have been messing it.

Please keep using your own for now. It does causes double query but is still better than my suggestion.

I will share better code later today.

regards
Brajesh