BuddyPress.org

In fact I have found a reasonable solution using CSS. I found some key clues on in the support forum for this plugin: Buddypress Xprofile Custom Fields Type (though I’m not using that plugin).

If anyone has any advice about how to improve this I would be glad to hear it. Thanks

/* Buddypress profile field description position*/
.editfield {
position: relative;
top: 5px;
}
.editfield label {
font-weight:bold;
margin-bottom: 30px;
}
.input field_4 {
margin-top: 5px;
}

form.standard-form p.description {
margin: 0 0 15px;
position: absolute;
top: 20px;
line-height:1em;
}

Hi Valuser,
That’s exactly what I mean Valuser. The way they do it right now is by using third party plugins called BP Multinetwork by segregating databases for every subsite.

My idea is that, it need not be segregated to achieve this. Actually, WordPress does this very well with Multisite. Buddypress can do it too if it stored the blog ID value in database for every activity captured, groups and members. That way you can design options to filter members of the present site, activity and groups that can all have separate and sitewide data. This way they don’t have to segregate database by the BP Multinetwork plugin and still have separate activity, groups and members. Better thing is you can “Internetwork”. Which means, you can have a group that is subsite specific and still build an option to share it with another subsite/main site as well, within the network/multinetwork platform.

Thanks Henry. I’ve got more info on this to help the core team fix this issue.

I think all WordPress conditionals are not working correctly inside the bp_after_has_activities_parse_args filter. Only BuddyPress conditionals are working inside it.

I also have custom member pages too using bp_after_has_members_parse_args, but WordPress conditionals inside that are all working fine, example:

// filter member pages
function cm_members_filter( $retval ) {

	if ( is_page('custom-page-3') ) {
		$retval['per_page'] = 1;
	}	
	
	if ( is_page('custom-page-4') ) {
		$retval['per_page'] = 5;
	}	
	
	if ( is_search() ) {  
		$retval['per_page'] = 3;
	}	
		
    return $retval;
}
add_filter( 'bp_after_has_members_parse_args', 'cm_members_filter' );

It is just the activity parse args that is having problems with WordPress conditionals. I can provide further info to help figure out why WordPress conditionals don’t work correctly inside bp_after_has_activities_parse_args, it has something to do with the way ajax is used on the load more button to load more items:

If I remove activity ajax features by removing <div class=”activity”></div> or by removing bp-templates/bp-legacy/js/buddypress.min.js. The load more button now works like a pagination next page button (similar to the members directory pagination). This makes the WordPress conditionals work fine and all my custom activity pages are now filtering correctly.

So to conclude, WordPress conditionals are working OK inside bp_after_has_members_parse_args, but they are not working correctly inside bp_after_has_activities_parse_args unless the activity ajax is removed.

I actually didn’t know about that, I’m fairly new to WordPress. I’ll certainly update that and the companion queries that go with it once I can get this function sorted out.

Done. Trac ticket is here

Yes @henrywright, the settings are correct.

Steps to repeoduce:

1. Install vanilla WordPress 4.4
2. Install vanilla BuddyPress 2.4.3
3. Use default theme
4. Post a status update
5. Create a new user
6. Log in as new user
7. Comment on status

Just to be clear, I’m talking about notifications in WordPress toolbar. Have not checked if email notifications work since I’m on localhost.