BuddyPress.org

@petervandoorn

I also have this problem running WordPress 3.9.1, BuddyPress 2.0.1 and BBPress 2.5.4. It’s only been the case since I moved over to BBPress for forums.

I’m happy to help anyone who’s trying to fix this apparent bug.

These other threads appear to be relevant:

https://buddypress.org/support/topic/private-group-topics-appearing-in-activity-stream-help/ (@kraigg)
https://buddypress.org/support/topic/bugs-between-bbpress-and-buddypress/ (@jboye, @johnjamesjacoby)

@jarith Marking this topic as resolved.

As to removing the “Private” and “Protected” prefices, you could try adding bbPress forum conditional to your function or to the one Konstantin (first comment in that post) posted
e.g.

if ( class_exists('bbPress') ) {
      if ( is_bbpress() ) {
         // do this
      }
}

Undoubtedly, you’ll get additional support at the bbPress forums 🙂

but I do not want “non-business” user types to be able to join the business groups

@farmer121 you can make the business groups either “private” or “hidden”

Ok, we’re closer, looks like the correct bbPress forum ID is correctly associated with the BuddyPress Group 🙂

It looks like the slug/permalink is broken 🙁

Before looking at a fix, a clarification if I could

Here is my bbPress Forums Hierarchy Structure Layout

 
BuddyPress Forums Category (Top Level Category)
— BuddyPress Public Group Forum (Forum)
— BuddyPress Hidden Group Forum (Forum)
— BuddyPress Private Group Forum (Forum)

In bbPress Settings (Settings -> bbPress) (/wp-admin/options-general.php?page=bbpress)

 
“BuddyPress Integration” -> “Group Forums Parent” is set as “BuddyPress Forums Category”

My bbPress settings for forum slugs are:

 
– Forum Root Slug -> forums
– Forum Prefix -> Check/Tick
– Single Forum Slugs -> Forum -> forum

So my URL’s are build with the “forum root slug” then the “forum single slug” then “BuddyPress Forums Category” and lastly the actual forum “BuddyPress Public Group Forum” which results in:

/forums/forum/buddypress-forums-category/buddypress-public-group-forum/

Now onto your URL’s:

Yours with bbPress forum ID 127650

 
/forums/forum/forums-2/f1/correct-group-name/

Yours with bbPress forum ID 127628

 
/forums/forum/forums-2/name-of-another-group/

These infer the following:

 
forums-2
— f1
— — correct-group-name
— name of another group

With your settings:

 
“BuddyPress Integration” -> “Group Forums Parent” is set as “forums-2”
– Forum Root Slug -> forums
– Forum Prefix -> Check/Tick
– Single Forum Slugs -> Forum -> forum

As long as the quote/code formatting displays as expected is this what your bbPress forums layout hierarchy looks like?

EDIT: Tweaked the formatting above and just trying to digest where the forums-2 comes from and why it is there, the f1 no doubt is part of the incorrect forum slug that we can get to with the fix, I’ve got to go dig through some source code of bbPress & BuddyPress to workout where things are broken and how to fix it.

I’m not having a registration page
how to create a registration page
Note: This is a private group, to belong to him, you must register on the site and request membership.

@hragupathi
Do you mean keep profiles private from logged out visitors or do you mean keep profiles private for logged in users? Please clarify a little better as to what your trying to achieve.

You’ll need /members/username/messages/ in order for private messages to work. You could disable the rest such as /members/username/settings/ using a redirect function hooked to template_redirect

Hi @paton400

This works great, but it also allows these user roles to read through other users private messages, change avatars, settings etc

If this applies to non-admin users such as contributors or subscribers, then this is a mighty big flaw. If that is happening due to the plugin then I’d expect the plugin author will want to know about it. Try raising the issue with them as a bug report or mentioning it in their support forum.

There is a plugin in the wordpress plugin directory to handle phpbb to bbpress migration,although no mention is made about private messages.

https://wordpress.org/plugins/cms2cms-phpbb-to-bbpress-forum-converter/

It looks like it is in active development so you might want to suggest the features you are looking for to the plugin author if it doesn’t already cover your needs.

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.