BuddyPress.org

For anyone who is looking for the solution for not being able to save buddypress settings.

Various plugins cause issues with adding various extra css in the admin area.

in my case there was a css file from a Codecanyon Woozone plugin which hid the P tags in the buddypress options pages

use firebug and find the bottom div that cotnains the submit button and disable any css that is hiding it and you can click the submit button.

after you have done that you might want to tell the plugin developer that caused the issue about it.

TLDR the button is there its probably just hidden. use firebug or chrome tools to unhide it and click save.

Having same problem with Danish language.
Have added both .mo and .po to wp-content/buddypress/languages/ but can’t see the translations…
However, bbpress seems to be getting the translations OK …

Replied to some people at https://wordpress.org/support/topic/problem-with-buddypress-plug-in-on-sweetdate-theme?replies=10

Fixed in BuddyPress 2.6.1.1 released minutes ago.

Please check the forum before asking for a same question posted a few hours before yours!

How do you setup the crop tool on the Cover Image upload?

Closing this topic as duplicate.

Deactivate loco translate and redo what i described previously.
Search also for evtl. issues mentionned on loco translate support.

Aside there is no reason to use that plugin if you don’t translated scecificcally BuddyPress to your nedd. sv_SE.po/mo are loaded automatically.
If despite this, you use your own translation version, see how to prevent your translation to be overidden. It’s explained in one of the sticky topics on the plugin support.

Yep, we missed a bug in testing. Will be fixed in 2.6.1.1 release later today.

We’re very sorry.

Bug report is https://buddypress.trac.wordpress.org/ticket/7153

rest all can be done with buddypress private groups….regarding this “view the package we sent them and be able to download them” do you want to offer digital downloads?

https://downloads.wordpress.org/plugin/buddypress.2.6.1.zip

I’m unable to reproduce your issue. WP and BP language update is working properly.

BuddyPress har uppdaterats utan problem.

Guess it is this who genrate now an issue.
I have tried to update the po file with a new mo file but no difference

Po & mo are not the same file, and mo is compiled…

Remove all bp language files from /language/
Deactivate and reactivate BP – this will force BP to reach his translation.

@fifnicke,

do you have an issue with WDS BuddyPress Cover Photo ? If yes, please open a ticket on that gist. Or at least give some information about what you’re doing.

Related:

PHP Fatal error on BP 2.6.1 activation

bp_activity_add() will add an item to the activity stream. It sounds like you want to add a notification. Try bp_notifications_add_notification():

bp_notifications_add_notification

Hi,

please don’t double post ! Closing this topic. Discussion goes here:

Getting error saying Buddypress Group photo large?

Yes, this is a known issue, likely introduced in BuddyPress 2.6.1. Will be fixed asap.

@destac There are different ways to implement the new feature. For the screenshot, I did it in 4 simple steps.

Note that you might need to adjust how the widgets are registered, named, or styled based on your theme.

1. Registered three new widget areas in the child/theme’s functions.php file.

<?php // Only add this line if you are adding this to an empty functions.php file
/**
 * Register three widget areas for Members front page.
 *
 * @since My Child Theme 2.6.0
 */
function my_child_theme_widgets_init() {
	register_sidebar( array(
		'name'          => __( 'bp-members-1st', 'my-child-theme' ),
		'id'            => 'bp-members-1st',
		'description'   => __( 'Appears on each member\'s front page.', 'my-child-theme' ),
		'before_widget' => '<aside id="%1$s" class="widget %2$s">',
		'after_widget'  => '</aside>',
		'before_title'  => '<h2 class="widget-title">',
		'after_title'   => '</h2>',
	) );

	register_sidebar( array(
		'name'          => __( 'bp-members-2nd', 'my-child-theme' ),
		'id'            => 'bp-members-2nd',
		'description'   => __( 'Appears on each member\'s front page.', 'my-child-theme' ),
		'before_widget' => '<aside id="%1$s" class="widget %2$s">',
		'after_widget'  => '</aside>',
		'before_title'  => '<h2 class="widget-title">',
		'after_title'   => '</h2>',
	) );

	register_sidebar( array(
		'name'          => __( 'bp-members-3rd', 'my-child-theme' ),
		'id'            => 'bp-members-3rd',
		'description'   => __( 'Appears on each member\'s front page.', 'my-child-theme' ),
		'before_widget' => '<aside id="%1$s" class="widget %2$s">',
		'after_widget'  => '</aside>',
		'before_title'  => '<h2 class="widget-title">',
		'after_title'   => '</h2>',
	) );
}
add_action( 'widgets_init', 'my_child_theme_widgets_init' );

