Hi Shyam,
Hope you are doing well.

For the time being, Please enable strict mode and the plugin should work. I am still having issue with getting it work in non strict mode for the languages needing multibyte support(Thai, Chinese etc). The strict mode will work.

Please give it a try.

Regards
Brajesh

Hi Tosin,
Thank you for the feedback. I am one of the early testers of the rewrite project and if there is any issue, Please be assured that it will be resolved.

once we test all our plugins, we will be submitting feedback to Mathieu .

Regards
Brajesh

Hi Khalid,
Thank you for using the plugin.

I think you are looking at the problem the wrong way.

Your problem is user not selecting a group type(which is an issue with BuddyBoss not enforcing it) and not that Group Tabs Pro is doing something.

With Group Tabs Pro, you are able to apply changes to all groups or scope to groups with some specific group types. We do plan to add “No Group Type” as scope in future but that is not the real issue.

For now, I will suggest reaching out to BudddyBoss support and asking them how to enforce atleast one type selection for group types.

Regards
Brajesh

Hi Darshan,
You were right. The code from Ravi used an API function that did not return hidden group if the user is context was not logged.

Here is the updated code. Please make sure to update the profile field id with your own.

/**
 * Retrieves all group ids of which the user is a member or has requested membership or is banned.
 *
 * @param int $user_id user id.
 * @param int $limit per page.
 * @param int $page page number.
 *
 * @return array
 */
function bd_get_user_group_ids( $user_id, $limit = false, $page = false ) {
	global $wpdb;

	$pag_sql = '';

	if ( $limit && $page ) {
		$pag_sql = $wpdb->prepare( " LIMIT %d, %d", intval( ( $page - 1 ) * $limit ), intval( $limit ) );
	}

	$bp = buddypress();

	$group_sql = $wpdb->prepare( "SELECT DISTINCT group_id FROM {$bp->groups->table_name_members} WHERE user_id = %d {$pag_sql}", $user_id );

	return $wpdb->get_col( $group_sql );
}

/**
 * Sync user's groups
 *
 * @param int   $user_id       User id.
 * @param array $new_group_ids New group ids.
 */
function buddydev_sync_user_groups( $user_id, $new_group_ids ) {

	if ( ! $user_id || ! $new_group_ids || ! function_exists( 'groups_leave_group' ) ) {
		return;
	}

	$existing_user_group_ids = bd_get_user_group_ids($user_id );

	$removable_group_ids = array_diff( $existing_user_group_ids, $new_group_ids );
	$new_join_group_ids  = array_diff( $new_group_ids, $existing_user_group_ids );

	foreach ( $removable_group_ids as $group_id ) {
		groups_leave_group( $group_id, $user_id );
	}

	foreach ( $new_join_group_ids as $group_id ) {
		groups_join_group( $group_id, $user_id );
	}
}

/**
 * Sync user's groups on field save.
 */
add_action( 'xprofile_data_after_save', function ( BP_XProfile_ProfileData $object ) {
	$field_id = $object->field_id;

	// Replace field id with yours field id.
	$group_field_id = 5;

	// If not our field id return.
	if ( $group_field_id != $field_id ) {
		return;
	}

	$new_group_ids = wp_parse_id_list( $object->value );

	if ( empty( $new_group_ids ) ) {
		// should we remove existing groups?
		// let us avoid that for now.
		return;
	}

	buddydev_sync_user_groups( $object->user_id, $new_group_ids );
} );

This code does not need the the Auto group join plugin. You can still use the plugin for other purpose.

Regards
Brajesh

Hi mdc,
Thank you for the question.

No, The plugin is not able to handle multiple conditions currently. The plugin does not load fields/options via ajax, It simply shows/hides them.

If you are referring to our Ajax Registration plugin, then yes, the current code is compatible.

Regards
Brajesh