BuddyPress.org

This will be fixed in BuddyPress 2.5.1.

This will be fixed in BuddyPress 2.5.1.

@rogercoathup Hi. Assuming those plugins re-implenment wp_mail(), as I expect most do, yes. Things will continue to work. They’ll get plain text versions of the BuddyPress emails, just the same as in previous BuddyPress releases (though some emails’ sentences have been tweaked/rephrased).

@lanvalencia I and others will try to get to help you as soon as possible.

None of us gets paid for contributing to BuddyPress. It’s the weekend. I have about 6 other forum discussions open where I’m trying to figure out why emails aren’t being sent at *all*, and that’s my current (personal) priority.

Please use the code button when sharing code.

The fields field_id and field_value do not exist in the function you are attempting to filter.
See this for accepted fields:
https://buddypress.trac.wordpress.org/browser/tags/2.2.1/src/bp-members/bp-members-template.php#L453

I think you want this field retval['include'].

Something like:

function see_woman_gender( $retval ) {
	global $wpdb;

	$field_id = 3;
	$field_value = 'Woman';
	
	$query = "SELECT user_id FROM " . $wpdb->prefix . "bp_xprofile_data WHERE field_id = " . $field_id . ' AND field_value = ' . $field_value;

	$woman_ids = $wpdb->get_col( $query );
  
	if ( !empty( $woman_ids ) ) 
		$retval['include'] = $woman_ids;

	return $retval;
}
add_filter( 'bp_after_has_members_parse_args', 'see_woman_gender' );

There are field re meta data; I don’t think they work with profile data.
But you could try this and let us know if it works:

function see_woman_gender( $retval ) {
     $retval['meta_key'] = '3';
     $retval['meta_value'] = 'Woman';
 
    return $retval;
}
add_filter( 'bp_after_has_members_parse_args', 'see_woman_gender' );

Hi @nkeatign

It ought to be totally do-able, but you’ll need to write it. If BuddyPress detects that something has re-implemented WordPress’ wp_mail function (like the Sendgrid plugin does), then it’ll use the plain text version of the email and pass that to wp_mail to let the custom wp_mail implementation deliver the email.

I am not aware of anyone who’s written a Sendgrid implementation for BuddyPress 2.5 yet, because the 2.5 release is still pretty new! Maybe you could write an integration plugin and be the first!

Here’s what you need to do (we can document this process more formally if this works for you): — off the top of my head, not tested, be wary of unexpected dragons, etc —

1) Add add_filter( 'bp_email_use_wp_mail', '__return_false' );
2) Add add_filter( 'bp_send_email_delivery_class', function( $delivery_class ) { return 'Your_Class'; } );.

These steps tell BuddyPress to always use its own email APIs, and tell it to use the class named Your_Class to handle the email delivery. The default delivery class is BP_PHPMailer which uses PHPMailer. I strongly suggest you use it as a reference for implementing a Sendgrid implementation.

Your_Class needs to implement the interface BP_Email_Delivery which provides a method bp_email(), which receives a BP_Email object. Everything about the email is contained inside the BP_Email object.

What your bp_email() method will need to do is call the Sendgrid’s plugin email-sending function. You can get all the information you need (recipients, HTML body, plain text body, etc) from the BP_Email object.

Hello,

I agree having more betatesters would be fine but sometimes it’s difficult when you just manage only one Buddypress site.

I’m having the same problem, the activation mail is not being sent since I updated. I have activated full debug mode (E_ALL and Display_errors) but nothing shows in the error log.

Besides, I had overriden the normal activation mail in my child’s theme’ functions.php. After it stopped working I did a grep and saw the function I was trying to use was in the v2.5 deprecated list, so I commented out all the overriding code.

I’m using the Easy WP SMTP plugin, the sender mails are good ones both in the plugin and the main WordPress configuration, and it can receive mails.

Yep, now it’s clearer. But sorry, I don’t know about a way to get some groups on main site and some others only on a secondary site.

Group should be intended as members group. And a group is not a site. It is just a bunch of members attached to a group.

Also, a group is not a blog and that’s why you get on a multisite install several blogs who share the same members, belonging eventually to differents groups. What and wherever the install is on main or seconday blog.

