BuddyPress.org

Right. That’s WordPress 4.4’s embed feature https://codex.wordpress.org/Version_4.4

I think we added support for that to our activity stream in our last relese.
If you don’t want the feature at aall, https://wordpress.org/plugins/disable-embeds/ might work.

Is it a relatively simple process?

Yes, BuddyPress is just a plugin so once you have WordPress set up you can install BuddyPress via a few clicks.

Importing members from a spreadsheet will most likely need a plugin. Try searching the Plugin Directory to see what is available.

You must have a plugin that affects how WordPress delivers email. Can you list what plugins you have active?

It isn’t really a copy-and-paste example. You’ll need to be comfortable with PHP and WordPress 🙁

Alternatively though, you could look for a plugin in the Plugin Directory. Maybe the functionality you need already exists?

To update this thread, I’ve just added a fix for emails not sending for certain server configurations. See https://buddypress.org/support/topic/read-this-first-buddypress-2-5-master-list/ and https://buddypress.trac.wordpress.org/ticket/6947

I think this will help many people, but I would surprised if it fixed everything for everyone. Fingers crossed!

I’ve just added a fix for emails not sending for certain server configurations. See https://buddypress.org/support/topic/read-this-first-buddypress-2-5-master-list/ and https://buddypress.trac.wordpress.org/ticket/6947

I think this will help many people, but I would surprised if it fixed everything for everyone. Fingers crossed!

Did you keep a backup copy of your database? If so then you’ll need to use that. Then there’s the files and folders. You should be able to get the 2.4.3 zip from:

https://downloads.wordpress.org/plugin/buddypress.2.4.3.zip

@invisibleland Can you start by looking in your web browser’s Javascript Console for any problems? See https://codex.wordpress.org/Using_Your_Browser_to_Diagnose_JavaScript_Errors — go to step 3.

@karolbielecki The German language pack has not been updated for BuddyPress 2.5, so that’s expected: https://translate.wordpress.org/projects/wp-plugins/buddypress/language-packs

Please start a new support discussion, I don’t think your issues have anything to do with this thread.

…but WordPress multisite and regular WordPress have different character restrictions in the username.

Nice 🙁

No, but WordPress multisite and regular WordPress have different character restrictions in the username.

Update: With reference to usernames on the wordpress.org forum:

Since [dotorg11555] only a-z and 0-9 are allowed for usernames.

Ref: https://meta.trac.wordpress.org/ticket/1308#comment:13

I’m not sure if this change will extend to the WordPress platform and BuddyPress.

sanitize_user() is used on the username at signup time so it should be alphanumeric characters plus _ space . – * and @.

Ref: https://codex.wordpress.org/Function_Reference/sanitize_user

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.