BuddyPress.org

Hi @darrenllrgmailcom, @adjunkten,

i had the same issue with a custom theme: fields didn’t wrap properly on small screens…
To solve it, i simply copied the concerned form rules from Twenty Sixteen into my child theme css and all went OK after that.

The 2016 rules of the register page:

#buddypress #signup_form.standard-form #profile-details-section,
#buddypress #signup_form.standard-form #basic-details-section,
#buddypress #signup_form.standard-form #blog-details-section {
	float: none;
	width: 100%;
}

@media screen and (min-width: 38.75em) {
	#buddypress #signup_form.standard-form #profile-details-section,
	#buddypress #signup_form.standard-form #basic-details-section,
	#buddypress #signup_form.standard-form #blog-details-section {
		width: 48%;
	}
}

@media screen and (min-width: 38.75em) {
	#buddypress #signup_form.standard-form #profile-details-section {
		float: right;
	}
	#buddypress #signup_form.standard-form #basic-details-section {
		float: left;
	}
}

Hi,

do you mean this plugin ? If it is the case, you have to ask the author directly.

Or if you only want to add some comment to a content you share, you can use this plugin. It is outdated but still working (i use it without trouble since years).

Depends where you need that and what you exactly want as result. You can hardcode something into the child theme template or use some CSS trick like this one.
Or maybe you need something like this ?

That said, be default, when you mention a user within a blog post or any update, a class name is automatically added: “bp-suggestions-mention”.

When you mention a user in a bbPress topic, there is no class name. But that’s lazy bbPress mentioning, not BuddyPress. If so, ask for this on their support.

it could be possible that your host plan doesn’t allow you to use BP.
it could be possible that you shouldn’t use php 7.1, as BP is not completely ready to use this latest php version.

To get sure, create a php info file and upload it at the site root (same level as wordpress)
Once uploaded, go to your-site/phpinfo.php. There you will see all information i asked you about your install. Check them and report them here please.

If you have an access to a php config via your host admin interface, go there and try to set it to php 5.6 or 7 instead of 7.1

Yes, it is not recommended to use 3rd partys automated WP installation tools. It is also not recommended to use page builders. Such tools are rarely updated, correctly maintained and often bugy… For 1.5$/mounth you can’t expect the creme de la creme, even if talented marketers try to suggest you the opposite.

Just jumping back in on this one.

I’ve been developing a large & complex WP site (60+ CPTs using Pods & BP) for the past few months on PHP 7.1. I ran all PHP 7.1 RCs and so far the only issues I’ve seen are related to BP. I’m now at the point where I’ve had to disable BP to continue development on PHP 7.1 (I need nullable types and void returns from PHP 7.1) and ignore any BP features I have on my roadmap until it’s stable (I hope soon 🙂 )

I can’t report any issues with WP-core and PHP 7.1 that I’ve witnessed.

No trying to say that BP is crappy 🙂 – just a hint that the issue may be more likely to be on BP side (especially since it seems that BBPress had a similar issue which they’ve already fixed – see my link in previous post).

The other issue I’m seeing on PHP 7.1 seems to be related to enabling Opcache and BP – https://buddypress.trac.wordpress.org/ticket/7361

Hope that’s helpful 🙂

Okay. The story is that PHP 7.1 is supported by WordPress 4.7 (or newer). Likewise, BuddyPress will need at least that version, too.

