BuddyPress.org

Thanks @r-a-y

This is a better solution. Any thoughts on how to solve the same problem with @mentions?

@mercime

Already select P2 on SuperAdmin > Themes, the problem is that on Appearance > Theme I select P2 but it not show as selected on same page instead BP-default show as selected, but if you hit the secon blog url it use P2.

Is there a way to sent you blog info privately, so you can check this issue ?

Regards,

For anyone else with this issue, here is the fix. Thanks to @sbrajesh

in bp-messages-templatetags.php, starting at line 498:

function bp_send_private_message_link() {
echo bp_get_send_private_message_link();
}
function bp_get_send_private_message_link() {
global $bp;

if ( bp_is_my_profile() || !is_user_logged_in() )
return false;

$user=new WP_User($bp->displayed_user->user_id);

return apply_filters( ‘bp_get_send_private_message_link’, $bp->loggedin_user->domain . $bp->messages->slug . ‘/compose/?r=’ .$bp->displayed_user->userdata->user_login );
}

Private messaging now works with persistent caching like memcached.

It looks like BP 1.3 is going to address some issues with object caching. https://trac.buddypress.org/ticket/2636

Can anyone who knows confirm if it will fix these messaging issues?

@r-a-y I think my issue is beyond a simple email issue. I installed the email plugin you mentioned just to humor the situation. When I try to send a private message I get redirected to the homepage of my site. So I could either be experiencing a 404 error or some other similar problem.

Also Im not even getting notifications at the recipient. I also do not have a message in the senders sent message box nor in the recipients inbox.

Thanks,

Just to update, I applied the code from the patch with no luck. Here’s what my messages-templatetags.php code now says:

function bp_send_private_message_link() {
echo bp_get_send_private_message_link();
}
function bp_get_send_private_message_link() {
global $bp;

if ( bp_is_my_profile() || !is_user_logged_in() )
return false;

return apply_filters( ‘bp_get_send_private_message_link’, $bp->loggedin_user->domain . $bp->messages->slug . ‘/compose/?r=’ . bp_core_get_username( $bp->displayed_user->user_id, $bp->displayed_user->userdata->user_nicename, $bp->displayed_user->userdata->user_login ) );
}

It looks like I now need to “apply a filter to “bp_get_send_private_message_link” and override it so it doesn’t use bp_core_get_username().” Anyone know how to do this?

Thanks guys.

@r-a-y

Thanks for the link, but I’m confused a bit. My current code already has that patch in it, changing the “public” to “private” looks to be the only switch. I’m guessing this was changed in a more recent BP release?

And, you said:

“With the patch, you’d still need to apply a filter to “bp_get_send_private_message_link” and override it so it doesn’t use bp_core_get_username().

The same problem occurs with the bp_get_send_public_message_link() function – aka the “Mention this user” link.”

It sounds like this is the step I need to take. How exactly do I apply this filter?

Thanks!

Batcache isn’t supposed to impact logged-in users, so it seemed like a natural fit for BP.

Paul, you think this is a BP issue as opposed to just tweaking a caching setting?

I know that there are people using BP with memcached and W3Total cache…are any of you guys having trouble with this? (W3TC doesn’t worth with multi-db’s or I’d be using it)