Adjust items registered in child theme based on how your theme is setting up the widget areas.

2. Created a new file front.php which should be located as follows: wp-content/my-child-theme-folder/buddypress/members/single/front.php
(Create the buddypress, members, and single directories/folders if you do not have those in your theme yet.)

Added the following in the front.php file:

<?php
/**
 * BuddyPress - Members Front Page
 *
 * @since My Child Theme 2.6.0
 */
?>

<div class="bp-member-front-wrap">

	<div class="bp-member-front-1">
		<?php dynamic_sidebar( 'bp-members-1st' ); ?>
	</div>

	<div class="bp-member-front-2">
		<?php dynamic_sidebar( 'bp-members-2nd' ); ?>
	</div>

	<div class="bp-member-front-3">
		<?php dynamic_sidebar( 'bp-members-3rd' ); ?>
	</div>

</div>

3. Added some styles:

.bp-member-front-wrap {
	clear: both;
	margin-bottom: 2em;
}

@media screen and (min-width: 46em) {
	.bp-member-front-wrap {
		clear: both;
		margin-bottom: 1em;
	}
	.bp-member-front-1,
	.bp-member-front-2 {
		float: left;
		margin-right: 1.5%;
		width: 32%;
	}
	.bp-member-front-3 {
		float: left;
		width: 32%;
	}
}

4. Went to Appearance > Widgets and add widgets to the Member Front Page Widget Areas.

As mentioned above, there are other ways to implement this new feature. Happy customizing!

Installing Group and Sitewide Forums

read the above carefully

BuddyPress 2.6.1 was just released, which fixes this issue.

wordpress.org still needs to be updated, but you can grab the release here:
https://downloads.wordpress.org/plugin/buddypress.2.6.1.zip

I think your question would be better suited on the bbPress forums since bbPress provides forum functionality for BuddyPress groups:
https://bbpress.org/forums

Hi @navyspitfire,

when you pick up code somewhere, you should also read the comments. The solution to your issue was in one of them.

Here is what wil exclude site admin from members directory and exclude also the logged_in user. The total member count will also be adjusted correctly on All members [x] tab and for the pagination count. $count-2 instead of $count-1 do the trick.

Excluded members, incl. admin, are of course excluded from search.

function bpex_hide_admin_on_member_directory( $qs=false, $object=false ){

	// Id's to hide, separated by comma
	$excluded_user = '1' ;

	// hide to members & friends 
	if($object != 'members' && $object != 'friends')
	return $qs;
	
	$args = wp_parse_args($qs);
	
	if(!empty($args['user_id']))
	return $qs;	
	
	if(!empty($args['exclude']))
	$args['exclude'] = $args['exclude'].','.$excluded_user;
	else
	$args['exclude'] = $excluded_user;
	
	$qs = build_query($args);
	
	return $qs;
	
}
add_action( 'bp_ajax_querystring','bpex_hide_admin_on_member_directory', 20, 2 );

// once admin is excluded, we must recount the members !
function bpex_hide_get_total_filter( $count ){
	return $count-2;
}
add_filter( 'bp_get_total_member_count', 'bpex_hide_get_total_filter' );

function bpex_exclude_loggedin_user( $qs = false, $object = false ) {

 //list of users to exclude
 if( !is_user_logged_in() )
     return $qs;

 //if the user is logged in , let us exclude her/him
 $excluded_user=  get_current_user_id();
  
 if( $object !='members' )//hide for members only
	return $qs;
  
 $args=wp_parse_args($qs);
  
 //check if we are listing friends?, do not exclude in this case
 if( !empty( $args[ 'user_id' ] ) )
	return $qs;
  
 if( !empty( $args['exclude'] ) )
	$args['exclude'] = $args['exclude'] .','. $excluded_user;
 else
	$args['exclude'] = $excluded_user;
  
	$qs = build_query( $args );
  
 return $qs;
  
}
add_action('bp_ajax_querystring','bpex_exclude_loggedin_user', 20, 2 );

Codex Reference

Playing with the user’s ID in different contexts

I’m using https://wordpress.org/support/plugin/mass-messaging-in-buddypress which seems to do the trick.