BuddyPress.org

Closing this duplicate https://buddypress.org/community/groups/creating-extending/forum/topic/extending-a-child-theme-adding-new-php-file-adding-member-invites-1/

A vaguely related group invite issue was addressed in BP 1.5.4. I suggest you upgrade asap and see if the problem goes away.

Can you create WordPress Pages ok? What do your permalinks for those look like? Can you create BuddyPress groups?

== define ( ‘BP_ENABLE_MULTIBLOG’, true ); how would this appear to work? ==
Didn’t see your earlier post https://buddypress.org/community/groups/how-to-and-troubleshooting/forum/topic/bp_enable_multiblog/

== does each blog have its own setting? ==
No, there’s only one instance of BP for a multisite installation by default.

== newly invited members (using “Invite Anyone” plugin, only appear as users in Network Admin and not on any blog. Is this a bug? ==
No it’s not a bug. It’s supposed to work like that for multisite even without Invite Anyone plugin. Can’t find the WP trac ticket that changed from user listed per site (old WPMU days) to sitewide user list (in WP 3.0).

BP Group Management works well and adds people to groups without sending friend requests: https://wordpress.org/extend/plugins/bp-group-management/

Invite Anyone is supposed to invite people via email and automatically place them in designated groups: https://wordpress.org/extend/plugins/invite-anyone/

Rewind then.

– Not out of the box. There’s no plugin that does exactly what you want. The Welcome Pack is a good start to invite people to join groups.

– BP Group Hierarchy doesn’t do that on the registration page.

Create one group that is hidden (maybe call it “Private Meetings”), this group will not show up on the site. Then invite those you want to have private discussions with. You can add and remove members for different discussions.

Private is basically read- and invite- only. https://codex.buddypress.org/getting-started/group-settings-and-roles/

First thanks to Boone Gorges for the direction on how to get started with this. And for those looking for a complete answer. Add this code (or similar) to your Theme functions.php file (my apologies if there is a better way to paste code…first time posting here):

function set_default_notifications($user_id, $key, $user) {
$valueyes = 'yes';
$valueno = 'no';

$new_messages = bp_get_user_meta_key('notification_messages_new_message' );
bp_update_user_meta( $user_id, $new_messages, $valueyes );

$new_notices = bp_get_user_meta_key('notification_messages_new_notice' );
bp_update_user_meta( $user_id, $new_notices, $valueno );

$group_invite = bp_get_user_meta_key('notification_groups_invite' );
bp_update_user_meta( $user_id, $group_invite, $valueyes );

$group_update = bp_get_user_meta_key('notification_groups_group_updated' );
bp_update_user_meta( $user_id, $group_update, $valueno );

$group_promo = bp_get_user_meta_key('notification_groups_admin_promotion' );
bp_update_user_meta( $user_id, $group_promo, $valueyes );

$group_request = bp_get_user_meta_key('notification_groups_membership_request' );
bp_update_user_meta( $user_id, $group_request, $valueyes );

$mention = bp_get_user_meta_key('notification_activity_new_mention' );
bp_update_user_meta( $user_id, $mention, $valueyes );

$reply = bp_get_user_meta_key('notification_activity_new_reply' );
bp_update_user_meta( $user_id, $reply, $valueyes );

$send_requests = bp_get_user_meta_key('notification_friends_friendship_request' );
bp_update_user_meta( $user_id, $send_requests, $valueyes );

$accept_requests = bp_get_user_meta_key('notification_friends_friendship_accepted' );
bp_update_user_meta( $user_id, $accept_requests, $valueno );
do_action( 'bp_core_notification_settings_after_save' );

}
add_action('bp_core_activated_user', 'set_default_notifications', 10, 3);

This is a great post but what about moving sub links to a new parent item, this kinda works but if I remove the parent item the function stops. in my themes functions.php

`function remove_blogs_nav() {
bp_core_remove_nav_item( ‘privacy’ );
bp_core_remove_nav_item( ‘settings’ );
bp_core_remove_nav_item( ‘invite-anyone’ );
}
add_action( ‘bp_setup_nav’, ‘remove_blogs_nav’, 15 );

function bp_add_create_group_subnav() {
global $bp;
$groups_link = ‘/groups-2/’;
$settings_link = $bp->loggedin_user->domain ;

/* Add the subnav items to the groups nav item */
if (function_exists(‘bp_core_new_subnav_item’)) {
bp_core_new_subnav_item( array(
‘name’ => __( ‘Create Clan’, ‘buddypress’ ),
‘slug’ => ‘create’,
‘parent_url’ => $groups_link,
‘parent_slug’ => $bp->groups->slug,
‘screen_function’ => ‘groups_screen_group_home’,
‘position’ => 40,
‘item_css_id’ => ‘home’ ) );

bp_core_new_subnav_item( array(
‘name’ => __( ‘Settings’, ‘buddypress’ ),
‘slug’ => ‘settings’,
‘parent_url’ => $settings_link,
‘parent_slug’ => $bp->profile->slug,
‘screen_function’ => ‘profile-settings’,
‘position’ => 30,
‘item_css_id’ => ‘profile-settings’ ) );

bp_core_new_subnav_item( array(
‘name’ => __( ‘Privacy’, ‘buddypress’ ),
‘slug’ => ‘privacy’,
‘parent_url’ => $settings_link,
‘parent_slug’ => $bp->profile->slug,
‘screen_function’ => ‘profile-privacy’,
‘position’ => 30,
‘item_css_id’ => ‘profile-privacy’ ) );

}
}
add_action(‘bp_setup_nav’, ‘bp_add_create_group_subnav’);
`
If I comment out :
`// bp_core_remove_nav_item( ‘privacy’ );
// bp_core_remove_nav_item( ‘settings’ );`

The sub links are in the Profile item, and functional, but still link to each original man item.

thanks Boone you are a lot of help

something like this (add to your theme functions php file)


function etivite_remove_group_invites_step() {
global $bp;

unset( $bp->groups->group_creation_steps );
}
add_action( 'bp_groups_setup_nav', 'etivite_remove_group_invites_step', 9999 );


Bump to the max! The friend component of BP is not appropriate for most of the sites I’ve made. This makes inviting users to groups impossible. It’s all the more confusing since BP asks who can invite people to the group when creating it, regardless of if the friend component is active or not.

In short – feature request for inviting any user (hopefully with a suggesting text-field) regardless of if they’re friends or not.

In BuddyPress 1.5, the parent slug for an individual group is not ‘groups’ or $bp->groups->slug. Instead, it is the single item slug (ie the group slug). Try this:
`bp_core_remove_subnav_item( bp_get_current_group_slug(), ‘send-invites’ );`

It’s a bit weird. If you disable avatar uploads in Settings, it’ll remove from the group step; however, you’ll also turn off member avatar uploads at the same time. Doh.

Try something like this in a bp_init hook (or somewhere after BP’s loaded):
`
global $bp;
unset( $bp->groups->group_creation_steps );
`

I’m pretty sure that is completely against Facebook terms of service. They’ve blocked Google from accessing your contacts as well as other services. They do not want you stealing your friends away from their advertisers.

This may help with getting users to invite https://buddypress.org/community/groups/invite-anyone/

@darrenmeehan

Hi. Some URLs can be changed, some others need to be changed in the theme (or core), unfortunately.
In BP 1.5, root-level pages e.g. .com/members and .com/groups are controlled by standard WordPress Pages. You’ll be able to rename title and slug by editing the Page details.

URLs like e.g. .com/members/admin/**groups**/ are changed as detailed on https://codex.buddypress.org/extending-buddypress/changing-internal-configuration-settings/ (“Change the URL slugs of BuddyPress components”).

URLs like e.g. com/groups/group_name/**send-invites**/ have to be changed by editing the theme files, and filtering parts of the BuddyPress core output.