Forum Replies Created
The change reported in https://buddypress.trac.wordpress.org/ticket/6972 has been added to BuddyPress trunk, and will be included in BP 2.6.
Do not edit core BuddyPress files. Next update, it’ll be replaced and you’ll have to do it all over again.
BuddyPress 2.5 made a lot of changes to how BuddyPress works with emails. We’ve been making incremental fixes and compatibility improvements in each release since, and we have v2.5.3 almost ready for sometime in the next couple of weeks or so.
People still having problems could try running https://en-au.wordpress.org/plugins/bp-email-to-wp-mail-from-bridge/ to see if it helps, but we have other fixes in place for v2.5.3 that aren’t provided by this plugin.
If you delete the page, I think you can probably just ignore that banner notification. It’s only telling you that the page isn’t set, but you already know that, because you’ve done it on purpose.
There isn’t a way to remove the nag message.
Thanks. This isn’t actually a bug in BuddyPress, but we flag it to reveal code in other plugins running at the wrong time because quite often this can cause very subtle problems in BuddyPress and other plugins.
We’ve very recently adjusted the messaging to make it clearer which plugin is causing us to trigger this notice: https://buddypress.trac.wordpress.org/changeset/10709/
wp_mail_fromsupport are coming back in BuddyPress 2.5.3. Thanks to everyone’s feedback regarding this.
There is one other tweak that’s coming up in BuddyPress 2.5.3 (not sure when it’ll be released, would guess a week or two) that might address it. After 2.5.3, BuddyPress should be identical with WordPress in terms of compatibility with the majority of plugins that help WordPress support SMTP.
For the record, if you’re running a plugin that defines
wp_mail()that helps you have WordPress’ emails be sent, then it just won’t work with BuddyPress.
Does adding https://wordpress.org/plugins/bp-email-to-wp-mail-from-bridge/ help?
^ that is pretty much why I removed the page. it was misleading to people looking for BP-compatible plugins.
The above is not a complete solution for Sendgrid, no.
webdevstudios have a couple of options — take a look on their site.
Not sure what you mean be “projects” feature — sounds like that’s part of this other plugin, so that’s not really in our wheelhouse. Or it’s something in BuddyPress that’s been renamed.
Have you checked the other plugin for options to disable it?
That’s for Mandrill. It relies on the fact that the wpMandrill plugin replaces wp_mail() so it gets the email data it needs, and just calls wp_mail().
Maybe you can use it as a base
If one type of email is getting sent and the others aren’t, it might be some part of the content triggering some kind of spam filter on the remote server. It could be some kind of throttling issue, and it’s only by coincidence one type of email is being sent. I don’t know. There’s all sorts of weird possibilities.
We have 2 further email delivery fixes that have been identified, which I imagine we will implement and release within the next 2 weeks. I don’t see how either would directly affect your site since you have SOME BP HTML emails being delivered, but not all — but maybe they will. This is certainly pretty weird.
Discussion with other person ended up with me not writing code. @slaffik I’ll try to get to this in the next day or two, but you need to implement your own
BP_PHPMAiler, and filter
bp_send_email_delivery_class, AND set bp_email_use_wp_mail to return false.
Filtering this to false is only going to try to send the email via PHPMailer. This doesn’t always work depending on server configuration, which is why SMTP plugins are quite common.
You need to create your own
BP_Email_Deliveryclass. Someone else is literally asking me this right now so I’ll throw together some example code quickly…
I’ll let those two continue to try to help, I just wanted to say I really want to investigate adding shortcodes for all BuddyPress things in some future release and have recently began to think about it. Doesn’t help you now, but might help someone in the future.
I’m going to assume that you haven’t changed post_content to match post_excerpt on purpose 😉
I think I know but can you dump the entire email object — in that bp_send_email_success filter — and share it with me? Either on github gist or email me or however.
@backpackersunion Some have asked about the “Hi” part. I suppose that could be changed. I have seen a few people ask, but if I see one post about something here, I normally multiple that number by 100, because very few people find it easy or convenient to get in contact with us (with support question), so probably quite a lot of people would like the option, even if it wasn’t the majority.
The unsubscribe I am a bit less sure of. I don’t want to make it easy for evil people running BP to remove the unsubscribe link for emails they send. In BuddyPress 2.6, an upcoming change means that this unsubscribe link will work, even if you’re not logged in to the site.
From a technical perspective, if we remove the token from the template and put it into the option, if a user has already customised the footer text option, they won’t see the new updated (default value for the) option.
This is not unsolvable, we’d run something on the upgrade routing, but we’d have to stick the token at the very bottom or top of the template. It’d be easy for the site admin to change, but it would annoy them. But it might be worthwhile.
So — maybe? You could create a ticket on buddypress.trac.wordpress.org to see if any other regular contributor likes the idea, or see if you can start a discussion or get feedback from other users via the forum.
@justarandomuser Please don’t post the same thing on multiple topics. If you find yourself wanting to do that, it’s best to just create a new discussion topic for better visibility. I’ve replied on your other topic.
@justarandomuser Yes. BuddyPress does not and will not support WordPress’
wp_mail_content_typefilter, so setting this or not does not affect BuddyPress.
Postman SMTP plugin re-declares a function called
wp_mail(). BuddyPress will send its emails in plaintext if
wp_mail()has been redeclared.
This decision was made because a lot of legacy WordPress plugins that change email content/appearance, or how they are delivered, re-declare
wp_mail()and it is impossible for BuddyPress to know if/how it could support all these custom implementations.
If you are using Postman SMTP to only send emails via SMTP, you could find an alternate SMTP plugin. People have mentioned some recently in email support discussions on this forum, though I can’t remember the names. If I find one again, I’ll try to remember to let you know here.
If you are using Postman SMTP for any other purpose, and you don’t want to switch to another plugin that only configures WordPress to send via SMTP, then I’m afraid you’re out of the options at the moment.
You are right that the Customizer does not indicate that the email will only be sent in plaintext in these situations. We’ll get some messaging added to that screen in the next BuddyPress release to clarify that.