We’re currently tracking some unit test failures in PHP 7.1 (see the very bottom of https://travis-ci.org/buddypress/BuddyPress), but we’ve not figured out if they are our bugs, or some bug in WordPress core. Likewise, this do_action issue might be a regression WordPress should fix instead of us (if we’re getting caught by this, I bet many other plugins are, too).

At any rate, I’m going to try to fix the unit tests once I get a PHP 7.1 box set up (hopefully this week), and then I’ll test the basics of BuddyPress, and see what other issues crop up, and fix or report them as necessary.

I think I’d wait a month or two to use PHP 7.1 with WordPress and BuddyPress in the wild, to be honest.

install BuddyPress and only activate the Profile component.

Here the complete list of functions containing threat_id in their name:
http://hookr.io/plugins/buddypress/#index=g&search=thread_id

Hi,

please give more details… what kind of post ? Blog, update, forum….
By the way, BP doesn’t handle blog posts.
Read documentation about emails here:

emails: https://codex.buddypress.org/emails/
custom emails: https://codex.buddypress.org/emails/custom-emails/

I asked a bit too soon… A little more searching and I found your explanation here. Setting the default component seems to have done the trick. Thanks for the code samples!

Sorry, i don’t act privately on user’s site.

If you’re unable to solve your issue, hire somebody who can help you on BP Job Board.

Have you tried deactivating all plugins apart from BuddyPress and using the 2016 theme? Does it work then?

Get inspired from here:
https://buddypress.org/support/topic/list-groups-i-am-admin-of/#post-240213

Hi,

the only valid URL to theme customizer is:
../wp-admin/customize.php?return=%2Fwp-admin%2Fthemes.php

BuddyPress pages are not customizable like ordinary WP pages. BP pages have dynamic content and can be adjusted to any theme directly by CSS and a child theme. These page should only exist with a title, and nothing else.

Depending the theme you use, and his complexity, customize it to your need first. Once your WP works with the desired layout, you activate BuddyPress.

This should work flawless, out of the box generaly. If you estimate that some details, like a header width or an avatar size should be modified, you do that directly via CSS.
Read codex for more details about themes.

@henrywright

This work okey –>: but, How I can Hide Admin from BuddyPress Widget??

—->

// Deny access to admins profile. User is redirected to the homepage
function bpfr_hide_admins_profile() {
	global $bp; 
	if(bp_is_profile && $bp->displayed_user->id == 1 && $bp->loggedin_user->id != 1) :
		wp_redirect( home_url() );
	exit;
	endif;
}
add_action( 'wp', 'bpfr_hide_admins_profile', 1 );

// Hide admin's activities from all activity feeds
function bpfr_hide_admin_activity( $a, $activities ) {	
	
	// ... but allow admin to see his activities!
	if ( is_site_admin() )	
		return $activities;	
	
	foreach ( $activities->activities as $key => $activity ) {	
		// ID's to exclude, separated by commas. ID 1 is always the superadmin
		if ( $activity->user_id == 1  ) {			
			
			unset( $activities->activities[$key] );			
			
			$activities->activity_count = $activities->activity_count-1;			
			$activities->total_activity_count = $activities->total_activity_count-1;			
					$activities->pag_num = $activities->pag_num -1;				
		}		
	}		
	// Renumber the array keys to account for missing items 	
	$activities_new = array_values( $activities->activities );		
	$activities->activities = $activities_new;	
	
	return $activities;
	
}
add_action( 'bp_has_activities', 'bpfr_hide_admin_activity', 10, 2 );

// Remove admin from the member directory
function bpdev_exclude_users($qs=false,$object=false){
    
    $excluded_user='1'; // Id's to remove, separated by comma
	
    if($object != 'members' && $object != 'friends')// hide admin to members & 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','bpdev_exclude_users',20,2);

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

Try another browser, the zip from .org should not download to local. It could also be an issue if you installed BuddyPress from a one click installer. They sometimes create bad folder permissions.

Check your forum settings and sync WP and BP users.

Usually on a local site, and standard setup, while you use BP group forum, the forum slug is:
http://localhost/groups/group_name/forum/
If you use wampp, you should have a list of virtual hosts (aka site names), where you installed wordpress. This means also that wp is at the site root. If your site is called mario, you install wp there and then you should have http://mario/ Once BP is activated, you’ll get http://mario/members/ or http://mario/groups/ and so on…

The link to the forum user/author/commenter is
http://localhost/members/member_name/

When you use bbPress as standalone forum (aside or without BuddyPress), the link looks like

http://localhost/root_forum/single_forum/forum_name/
Link to user is the same as the one indicated previously.

More details here

Installing Group and Sitewide Forums

You can also follow the bbPress install guide if you use bbPress separately.

@danbp thank you , i’m a beginner my self and that’s how i did it , can you please answer my question here Broken user Link

@mohamedouqas, @vidalpaulo

if you want to change the labels for you theme you can go to your theme directory and search for these words and replace them. That’s a rough, dirty trick to avoid. 😉

Much more simple, and best practice by the way, is to use the language file shipped with your theme.

Customizing Labels, Messages, and URLs

But as we’re talking here about BuddyPress, most of the items are in the BP language file.

“Follower” sounds more like used by another plugin. But again, you’ll find it in that plugin language file.

2) There is a plugin: https://wordpress.org/plugins/buddypress-login-redirect/

3) you’re right, this need some custom coding. Read here how to do that:

Navigation API

If you search the forum, you’ll find many examples too.

Hi,

basically, you can get it by using WP’s get_bloginfo() function (read here).

There is also this BP function bp_blog_description(), which works when you’re in the blog loop.

You have also several action hooks in the blog template (bp-templates/bp-legacy/buddypress/blogs/blogs-loop.php) you can use to insert a blog description to the blog list.

No. Chat is plugin territory.

Hi @archie22is,

thank you for your report. But when you write such information, it is of your responsability to give correct information.

Such alarming title can confuse any user. It is unfair and to be honest, it is only concerning you (it’s your install who has that issue, not WordPress or BuddyPress, in their globality). Especially that the error message has nothing to do with BuddyPress.

In other words, you annonce 2 wrong information on the wrong forum.

The error is related to bbPress. And there is already a topic about this warning on WordPress support.

Read it and try to repair or add your own opinion to that topic.
Open also – if none exist – a topic on bbPress support.