BuddyPress.org

Hey Paul Gibbs, I did what you asked and the results in the mail i got from the site admin was :

Email delivered – true

Also i do get mails when users change stuff from there wordpress profile, for example in the backand i changed a users email and he got a mail of email change.

My users do not get any mails from registering or activitys on the site they signed up for

Just adding to master topic tracking this.
I’m seeing similar problems using Mandrill to send email.

Here’s the plugin I’m using: https://wordpress.org/plugins/wpmandrill/
I’ve got version 1.33 installed.
Wordpress 4.4.2, Buddypress 2.5, Single Instance wordpress running on nginx

I don’t know how easy this might be to change at the moment – I think someone would have to write a small plugin – but we are tracking this feature request at https://buddypress.trac.wordpress.org/ticket/5500 for inclusion in a future BuddyPress release.

@fidelleon Thanks for testing!

Support for “WP-Mail-SMTP” and “Easy WP SMTP” will be fixed in BuddyPress 2.5.1.
See https://buddypress.trac.wordpress.org/ticket/6945 for tech details.

Support for “WP-Mail-SMTP” and “Easy WP SMTP” will be fixed in BuddyPress 2.5.1.
See https://buddypress.trac.wordpress.org/ticket/6945 for tech details.

Note that filters like wp_mail_from will continue to not be supported. See previous posts for how to implement the change in new versions of BuddyPRess.

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. 😉

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.

Cool!

@jgob https://github.com/WordPress/WordPress/blob/ef7a559e2e7804844f99034e4ec018c5ffbf66c9/wp-includes/pluggable.php#L1700

There’s no way to filter or halt the action; I suppose it MIGHT be possible to intercept it inside wp_mail() but it’d be awkward.

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.

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.

@danbp The email subject and email body content are both intended to be translatable via .po/.mo.

@xxsemmiexx The Dutch translation of BuddyPress has not been updated for v2.5. Look here: https://translate.wordpress.org/projects/wp-plugins/buddypress — “Dutch” + “Stable” = 90%.

For example – the email in your screenshots – you can see the text is untranslated at the bottom of this screen of the translation tool: https://translate.wordpress.org/projects/wp-plugins/buddypress/stable/nl/default?filters%5Bstatus%5D=untranslated&sort%5Bby%5D=priority&sort%5Bhow%5D=desc&page=10

Once a language’s translation is 100% complete for the “Stable” version, a Language Pack is automatically built, and your WordPress will then prompt you to download it on its normal “Updates” screen.

Once THIS happen, THEN you can run the repair tool, and you’ll have Dutch emails. 🙂

—

You can see the latest available translation packs for all languages here:

https://translate.wordpress.org/projects/wp-plugins/buddypress/language-packs

Hi,
it seems you don’t use BuddyPress.
Ask better on https://wordpress.org/support/ or at least, analize your site on an expert site like https://gtmetrix.com

Hi,

it’s enabled by default. More about Emoji on WP Codex: https://codex.wordpress.org/Emoji

IMHO, this need also to be reflected in terms of gamification. Because…

If you never write about humour and funny things, you don’t develop for mobile devices or don’t use a forum or don’t allow comments (or rarely) and not maintain a site for kids, you could probably disable this feature. Search for Disable Emojis on WP plugins repository.

The dark side of Emoji’s is that it use an external ressource which is(can be) bandwith consumpting. So if you haven’t an absolute necessity for them, prefer the good old built-in WP smiley.

I’m no Buddypress or WordPress pro but for a temporary fix add this to your styles.css

ul.first.acfb-holder li{
list-style:none;
}

Please use the code button when sharing code or error-log entries.

Thanks for your report.

Re #3: See https://buddypress.trac.wordpress.org/ticket/6937

Re #2: Use the new BP filters.
See: https://buddypress.org/support/topic/bp-2-4-x-to-2-5-wp_mail_from-not-working-with-new-emails-in-bp/#post-250532

Re #1: You can open an enhancement ticket here..
Use the same user / pw you use on these forums.
The new BP Mail API is generating a lot of tickets – per usual for a new API.

Also a couple of new features in GlotPress now on https://translate.w.org:
• BuddyPress Language packs: https://translate.wordpress.org/projects/wp-plugins/buddypress/language-packs
• BuddyPress Translator contributors: https://translate.wordpress.org/projects/wp-plugins/buddypress/contributors