BuddyPress.org

@ivanguinea – If you recently added some new strings on translate.wordpress.org, you might need to force a translation update to see the changes.

By default, translation updates get updated when WordPress checks for new versions of plugins.

One way to force this is by installing the WP Crontrol plugin and by forcing the 'wp_update_plugins' cronjob to run. Untested, but please do try and let us know if it works.

But even if the file still loads, will it work if the line numbers are off?

It should, but for new strings introduced in BP 2.1, you’ll need to merge your translation file with the .pot file from BP 2.1 – /wp-content/plugins/buddypress/buddypress.pot.

View the “Updating your custom language file” for how it’s done with poEdit:

Customizing Labels, Messages, and URLs

We don’t have a tutorial for those using command-line tools though 🙂

ivanguinea – If you look at the Spanish translation on translate.wordpress.org, there are still some strings that haven’t been translated:
https://translate.wordpress.org/projects/buddypress/dev/es/default?filters[status]=untranslated

You can help by translating these strings. If you decide to help and are not sure how to add your contributions, let us know and we’ll point you in the right direction.

remove the greek translation of WP and BP and test in english

Glad you got it to work !

FYI: BP Poke comes with his own languages folder who contains po/mo in english. This is wrong, but has no influence if you want to use another language.

The reason is that many authors create a po file instead of a pot file, and when they save the file, poEdit (or similar) automatically creates a mo file.
The correct file name should be bp-poke.pot ! You can remove the original – in english – mo, totally useless: the plugin is coded in english !

To use a translation for this plugin, you add xx_XX.mo to bp-poke/languages/xx_XX.mo

Text domain ref: bp-poke.php:50

I just tested Duena and the BP translation is fine.

Recheck your po/mo files. Here what you must have:

duena – leave as is.
buddypress/bp-languages/buddypress.pot
wp-config – if you use english, as it’s default language you have nothing to do
// define(‘WP_LANG’, ” );
wp-content/languages/plugins/buddypress-en_US.mo

Now if you want to modify only some strings, make a copy of the pot file and put it in a folder outside of buddypress.

From this copy you remove anything you don’t want and keep only the 2 lines or 4 lines (if plural form) who belong to the string you want to change. You keep only the string you want to change.
Once done, save and rename it buddypress-en_US.po and open it with a text editor (not poEdit), as we’re going to modify the header.

msgid ""
msgstr ""
"PO-Revision-Date: 2014-09-12 00:05+0100\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Plural-Forms: nplurals=2; plural=n > 1;\n"
"X-Generator: Poedit 1.5.7\n"
"Project-Id-Version: BuddyPress 2.0.2\n"
"POT-Creation-Date: \n"
"Last-Translator: \n"
"Language-Team: \n"
"Language: en\n"
"X-Poedit-SourceCharset: UTF-8\n"
"X-Poedit-Basepath: .\n"
"X-Poedit-KeywordsList: __;_e;__ngettext:1,2;_n:1,2;__ngettext_noop:1,2;"
"_n_noop:1,2;_x:1,2c;_nx:4c,1,2;_nx_noop:4c,1,2;_ex:1,2c;esc_attr__;"
"esc_attr_e;esc_attr_x:1,2c;esc_html__;esc_html_e;esc_html_x:1,2c\n"
"X-Poedit-SearchPath-0: ..\n"

The rest of the file looks like this:

msgid "Friendships"
msgstr ""  <strong><- replacement goes here</strong>

#: bp-friends/bp-friends-template.php:588
msgid "%s friend"
msgid_plural "%s friends"
msgstr[0] ""
msgstr[1] ""

Save in text format utf8 without BOM. (important)

Now you can open this po file with poEdit, do your translation and save so that poEdit generate a mo file (see poEdit settings first to get this automatically each time you save a file).

Copy the mo file in the appropriate folder and, normally, you’re done.

References
https://codex.wordpress.org/Translating_WordPress
https://make.wordpress.org/polyglots/handbook/translating/basics/
http://www.wpbeginner.com/wp-tutorials/how-to-disable-automatic-updates-in-wordpress/

The definitive guide to disabling auto updates in WordPress 3.7

11. Do you have any custom functions in bp-custom.php? Yes, the function from every tutorial talking about the language, but changed for my custom language file.

Which tutorial are you telling about ?

Remove that function, it’s not necessary i guess.

By default, you set your site language in wp-config define ( ‘WP_LANG’, ‘de_DE’ ); and in wp settings > general (depending if single or MS install)

Where to put the translation ?
wp-content/languages/de_DE.mo (this is the WP translation)
wp-content/languages/plugins/buddypress-de_DE.mo (this is the BP translation)
wp-content/languages/themes/theme_name-de_DE.mo (this is the theme translation)

You say you used gedit to generate your translation. It’s a text-editor, not a mo compiler. (mo means machine only, you can’t read it !)

I suggest that you use poEdit to make a translation and generate a correct mo file.
On Ubuntu, you can (not sure) use the msgmt command from the gettext package. Something like this

$> msgfmt -o your_file.mo -v your_file.po

@giggio,

verify that your translation files are in the correct directory.

For bbPress:
wp-content/languages/bbpress/bbp-xx_XX.mo (required)
wp-content/languages/bbpress/bbp-xx_XX.po (option)
where xx is your language

For BuddyPress:
wp-content/languages/plugins/buddypress-xx_XX.mo (required)
wp-content/languages/plugins/buddypress-xx_XX.po (option)

FYI: both plugins are shipped with a pot file containing the strings you can translate.
/plugin_name/languages/plugin_name.pot

Don’t put a translation in this folder, as it will be overwritten at each update.

