BuddyPress.org

@kokiri

It sounds like you’ve already taken some great troubleshooting steps. Since the “Join Group” button isn’t functioning, I would recommend the following:

Check for JavaScript errors: Right-click on the page, select “Inspect,” then go to the “Console” tab to see if any errors appear when you click the button. JavaScript conflicts often cause buttons to stop working.

Enable WordPress Debugging: You can enable the debug log by adding the following line to your wp-config.php file:

php

define(‘WP_DEBUG’, true);
define(‘WP_DEBUG_LOG’, true);

This will help catch errors that might not be visible in the front-end.

Check group creation method: If your groups were created using a plugin or demo import, try creating a new group manually to see if the issue persists. Sometimes imported data can cause conflicts.

If none of these resolve the issue, it could be helpful to explore potential theme conflicts with BuddyPress or review any customizations you may have made.

People can check the list of groups and list of members on the directory page. Usually, the page is “yourwebsite.com/members” for the member’s directory and “yourwebsite/com/groups” for the group directory.

You can see and edit the slug on BuddyPress Settings >> URL tab.

If the issue is the non logged-on user can not access it, I think it is because there’s a restriction system on your website. Maybe it’s part of a plugin/theme on your website or a code. You need to disable it so people can access your BuddyPress directory.

1. You can disable all plugins except BuddyPress change your WordPress to the default theme and see if the issue persists or not.

2. You can check if you add any custom code on the bp-custom.php or functions.php file inside the theme folder. If you have that custom code, you can remove it and see if it fixes the error or not.

Since version 12, BuddyPress has no longer used WordPress pages. That’s why you will not find a page ID on the BP pages.

A possible solution, you install the BP Classic plugin so the BuddyPress page can use the WP page.

You can use this CSS:

#buddypress #item-header-avatar a {
  pointer-events: none !important;
}

It sounds like you’ve done a lot of the right things already. Here are a few additional steps you might try:

Check for Conflicting Plugins: Ensure no other plugins are overriding BuddyPress translations.
Clear Caches: Clear any caches that might be affecting the translation display.
Verify Translation File: Double-check that the .po file has the correct translation for “Name” and is properly saved.
Theme Conflict: Make sure your theme isn’t overriding the BuddyPress translations.
If the issue persists, you might want to reach out to the BuddyPress support community for more specific advice.

You also can try “Reset all BuddyPress slugs to default ones” on the Tools >> BuddyPress. If it also won’t help, I think you need to contact the BP Better Message team for support.

Please try to check “Better Messages Location” on your BP Better Messages settings page. It should be set to “Show in BuddyPress profile” instead of another page.

@adjunkten you can find pot file inside BuddyPress plugin language folder and to sync you also also use poedit tool

You can change it from BuddyPress Url Setting https://tinyurl.com/24shwf9b

Hi,

You may try disable all non BuddyPress plugin and change your WP theme to default theme for temporary.

Check site to see if issue still exists. If issue goes away after deactivating other plugins and switching theme then this means that either the theme or one of the plugins was conflicting with BuddyPress. If it turns out to be a plugin/theme conflict, then you need to activate the plugins/theme one by one until you find the plugin/theme that causes the issue to come back.

If the issue still exists then it is not a plugin or theme conflict. And do these things

1. If you have a custom code in bp-custom.php, please remove it for temporary
2. Make sure to use the latest version of BuddyPress
3. Check your PHP version, and upgrade it to minimum 7.4 version.

PS: Backup your website first before do those steps!

Hello,

You can try to reinstall BuddyPress emails. It’s on Tools >> BuddyPress of your WordPress dashboard.

You also can try to install a Mail SMTP plugin and do testing to send a test email through the Mail SMTP plugin menu, to make sure if the issue comes from BuddyPress or the Sendgrid.

@keithkhl Could you take a look at this comment here and provide testing steps?

But Mathieu for your info, if I put the buddypress-fr_FR.mo file in /wp-content/languages/plugins/ as I did before, it does not work.

Here is what we get

While we should have

I haven’t tried to put the .mo file in /wp-content/languages/plugins/buddypress/

Thanks for your help and reactivity. It now works for me, as I said before, when I simply put the .mo file in /wp-content/languages/
We can close this thread

Hi @capexpe

I believe we’ve improved this part actually in 14.0, see https://buddypress.trac.wordpress.org/changeset/13936.

You shouldn’t put your custom language into /wp-content/languages/plugins because it will be replaced by the official translation after it has been updated by the Polyglots team.

Custom language files for BuddyPress should be in one of the locations we are looking for:
– /wp-content/languages/plugins/buddypress
– /wp-content/languages/buddypress
– /wp-content/languages

More informations are available from this documentation page: https://github.com/buddypress/buddypress/blob/master/docs/user/advanced/texts.md

I’ve just tested renaming “Groupes” with “Expé” in custom fr_FR translation files I’ve included in the /wp-content/languages/plugins/buddypress folder:
– /wp-content/languages/plugins/buddypress/buddypress-fr_FR.po
– /wp-content/languages/plugins/buddypress/buddypress-fr_FR.mo

And it’s behaving the way it should, see screenshot below:

@adjunkten I have no idea how Loco translate deals with translation files, but if you put their generated alternative language files at one of the three locations I listed above making sure they respect the WordPress default way of naming these, it should also fix your issue. Here’s the translated message for the “members-only” login page.

It seems that the /buddypress/v1/members/ endpoint returns only approved and active members displayed on your website. On the other hand, the /buddypress/v1/members/<user_id> endpoint may include all members, regardless of their status, such as pending applications or unapproved members. The extra members you’re seeing could be those who have applied but are not yet approved or are inactive. You may want to add query parameters or filters to refine the results.