BuddyPress.org

@ultimateuser

create bp-custom.php and place it in wp-content/plugins, not wp-content/plugins/buddypress.

copy directly and paste the code below into bp-custom.php you created.

add_filter( 'bp_activity_do_mentions', '__return_false' );

The activity feed in BP has a filter that you can use to select things like All posts, All Comments, All Activity Updates etc. It’s a dropdown on the activity feed. It sounds like what you want is for it to default to just posts, and not to everything (avatar changes, friend requests etc.)

This might help:

How To Customize The BuddyPress Activity Loop

Here’s another topic in which the user was trying to do something similar

https://buddypress.org/support/topic/show-updates-as-default-in-activity/

@aravere

Try upgrading to bp 1.9+ it has had some attention in the user name area: https://buddypress.trac.wordpress.org/ticket/5185 and https://buddypress.trac.wordpress.org/ticket/4622

Cool. Good luck with it. Breaking up your questions also means that someone doesn’t look quickly at this thread and assume everything is solved. Hope it works out.

BTW: Found this that might help the other issue. Haven’t tested it but Brajesh is a brilliant dude so I assume it will probably work. Just follow along on the comment thread below the snippet: it’s hard to tell if he updated the code, or just suggested how to do so.

Prevent spaces in WordPress/BuddyPress Usernames

In the BuddyPress settings, you could just turn off the Friend component.

1. Have you disabled site tracking? Try going to the WP dashboard where you can disable and enable BuddyPress components and check that site tracking is enabled.

2. Maybe check entries are recorded when using a different theme? Twenty Thirteen is a good tried and tested one.

In the BuddyPress admin area, you need to assign a WordPress page (created in the Dashboard under Pages/New) with a BP component. This codex page explains in more detail

Configure BuddyPress

The difference is in the scale and the level of complexity.

buddypress + WordPress on a single site is relatively simple to setup
wheras Buddypress+ WordPress Multisite is more complex and requires additional hosting resources

The functionality difference is on a single site install your users will be posting to a single blog whereas on a multisite instaall each user would have their own blog to post to.

If you are just seting up the site then my advice would be keep it simple and go for a single site WordPress+Buddypress setup

I’m a great believer in keeping things simple,and WordPress Multisite creates an additional layer of complexity which you probably do not require in initially.

The problem here is the bp_has_message_threads() function itself. It comes with hardcoded checks to override the $box to sentbox or inbox based on the results of bp_is_current_action().

You could try something this, in lieu of bp_has_message_threads():

function bp_custom_has_message_threads( $args = '' ) {
	global $messages_template;

	$r = wp_parse_args( $args, array(
		'user_id'      => bp_loggedin_user_id(),
		'box'          => 'inbox',
		'per_page'     => 10,
		'max'          => false,
		'type'         => 'all',
		'search_terms' => isset( $_REQUEST['s'] ) ? stripslashes( $_REQUEST['s'] ) : '',
		'page_arg'     => 'mpage', // See https://buddypress.trac.wordpress.org/ticket/3679
	) );

	if ( bp_is_current_action( 'notices' ) && !bp_current_user_can( 'bp_moderate' ) ) {
		bp_core_redirect( bp_displayed_user_domain() );
	}

	$messages_template = new BP_Messages_Box_Template( $r['user_id'], $r['box'], $r['per_page'], $r['max'], $r['type'], $r['search_terms'], $r['page_arg'] );

	return apply_filters( 'bp_has_message_threads', $messages_template->has_threads(), $messages_template );
}

this link might help you understand how the two work together:

WordPress Blogs

multisite is just activated by a setting in your wordpress config file it can be done before or after buddypress but if you are starting from scratch id probably do the multisite first, then add any plugins.

Copy it to your theme or child-theme

See ‘Overloading Template Compatibility theme files’ here:

Theme Compatibility & Template Files

The easiest path is just to add a conditional to an override of this template:
buddypress\bp-templates\bp-legacy\buddypress\members\single\profile\edit.php

The name field is, I believe, always:
input type="text" name="field_1" id="field_1"

So in the template, change this:
if ( 'textbox' == bp_get_the_profile_field_type() )

to:
if ( 'textbox' == bp_get_the_profile_field_type() && 'field_1' != bp_get_the_profile_field_input_name() )

and add an ‘else’ to just show the name value – bp_the_profile_field_edit_value()

Root profiles are not deprecated, though we have some planned obsolescence for almost all of our global constants, moving them into functions with filters and/or options.

Our rewrite rules improvements for BuddyPress 2.0 will ideally enable any component to exist at a root level. At the time that code was written, it solved an immediate problem for us, but going forward this feature should not be exclusive to profiles.

In your theme dir, create an over-ride of this file.
buddypress\bp-templates\bp-legacy\buddypress\members\members-loop.php

How to over-ride a BP template

Theme Compatibility & Template Files

In the over-ride, remove this code:

<div class="action">
	<?php do_action( 'bp_directory_members_actions' ); ?>
</div>

I have never tried to use “BuddyDev bp multinetwork” but as you described your problem it looks like it has something to do with “BuddyDev bp multinetwork” and not BuddyPress it self. To be more specific I think you should recheck your domain mapping settings.

http://codecanyon.net/item/buddypress-profiles-statistics/2215514

Hi @josswinn

Is this ticket related to your problem by any chance?

https://buddypress.trac.wordpress.org/ticket/4680