@annyrakesh,

please don’t jump into old post !

You want to modifify this phrase:

Registering for this site is easy. Just fill in the fields below, and we’ll get a new account set up for you in no time. who sit on the register page.

The string is in bp-templates/bp-legacy/buddypress/members/register.php line 22
and in the pot file of bp 2.0.2 at line 1236.

The pot file is a working copy for translators, not the file to modify to get any customization.
To do this you have to use poEdit, or a similar software.
poEdit only read the pot file, then he create a po file on the fly and when you save this po file, poEdit generate a mo file.

This is a compiled file, not human readable, who is used by the gettext php module to translate the strings he find in the buddypress code.

Pot files are provided by the plugin authors. It’s a simple text format file with a specific syntax.
The po file is also a text format file, but written differently, as it contains the original string in english AND the translation of this string in a foreign language.
And the mo file is the system file who have to use on the server.

register.php is a template file, so if you have to change only this phrase, you can make a copy and paste it into your child-theme and modify the wording directly in the file. Not orthodox, but it works.

If you have other question about translation or wordings, feel free to open your own topic, give your bp version, theme name and used language on the installation.

Topic closed.

@annyrakesh

you jumped into a topic marked as resolved 14 mounth ago ! Please open a new one and indicate your theme, the language you use and where you pick up the translation.

Topic is now closed.

It is not an issue, it is intended so !

The logged user’s profile tab comes with 3 sub menus:
– View (public)
– Edit (private)
– Change avatar (private)

On the main navigation of the member, you have at least
– Settings with 3 sub nav items:
– account credential (email, password)
– notifications
– field visibility settings

And if component is activated:
– Friends
– Groups
– Forum

I agree that this Setting is confusing, at least, because those labels should indicate My Friends, My Groups, My Forums and My profile fields visibility settings, which is too long i grant you. 😉

FYI: such distinction wern’t really possible untill now in the original english version.
But the upcomming BP 2.1 brings some better context disambiguation just to improve such situation.

To solve this today, you can:
1) create a translation file and modify the wording (but, as said, without disambiguation)
2) use a child theme and hardcode the text you want into the template file (best approach)
3) wait a few days for 2.1 to use the first option

Hi @presis_carsten,

could effectively be a translation issue. Why ?
For translation, we (i translate BP into french) mostly use HTML entities for special characters.
In brief, accented letters in HTML. For instance, if you want to type één you would type één.

The only part this should never be used is in the messages, as gettext doesn’t handle mail content.

And so far i see, the dutch phrase contains such an accented letter (beëindigen)

buddypress-nl_NL is here. And you’re free to modify it on Glotpress and of course in your copy, with poEdit or similar.

I checked WP & BP’s nl_NL version on Glotpress and didn’t find the phrase you mention. Could it be you use a very old translation or some notification plugin ?

buddypress/bp-languages/buddypress.pot
Don’t use DW to read, modify or save a translation. Use a text editor (not word) like notepad or notepad++

The NL translation is on Glotpress and the translation you need to put on your server is buddypress-nl_NL.mo

This is a compiled file used by gettext. You cannot read or modify it. If you want to do so, see poEdit.
https://translate.wordpress.org/projects/buddypress/dev/nl/default

Languages and Translations

You can find many other related topics if you search a little on the forum.

ok, supposing you did a translation file (even if you use english by default) to test the above solution and assuming it hasn’t work, let’s try the hard way.

Add this to functions.php, it will force gettext to translate the string.

function bpfr_force_translation( $translated, $original_text, $domain ) {
		
	if ( 'buddypress' !== $domain )  
	return $translated; 
	
	switch ( $original_text ) {
		
		case 'Registering for this site is easy, just fill in the fields below and we'll get a new account set up for you in no time.':
		return 'Join PushkarGuide.com - share your experience, thoughts about this pretty town Pushkar (INDIA).';
		
		default:
		return $translated;
	}
}
add_filter( 'gettext', 'bpfr_force_translation', 10, 3 );

If it doesn’t work i have no other solution to propose.

there are only two files […] which need to be modified.

False.

If you use the old BP-default theme, you only modify a copy of bp-themes/bp-default/registration/register.php placed in your child-theme

If you use any other theme, you modify only bp-legacy/buddypress/members/register.php
placed in the child /your-child-theme/buddypress/members/register.php

The one or the other, but not both. And don’t forget that you should never modify core files, as your work will be lost at the next BP update. That’s why child-theme exist and is so important for customization.

If this change doesn’t work (but it should), you have to try something different.

Create a language file containing only the mentionned string.
Read here.

Do you already use a language file ? §Is your site in english ? If not indicate the used language.
And gave your plugin list and theme name. It could be you have somewhere a conflict with ajax who block something on the registration page.

@micasuh _e( $text ) will search for the translation of $text and print it to screen. If a translation doesn’t exist, it’ll print $text. You might also come across __( $text ). This does the same but it returns instead of printing.

So yeah, these functions are definitely related to translating.

@micasuh the .mo file is most likely being loaded from your theme’s functions.php file. Alternatively, it may be loaded from a plugin. Or, maybe even bp-custom.php (if you have one of those).

Look for something such as the following and try removing it to see if it resolves the issue:

if ( file_exists( WP_LANG_DIR . '/buddypress-en_US.mo' ) ) {
    load_textdomain( 'buddypress', WP_LANG_DIR . '/buddypress-en_US.mo' );
}

If it doesn’t resolve the problem then we know your translation file is OK.

If you still believe the issue is a virus in your database then you could try rolling back. Do you keep database backups? But, to be honest, I’m more inclined to think this is occurring as a result of some rogue theme or plugin code.