BuddyPress.org

Hi,

try this snippet (add it to bp-custom.php or child theme’s functions.php):

function garfrey_widget_title( $title ) {
if ( $title == "Members") {
$title = __('Members Translation') ; // foreign char. here
}
return $title;
}
add_filter ( 'widget_title' , 'garfrey_widget_title', 21 );

Reference:
https://codex.wordpress.org/Plugin_API/Filter_Reference/widget_title

Hello Brajesh Singh and Engine44

I am a newcomer to buddypress and I think I had similar problems as Engine44.
Frankly I could imagine that there are more people who have this
problem but eventually don’t even realize it as a problem.
In particular I can’t imagine that all that bp networks which
are used by schools want to have kids discuss in public. So it might
be a severe problem. But as said I am a newcomer so I might easily be
wrong.

The following concerns mostly the member and activity pages (I hope they are called
this way, this is a direct translation from german), which are either set
public -or if set private can’t be found anymore (which seems to kill more or less all major bp functions, like you can’t see profile etc.) I haven’t looked into groups yet.

I asked a person for help who is pretty proficient in solving general programming
problems but who is not a programmer and in particular not a PHP programmer. So eat with
utmost caution.

He came up with the following hack:
The activity and member pages need to be public in order to assign them
on the bp page. (I think this is the default upon installation)
Then set the pages to private.

go to buddypress/bp-core/bp-core-functions.php
and then in function bp_core_get_directory_pages() {…

change

$page_names = $wpdb->get_results( „SELECT ID, post_name, post_parent, post_title FROM {$posts_table_name} WHERE ID IN ({$page_ids_sql}) AND post_statues = ‘publish’ ” );

into

// temporary hack
if ( is_user_logged_in() ) {
$page_names = $wpdb->get_results( “SELECT ID, post_name, post_parent, post_title FROM {$posts_table_name} WHERE ID IN ({$page_ids_sql}) ” );
} else {
$page_names = $wpdb->get_results( “SELECT ID, post_name, post_parent, post_title FROM {$posts_table_name} WHERE ID IN ({$page_ids_sql}) AND post_statues = ‘publish’ ” );
}
// was:
// $page_names = $wpdb->get_results( “SELECT ID, post_name, post_parent, post_title FROM {$posts_table_name} WHERE ID IN ({$page_ids_sql}) AND post_statues = ‘publish’ ” );
// /temporary hack

Translated to 100% doesn’t mean updated to 100%. Have you verified any of your translation with the .pot file ?

Normally, an update (plugin, theme,..) is shipped with his most recent pot file. Open the .po file with poEdit and run an update from pot.

With poEdit you can also check the file and the line number containing the word you’re not able to translate. With this information, control the file content and verify that the string is correctly formatted for i18n. Sometimes, a localization is omitted, or in case of buttons, the error can be in a js file… You have to investigate attentively. I can’t help you more, sorry. 😉

Hi,

check your theme translation or menu settings and eventually your plugins (if you use some).

On your members page source code, there is a long phrase in english inside a div which is not from BuddyPress:
You can browse all activities here. Use menu below if you want to browse only specific activities like […]

The theme was published in 2013, it could be possible that it is not updated for latest BP version…

Try downloading the following:

• https://translate.wordpress.org/projects/wp-plugins/buddypress/stable/de/default/export-translations
• https://translate.wordpress.org/projects/wp-plugins/buddypress/stable/de/default/export-translations?format=mo

Rename the files to buddypress-de_DE.po and buddypress-de-DE.mo respectively.

Then, move the files to /wp-content/languages/plugins/.

Since the translation is not 100% complete, you might see some English strings.

Let me know if that works for you.

I think the German translation is not fully 100% translated, which is preventing WordPress from fetching the latest German translation for BuddyPress.

If you are able to help translate the remaining strings, please visit:
https://translate.wordpress.org/locale/de/default/wp-plugins/buddypress

Also, read the following guide to find out how to contribute towards the translation:

translate.wordpress.org (GlotPress)

Are you using BuddyPress Multilingual as well?

My guess is that BuddyPress has newer translation strings in v2.4.0 and you’ll need to update the BuddyPress-specific strings on your WPML install to reflect that.

Read their “Translating profile fields” tutorial:

BuddyPress Multilingual

They also have a support forum here:
https://wpml.org/forums/topic-tag/buddypress/

It might be that their plugin will need to be updated.

If it ends up that this is indeed a BuddyPress problem, please let us know.

Are you sure that the translation exist ? Have you a buddypress-xx_XX.mo file ? Where xx_XX is the iso of your language (eg en_US).

mo is a compiled format and the only file that php need to translate your strings.

To get such file, you need to use a language compilator like poEdit. Changing strings in only buddypress-xx_XX.po has no effect on the translation. This format is a simple text format intended to be used by the translator.

And the buddypress.pot (note the final T) is also a text format file which contains the list of all strings you can translate.

Where do you add your copy and which language do you use ?

No I don’t think so.

The alternative is to change the text by way of creating your own translation of it using Poedit.

See the following:

Customizing Labels, Messages, and URLs

The poedit program, used for editing and creating the translation files is available for free here:

https://poedit.net/download

Hi, perhaps you omited a dot or another php element. Anyway, below snippet add same fonction to members directory by using the appropriate filter, so you haven’t to touch the template.
Add it to child theme functions.php or bp-custom.php

Show user’s role on member directory

function who_are_you_dir() {

$user = new WP_User( bp_get_member_user_id() );

	if ( !empty( $user->roles ) && is_array( $user->roles ) ) {
		foreach ( $user->roles as $role ) {

	/**
	 * Fetch the user's role. See https://codex.wordpress.org/Roles_and_Capabilities
	 * _e('role name', 'text_domain' ) allows use of translation
	 * else use echo "role name"; 
	*/

		// Output
			if ( $role == 'administrator') {
			echo "Administrator";
			} 

			if ( $role == 'subscriber') {
			echo "Subscriber";
			} 

			if ( $role == 'contributor') {
			echo "Contributor";
			}

			if ( $role == 'author') {
			echo "Author";
			}

			if ( $role == 'editor') {
			echo "Editor";
			} 
		}
	}
}
add_filter ( 'bp_directory_members_item', 'who_are_you_dir' );

To show user’s role(s) on his profile, you can use this:

Show user’s role on profile

function blablabla() {

$user = new WP_User( bp_displayed_user_id() );

	if ( !empty( $user->roles ) && is_array( $user->roles ) ) {
		foreach ( $user->roles as $role )
			echo $role;
	}
}
add_action( 'bp_before_member_header_meta', 'blablabla' );

WPML seems to be the most sophisticated translation engine, however it adds a lot of complexity to the site and using it with Buddypress tends to mean you will have a slow site.

Hi @3t_mj,

this can be done CSS, using :after pseudo selector. All labels containing (required) have a for attribute which let you select them individually. You can also apply a rule by field type.
As the string (required) is in translation, remove it from there and use & nbsp;(without space after & ) in place of.

Here a working example, with both technique.

/* Register bp section */
#profile-details-section .field_type_textbox label:after {
  content: " *";
  color: red;
  position: relative;
}

