BuddyPress.org

@danbp The email subject and email body content are both intended to be translatable via .po/.mo.

@xxsemmiexx The Dutch translation of BuddyPress has not been updated for v2.5. Look here: https://translate.wordpress.org/projects/wp-plugins/buddypress — “Dutch” + “Stable” = 90%.

For example – the email in your screenshots – you can see the text is untranslated at the bottom of this screen of the translation tool: https://translate.wordpress.org/projects/wp-plugins/buddypress/stable/nl/default?filters%5Bstatus%5D=untranslated&sort%5Bby%5D=priority&sort%5Bhow%5D=desc&page=10

Once a language’s translation is 100% complete for the “Stable” version, a Language Pack is automatically built, and your WordPress will then prompt you to download it on its normal “Updates” screen.

Once THIS happen, THEN you can run the repair tool, and you’ll have Dutch emails. 🙂

—

You can see the latest available translation packs for all languages here:

https://translate.wordpress.org/projects/wp-plugins/buddypress/language-packs

Hi @xxsemmiexx,

the new email feature comes in with a pre-built list of emails. These emails are defaults one for any possible situation in BuddyPress. It’s more or less the same as you have on your profile > settings > messages, where you have the email situation and a checkbox.

The translatable part of these emails, shipped with xx_XX.po/mo, is the mail subject.
When you click on the subject from within the email list, you’ll get the email editor.

At this stage and if the mo file is correctly made, you see the list in your language.

Now, let’s see the mail content. Click on Edit.

As title you have the subject (which is translated) and the body (which is not).
That’s intended so. It’s fake content in english and let you see how to use the tokens inside the email body – or subject.

This is also usefull if you want to add some custom email.

That said, after updating a translation, the modification doesn’t show up automagically in the list. To see it, you have to run the email repair tool.

Hope it is clear and helpfull for you.

I’ll try to test this type of email before the weekend. Can you paste me the translated text you’ve entered into the email title and email content for this type of email? Please put it on http://pastebin.com/ and then link to it here.

If all the other emails are working, it’s most likely that some custom text in the email is getting detected by your ISP’s email filters (etc) and blocking the email.

I will put your translation into my email of this type, and test it, and see if it works for me.

Yes, the French translation needs to be updated for BuddyPress 2.5. See https://translate.wordpress.org/projects/wp-plugins/buddypress/stable/fr/default?filters%5Bstatus%5D=untranslated&sort%5Bby%5D=priority&sort%5Bhow%5D=desc

@lanvalencia The Spanish translation still needs to be completed for BuddyPress 2.5. The new phrases for the emails have not been translated: https://translate.wordpress.org/projects/wp-plugins/buddypress/dev/es/default

Maybe you can help @_dorsvenabili get those done 😀

After the translation is updated, and after WordPress downloads the updated language pack (the .mo and .po files), go to wp-admin > Tools > BuddyPress and run the “Reinstall emails” tool.

Screenshot: https://i.imgur.com/kQj5CtT.png

This will reinstall the emails in Spanish for you.

Thank you for using BuddyPress!

unfortunately this forum is for support with BuddyPress itself, when there are added plugins it can make it impossible for someone to test.

Did you read through translation docs? https://codex.buddypress.org/getting-started/customizing/buddypress-in-your-language/

Hi,

you need to use bbpress.po translation file, even if your site is in default english language.
Or if you only want to modify one word, you can use this snippet from inside your child-theme’s functions.php (will also work in bp-custom.php)

function bruce_change_name( $translated, $original_text, $domain ) {
		
	if ( 'bbpress' !== $domain )  
	return $translated; 
	
	switch ( $original_text ) {
		
		case 'Forums':  // original word
		return 'Four Rhum'; // your custom word
		
		default:
		return $translated;
	}
}
add_filter( 'gettext', 'bruce_change_name', 10, 3 );

WP reference: https://developer.wordpress.org/reference/hooks/gettext/

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;
}