BuddyPress.org

In reply to my above situation, I went to the WordPress Codex page which lists all the hooks available to developers. On this page, you can see a listing of things used as the first parameters for the add_filter('hook','your functions to run on that hook') method.

There was an example listed in that Codex that referenced exactly what I was trying to accomplish, namely, removing ‘Private: ‘ from private forum titles.

Below is the code that I am using now, it strips ‘Private:’ as well as leaving my profile page without any of the wierd markup that the previous code was using (note the previous code was from a post in ’09, so things likely changed since then):

/* Removing private prefix from post titles */ 

 
function spi_remove_private_protected_from_titles( $format ) {
	return '%s';
}
add_filter( 'private_title_format',   'spi_remove_private_protected_from_titles' );

I resolved this issue, but another remains:

Yesterday, I was getting frustrated with the bbPress (a forum plugin for WordPress), because when I’d have a private forum, instead of it just being an attribute, it prepended ‘Private: ‘ before every forum.

In my attempt to resolve this issue, I found a similar thing to what JSHelp referenced in this Stack Overflow Post: a code that would be located in the theme’s (my theme was Twenty-Fourteen) functions.php file.

My attempt to resolve THAT issue, led to THIS issue (where we have HTML code being converted to non-code text on the buddyPress profile page).

On removing the code from function.php, the issue fixed itself.

However, I am unsure why these two interact in the way that they do, below is the code I added and later commented out:

function the_title_trim($title) {
	// Might aswell make use of this function to escape attributes
	$title = attribute_escape($title);
	// What to find in the title
	$findthese = array(
		'#Protected:#', // # is just the delimeter
		'#Private:#'
	);
	// What to replace it with
	$replacewith = array(
		'', // What to replace protected with
		'' // What to replace private with
	);
	// Items replace by array key
	$title = preg_replace($findthese, $replacewith, $title);
	return $title;
}
add_filter('the_title', 'the_title_trim');

I also have the same problem.
Occurs in hidden group and private group.

I also hope to resolve this problem.

@bp-help I guess form this previous forum topic he’s wanting to create just utilize private messages https://buddypress.org/support/topic/using-buddypress-messaging-in-a-unique-way/

@sparkingproducts Can you gives us more detail of what you trying to accomplish because it could be as simple as deactivating a component or styling CSS elements to be hidden

change whatever you want in the arguments

function filter_send_message_btn() {

		$args = array(
			'id'                => 'private_message',
			'component'         => 'messages',
			'must_be_logged_in' => true,
			'block_self'        => true,
			'wrapper_id'        => 'send-private-message',
			'link_href'         => bp_get_send_private_message_link(),
			'link_title'        => __( 'Send a private message to this user.', 'buddypress' ),
			'link_text'         => __( 'Private Message', 'buddypress' ),
			'link_class'        => 'send-message',
		);

		return $args;

}
add_filter('bp_get_send_message_button_args', 'filter_send_message_btn');

Hi @espellcaste

Try adding this to compose.php right under the private message <textarea></textarea>

wp_editor( '', 'content' );

I do believe that should be enough to get the basic editor working for private messages on the compose screen.

Note 1: Untested

Note 2: You can also pass an array of arguments in the form of $settings. This is optional. It will let you do slightly more advanced stuff like load TinyMCE or quicktags. See the Codex link above for more info.

As an admin you can contact all uses using a sitewide notice. This depends on the messaging component being activated. If you want to contact members individually or if you want to disable private messaging then the only option I can see is to email them directly.