/* Register WP section */
#basic-details-section label[for="signup_username"]:after {
  content: " *";
  color: red;
  position: relative;
}

Check the translation file: buddypress_CN.po (with a text editor like Notepad++) and verify that email text are all in plain text. Those strings shouldn’t contain any html entities.

Read from here for more details about email customization:
https://buddypress.org/support/topic/customizing-emails-template/
https://buddypress.org/support/topic/registration-process/

Before saying it’s not working, please follow the instruction.
Read my previous answer slowly and check the path i indicated.

wp-content/languages/plugins/buddypress-es_ES.mo

According to the screenshot, your site use the mexican version of WordPress.

Unfortunatly, there is no mexican spanish translation avaible for BuddyPress !

This force you to use spanish (es_ES and NOT es_MX) as site language to get automatically the es_ES BP translation.

In other words, you can’t use mexican language on main site if you want BP in spanish.

Translation can be found here: https://translate.wordpress.org/projects/buddypress/2.2.x

@alex42152,

The main site language should be set to spanish first.
See in WP dashboard > Stettings > General

Normally, this settings allows automatic translation file upload of BuddyPress and bbPress (if installed).
If not, you can add manually the language files in the wp-content/languages/plugins/ folder to get:

wp-content/languages/plugins/buddypress-es_ES.mo
wp-content/languages/plugins/buddypress-es_ES.po

Each version of BP comes also with its own translatable strings file, which is at the BP plugin root.
wp-content/plugins/buddypress/buddypress.pot

The default BuddyPress site setup only supports a single activity, members, groups directory page.

One solution is to create your own custom page templates, and embed the code for the activity, member and group loops in the template. You’d then assign it to your duplicate pages. You can read more about coding your own loops in the documentation section of this site.

You could also look to see if it’s possible to use the language files — dynamically loading the appropriate text domain translations of the BuddyPress text depending which language the user has selected. In this scenario, you’d work with the default ‘single’ page setup.

Perhaps too late for your site (if you’ve gone down the polylang route), but for all our multi language solutions, we go the multisite approach and using the Multilingual Press Pro plugin. It gives a really clean solution. Remember to enable bp multiblog if you switch to this approach.

Hi @thesmartone,

I even changed wp_config.php, variable WPLANG
This is no more necessary since WP 4.0

If your WP is in portugese, BP should be in same language automatically (except if you deactivated this feature)

BP translation can be found on GlotPress. pt_BR is translated to 96% (see here)
The po/mo files goes to wp-content/languages/plugins/buddypress-pt_BR.mo

Your comment is awaiting moderation, is a default WP string. In many cases, it can also be in theme. To ensure this, activate 2013 or 2015 and test all translations for WP and BP.
Deactivate all other plugins while doing this.

And before claiming about buggypress, check for PBCK. Or better, read the doc before installing something. 😉