[@thomasbp Participant 14 years, 4 months ago]

I’d like to have a password field. Is this going to be implemented?

[@thomasbp Participant 14 years, 11 months ago]

Thx, I got it, but my users won’t, since they see a PM rather as an email and not as another kind of a discussion group (core age 15, so they have plenty of time to enter all the names ). It’s also in my opinion not intuitive.

If there is no simple way to include a “no bcc” option – is there a way to limit the number of recipients to one user?

[@thomasbp Participant 15 years, 1 month ago]

I’m late, but thx u2!

@DPaul: I’ve used that template while I was desparately looking for a solution. However, I probebly miss something obvious.

@buzz2050: Your workaround did it!

[@thomasbp Participant 15 years, 2 months ago]

Do you maybe have conflicting plugins within the mu-plugins direcctory? Because those are working in the background without being visible on the plugin page.

[@thomasbp Participant 15 years, 2 months ago]

It bases on the skeleton component for buddy press that is not compatible with 1.1. Andy said he’ll fixed it: https://buddypress.org/forums/topic/bp-11-rc-compatible-with-skeleton-component-122

[@thomasbp Participant 15 years, 2 months ago]

1) 2) is solved in BP 1.1. see https://buddypress.org/forums/topic/better-avatar-crop-function

3) Well I wanted to refer to the user settings, where the user-delf-delete checkbox was in 1.0.3. But in 1.1 Ican’t find it anymore even though the self deletion is activated in buddypress’ backend settings. What happended to it?

4) The simplest way would be CSS (the activity remains in the code, though)

[@thomasbp Participant 15 years, 2 months ago]

I’m running 1.1 RC and can affirm the other answers. The cropping in 1.0.3 was terrible but now it works like a charm.

[@thomasbp Participant 15 years, 2 months ago]

Thx Andy,

problem solved.

My mistake was:

I wanted to modify the the wire content and the activity content with two different functions. However, the activity entry is triggered by the wire save functions. Thus I had only to change the content before it’s processed by the wire functions and “forwarded” to the activity process. This is how I did it:

Solution:

add_action(‘bp_wire_post_content_before_save’, ‘sw_add_image_wire’,1);

function sw_add_image_wire($message){

$image = createImage();

if($image === false) return $message;

$image_link=”.date(‘Y’).’|’.date(‘m’).’|’.str_replace(‘.jpg’,”, basename($image)).”;

$message.= $image_link;

return $message;

}

[@thomasbp Participant 15 years, 3 months ago]

May I reopen?

The solution above worked for me until BP 1.1.

Now I don’t want to tamper around with the functions.php in the parent theme.

Thus I’ve tried to unhook the “bp_dtheme_show_home_blog” function in the bp-sn-parent/function.php by entering

remove_action( ‘wp’, ‘bp_dtheme_show_home_blog’, 2 );

into the functions.php of my child theme. Even though other functions in my child functions.php are working the removing of this action does not succeed. Any idea why?