BuddyPress.org

I asked seventhqueen for help and they said the problem is from buddypress, they can not help.

When you have a private group and go to approve some member the warning is showed but after approving, when the page reload saying that the membership was approved, the warning dissapears, is the only page where the warning is not being showed.

Set it as a private network?

This works and hides the button, but I’m curious. Can someone still send a private message to another user when they are “not” friends using URL manipulation or should the _wpnonce stop that?

It could be, difficult to answer since you have not given a great deal of detail on what features you want. You can create multiple extra profile fields which are searchable, you can use a plugin like BP Profile Search to enable all sections of the profile to be searchable, and of course BP supports public and private forums.

Have you tried deactivating all plugins and testing this? By default, activity in private groups stays within the group.

hi @masoud1111,

all i found was how to hide that button, or remove it.
but not show it only on some profiles

You just need to add some conditionnals.

Try this (in bp-custom.php) and give feed back if it works.

function bpex_private_message_button( $button ) {
$user = bp_loggedin_user_id();

    if ( is_super_admin() ) { 
		return $button;
	}

	if ( !empty( $user->roles ) && is_array( $user->roles ) ) {

		if ( $role == 'subscriber' || $role == 'contributor' || $role == 'author' || $role == 'editor' )  {
			// hide button for these roles
			$button = '';
		}
	}

	// allow the button to appear on admin's profile only
	if ( bp_is_active( 'xprofile' ) && bp_is_user() )  {	
		$user_id = bp_displayed_user_id();	
		// assuming admin's ID is 1
		if ( $user_id == 1 ) {
			return $button;
		}

	}

}
add_filter( 'bp_get_send_message_button', 'bpex_private_message_button', 1 , 1 );

1. Which version of WordPress are you running? 4.6.1

2. Did you install WordPress as a directory or subdomain install? directory

3. If a directory install, is it in root or in a subdirectory? root

4. Did you upgrade from a previous version of WordPress? If so, from which version? yes 4.6.0

5. Was WordPress functioning properly before installing/upgrading BuddyPress (BP)? e.g. permalinks, creating a new post, commenting. yes

6. Which version of BP are you running? 2.7.0

7. Did you upgraded from a previous version of BP? If so, from which version? 2.6.2

8. Do you have any plugins other than BuddyPress installed and activated? If so, which ones?

– AsynCRONous bbPress Subscriptions
– BackWPup
– BAW Login/Logout menu
– bbP private groups
– bbPress
– bbPress auto subscribe for new topics and replies
– BP Direct Menus
– BuddyPress
– BuddyPress for LearnDash
– BuddyPress NoCaptcha Register Box
– Cloudflare
– CodeStyling Localization
– Contact Form 7
– Content Aware Sidebars
– Custom Post Type Page Template
– Draw Attention
– Gallery Carousel Without JetPack
– Google XML Sitemaps
– LearnDash & BBPress Integration
– LearnDash – Gradebook
– LearnDash Content Cloner
– LearnDash LMS
– LearnDash Pro Panel
– LearnDash WooCommerce Integration
– Livemesh SiteOrigin Widgets
– MailChimp for WordPress
– Members page only for logged in users
– Page Builder by SiteOrigin
– Post Types Order
– Postman SMTP
– Prevent Content Theft Lite
– Revolution Slider
– Simple User Profile
– SiteOrigin Widgets Bundle
– Slideshow
– Slim Stat Analytics
– The Events Calendar
– Theme My Login
– Ultimate Posts Widget
– User Login Log
– W3 Total Cache
– Widget Importer & Exporter
– WooCommerce
– WooCommerce MailChimp
– WordPress Importer
– WP Better Emails
– WP Smush

9. Are you using the standard WordPress theme or customized theme? customized

10. Which theme do you use ? Invent

11. Have you modified the core files in any way? no

12. Do you have any custom functions in bp-custom.php? no

13. If running bbPress, which version? Or did your BuddyPress install come with a copy of bbPress built-in? 2.5.10

14. Please provide a list of any errors in your server’s log files. none

15. Which company provides your hosting? InMotion Hosting

16. Is your server running Windows, or if Linux; Apache, nginx or something else? Apache

I did the tests you recommended and it was my W3 Total Cache plugin that was causing the issue. I will have to look into that to figure out what setting was messing it up. @Scaffies doesn’t have that plugin, so guess our issues were caused by different things.

The function is working correctly on my install.

Perhaps you have an issue with quotes, ie after copy/pasting the snippet from a topic where the code whas inserted without using the code button.
Which software do you use to publish bp-custom ?

Copy/paste following and give a try:

function buddydev_hide_members_directory_from_all_except_admin() {

if ( bp_is_members_directory() && ! is_super_admin() ) {
//should we add a message too?
//bp_core_add_message( 'Private page.', 'error' );
bp_core_redirect( site_url('/') );
}
}
add_action( 'bp_template_redirect', 'buddydev_hide_members_directory_from_all_except_admin' );

https://wordpress.org/plugins/bp-simple-private/

This makes it so the only page you can view is the homepage, then make sure all you can see on the homepage is the login button? Either that or modify the above plugin so that it redirects to the login page.

This topic is titled “Function to hide private message depending of user role”.

and the snippet does that ! Subscribers have no access to the button. So far i remember it is also the default role in WordPress. You change that to your need.

The first condition in the snippet allows some users (by ID) to access the button, whatever their role.

If you want to add other WP roles, you simply copy the 2nd conditionnal if(role=='') and add another role if(role=='mamamouchi") { //do something }.

Or you use only the user ID if you have only a few members allowed to access. I litle understanding of php is of course a + to do that.
You have the basics in the snippet. Now, it’s to you now to make it work for your need.

Hi,

try this (goes to bp-custom.php)

function bpex_remove_private_message_button( $button ) {
$user = bp_loggedin_user_id();

    if ( $user == '4' || $user == '7' || $user == '25'  ) { // the allowed user ID's
	 return $button;
	}

	if ( !empty( $user->roles ) && is_array( $user->roles ) ) {

		if ( $role == 'subscriber') {
			$button = '';
		}
	}
}
add_filter( 'bp_get_send_message_button', 'bpex_remove_private_message_button', 1 , 1 );

No idea how to get specifically a pmpro defined user ID – you have to check their doc to adjust the above snippet. Note that it works on a standart install – without pmpro.