Members are all in the same DB table and WP doesn’t share them by groups, but by username > blog authors…

As you already know, BuddyPress comes with a member directory and a group directory. And on a multisite(aka network), a blog directory. But basically, all 3 cases are related to members, not to blog. There is no relation between a blog and a group. You can eventually install a blog into a group (buddypress group blog plugin), but you can’t install a group into a specific blog (outside the one where BP is activated). A group is not a blog.

On codex it is specified: buddypress root blog (the one you get from WordPress) or buddypress root blog on secondary site.

In other words, It should go to the secondary site. is not possible.

But i can be completely wrong. 😉

The css tag ID #aw-whats-new-submit may exist, but if your theme use some specific height or width for it which is different from what is used by BP in the js/css file, you didn’t see the button.

This is a very common theme issue, handled on many topics on this forum.

@tonyxs1 logically in the template. The what’s new form is used on activity, profile and group page.

You’ll certainly find some good information from these one or other search results:
https://buddypress.org/support/search/what%5C’s+new+form/

Hi @tammy1999

I have a 2 site multisite sounds a bit ambiguous.

Do you mean 2 multisite installs or 1 multisite install with 2 sites ?

If your config is the second option, BuddyPress should be at the root of the main site, at the same level as WordPress. Case A. of a standart network install, as explained here:

Installation in WordPress Multisite

Read attentively each step of your special configuration to see if you didn’t omited something in your settings.

People who are having problems: as far as I know, we have never seen this problem before during testing. If someone like you had helped us test BuddyPress 2.5 in beta or release candidate stage about four weeks ago, we’d have fixed it prior to release.

We’ll get it fixed as soon as we figure out what the problem is.

I was just thinking about it and have one question which would be interesting: in wp-admin Settings > General, the value for the Email Address — is it a REAL email address? For example, if you were to send an email to that address, would it receive it?

Im running into the same problem, But its not just the Activation mails, its any kind of mail related to buddypress thats not working anymore. My members get no updates and cant activate. Please Bring us a fix/solution Asap

Thanks for your feedback, @backpackersunion. I’ll let others chime in as I spent a long time working on the email feature, so it’s close to my heart, but here’s my thoughts:

• Decisions, not options.
• It’s much easier to add options than it is to remove options.
• It’s risky to add options or features unless you’re sure what your users want, so launching with a minimal feature set and listening to feedback and consensus helps us make informed decisions.

And the template, yes — you run the risk of the template going out-of-sync with the version distributed by BuddyPress. But this isn’t specific to the email feature, and could apply to any of BuddyPress thirty or so other templates.

We have some plans to add some communication around template changes in a feature release, like WooCommerce apparently does, which will help a bit.

@airsid

IF your translation file is up to date (have you re-downloaded the files to check?), those strings should be getting translated.

Otherwise, another option is to edit the email template. Copy buddypress/bp-templates/bp-legacy/buddypress/assets/emails/single-bp-email.php into your theme and make whatever changes you want.

If the filter bp_email_use_wp_mail returns true, it’ll grab the “plain text” version of the email from BuddyPress, and send that to wp_mail(). BuddyPress does not re-implement wp_mail().

BuddyPress will also fall back to use wp_mail() if it detects that any other plugin has re-implemented that function (pretty common in email plugins), or if something’s configured WordPress to send HTML emails.

BuddyPress does not stop or block any other plugins’ emails from being sent, nor any emails sent by WordPress core (with a few exceptions for multisite-specific emails, but this has been implemented for about 6 or 7 years, so it’s not a new change).

I am just now testing this with WP Better Emails. Give me a minute.

Hello,

@djpaul: link is not good anymore 🙁

@danbp: thank you. I’ve buddypress in french isntalled already. Such a great plugin 😉
But what i can’t find is how to translate the “Hi” of the “Hi {{recipient.name}},” in emails header.
And the idem for the “unsubscribe” in bottom of emails.

What you want is the ability for members to create posts in the front end.
And have filterable activity items created for those posts.

Both items are very doable – via other plugins or custom code.

To see the current offerings, Google: buddypress front end post