BuddyPress.org

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.

This sort of functionality is something that’s definitely required for BP – there’s no way an admin can go round reading everything on a busy site, abuse monitoring has to be crowdsourced to the members.

The plugin I’ve been testing, which was last updated in 2013, is this one: https://wordpress.org/plugins/bp-moderation/

Interestingly it covers just about everything – from members, private messages & their senders, statuses, activity comments, topics, forums, groups, posts, pages, blog comments, and probably a whole bunch of other things. I have a hunch they are hard-coded though.

It works to an extent, but glitches I’ve found so far include:

* Setting to define what text appears on the ‘Flag’ links don’t get applied to all links
* Flag link text for things like posts (and possibly pages) starts appearing in excerpts
* It’s using images rather than FontAwesome / Fontello via CSS = ugly and slow
* The admin menu icon is broken somewhat (looks ugly) but that’s minor thing

IMHO if the UI could be cleaned up, images replaced with icon fonts, and somewhat improved control over link text implemented, this plugin would be pretty much there and would cover just about all aspects of WP, BP and (with some extra coding) probably even bbPress.

Unfortunately I’m pants when it comes to PHP so can’t help with this task 🙁

This sounds like something that can be achieved without multisite.You can use Buddypress Groups and bbPress running as a forum for each group to achieve the discussion / chat.

Each project could become a BuddyPress Private Group with its own forum / docs.

If you want a seperate blog for each project then that would require multisite,but one blog categorised by project could achieve the same thing without the additional comlexity.

https://wordpress.org/plugins/private-bp-pages/
https://wordpress.org/plugins/private-community-for-bp-lite/

above 2 work for me absoutely fine. great plugins by @bp-help

There’s no actually need any plugins, you can easily do this by adding these lines to your themes function.php file:

`<?php

add_action( ‘wp’, ‘custom_private_area’, 3 );
function custom_private_area(){
global $wp;
if (!is_user_logged_in()){
if ( bp_is_activation_page()
|| bp_is_register_page()
|| is_page_template( ‘wp-login.php’ )
|| ( in_array( $GLOBALS[‘pagenow’], array( ‘wp-login.php’ )))
)
return;
bp_core_redirect(get_option(‘siteurl’) . “/wp-login.php”);
exit;
}
}

?>

The best approach is to list all of the places a member can enter text then try to lock each one down.

Off the top of my head I can think of:

The WP admin area – creating posts and pages etc

Comments (if you have comments enabled)

The BP profile area (xProfile fields)

The activity stream (commenting, replies, new updates etc)

Private messaging?

Private BuddyPress by Dennis Morhardt works an absolute treat for me.

I am having the same issue. I am getting 404 error for requests to a private group. Very frustrating.

Confirming this bug, which lead to some drama on our forum. You think private topics are private, but turned out that if you click on the last reply links from a private forum, you sometimes can get in even when you don’t belong to the group. Not funny.
Also, subforums don’t inherit the settings from their parent forum.

1GB RAM is a minimum, 2GB RAM is ideal. As you scale up you may need more. On a good server setup you can actually see live (via SSH) how much of your RAM is being used up and how much is free. If you’re bottlenecking, you can contact the hosting company to add more RAM or bump you up to the next server. That is not the same as migrating to a new host… if it’s within the same company they should handle it for you seamlessly in the background.

Another option is to use Amazon (AWS) instead of a private server and it just scales up automatically as needed – they mostly charge by data rather than by server. They will be more expensive for most sites and will be slightly harder to set up, but they are also incredibly scalable.

A CDN isn’t really a “cache” in the way you imagine W3 working. It’s only caching resources (stylesheets, images, javascript files, etc) but not caching “content”. Your resources usually don’t go stale because they are not updated often. And if you do it properly, the cache can be broken any time you update a resource (by adding a version number to the enqueue in your theme). The version number gets appended to the URL of the resource, so if it changes the CDN thinks it’s a different file and immediately serves up a new file.

Content does go stale. By content I mean the data that is outputting for everyone to see right on the website. Like a profile, activity page, member directory, etc. This is the stuff that plugins like W3 are primarily used to cache (among other things as well).

You can integrate a CDN very easily using WP Super Cache. You can just turn off the content caching stuff and use it only for pushing your resources into a CDN. It’s a set it and forget it kind of setup for the most part.

If you happen to be in the Miami area on May 9, I’ll be speaking about scaling BuddyPress at the BuddyCamp (1st day of WordCamp Miami). http://2014.miami.wordcamp.org/
Should be a fun event.

@batmanfan You can make a forum private, public or hidden.
Check out the doc: https://codex.bbpress.org/getting-started-with-bbpress/

You have no idea what you can learn by reading it. =)