Skip to:
Content

BuddyPress.org

Opened 2 months ago

Last modified 2 months ago

#8332 assigned defect (bug)

Token {{recipient.name}} is not processed by BuddyPress

Reported by: connorwexc Owned by: imath
Milestone: Awaiting Review Priority: normal
Severity: normal Version: 6.1.0
Component: Emails Keywords: reporter-feedback
Cc:

Description

In the "Verify Acount" event, the token recipient.name is not processed. The salutation of the email is then "Hi, {{recipient.name}}". In GMail (and possibly other mail applications), this is automatically linked to a website that contains adult content.

WP Version: 5.4.2
BP Version: 6.1.0

I'm attaching a screenshot of the email as well.

Attachments (3)

recipient-name-token-not-generating.png (49.8 KB) - added by connorwexc 2 months ago.
recipient-name-buddypress-site-health.png (52.3 KB) - added by connorwexc 2 months ago.
bp-custom.php (9.8 KB) - added by imath 2 months ago.
Content of the bp-custom.php file

Download all attachments as: .zip

Change History (9)

This ticket was mentioned in Slack in #buddypress by imath. View the logs.


2 months ago

#2 @imath
2 months ago

  • Component changed from Core to Emails
  • Owner set to imath
  • Status changed from new to assigned

Hi thanks for your feedback. I will look into it asap.

#3 @imath
2 months ago

  • Keywords reporter-feedback added

Hi again!

@connorwexc I wasn't able to replicate although I've tested a lot of different scenario. Could you share more information about your configuration?

How BuddyPress is activated?

  • Network activated on a multisite WordPress config
  • blog activated on a multisite WordPress config
  • activated on a regular site

What is the name of the theme you are using?
Do you have other activated plugins? If so could you list their names?
Have you added custom code into the bp-custom.php file?
Could you share the content of the BuddyPress panel of the Site Health information screen?

#4 @connorwexc
2 months ago

Hey there, thanks for getting back so fast!

It is on a regular site config. The theme is WPLMS, https://wplms.io/, which is a big bundled theme by Vibe Themes for Learning Management. I'll attach a screenshot of the BuddyPress Site Health info.

It comes with:

Then there are some custom plugins that the theme creators have made that I can reach out to them about. They involve integrating plugins other than BuddyPress; CoAuthors, H5p, MyCred. It seems like my client has added a lot of plugins without reaching out to us. I'll see if I can get any info from them about why/when they added those plugins. My suspicion is that this list can be whittled down.

The theme creators added extra code to the bp-custom.php file, though none of it seems related to the functions. I'll paste it in anyways:

see attached bp-custom.php

For now that is all the info I have. Once the client get's back to me with the info on those other plugins, I will post that as well.

Last edited 2 months ago by imath (previous) (diff)

@imath
2 months ago

Content of the bp-custom.php file

#5 @imath
2 months ago

Thanks for your feedback @connorwexc,

FYI, I've copy-pasted the bp-custom.php content into an attached file.

I believe the issue is not in BuddyPress as all tests I've made are using a regular WordPress site just like yours. Unfortunately the theme is a premium one and we cannot afford to test such themes.

All tests I've made led to a good token replacement for {{recipient.name}}. Here's what I'd suggest:

  1. open a support topic on https://wplms.io/support/ to get their opinion about this issue.
  2. clone the Website on a staging/testing environment,
  3. Deactivate the theme and use a TwentyYear theme to see if the issue is due to the theme.
  4. If not, deactivate all plugins except BuddyPress to confirm the issue is not a BuddyPress one.
  5. Reactivate plugins one by one, making sure to test user registration to find the problematic plugin between each reactivation.

In the meantime for the production site, here's a quick workaround to fix the issue, BuddyPress is using an email template located into:

/wp-content
  /plugins
    /buddypress
      /bp-templates
        /bp-nouveau
          /buddypress
             /assets
                /emails
                  /single-bp-email.php

You can copy the single-bp-email.php file and put it into your active theme making sure it's located into

/wp-content
  /themes
    /YOUR-ACTIVE-THEME
       /buddypress
          /assets
             /emails
               /single-bp-email.php

Once there replace <?php bp_email_the_salutation( $settings ); ?> with any string like Hi,. This will remove completely the {{recipient.name}} token for all email types.

Please keep me informed about your debugging of this issue. I'd like to understand what's going wrong to try to prevent this from happening even if it's due to a plugin or a theme overriding our code.

#6 @connorwexc
2 months ago

I had a sneaking suspicion that that would be the case, but I appreciate the work you've done! I'll reach out to their support and see what I can find out.

Thanks for the help!

Note: See TracTickets for help on using tickets.