BuddyPress.org

The download link on glotpress is below the content, in the bottm left corner.
Select the mo format and click on “export” and do the same for po format.

I’ve heard that the buddypress traduction never fails

Caramba ! Never trust rumours !

I can´t believe that nodoby has the same problem

Search for “translation” on this forum and you’ll be stumped !

Which theme do you use ?
Can you test youre install with Twenty Fifteen theme and see if anything is translated ?
Are the terms not translated on front-end, or also in back-end ?

FYI, the spanish translation for BP is only completed to 96%, but activity is translated. To ensure you have the most recent copy, download the spanish .mo file from here and install it in wp-content/languages/plugins/buddypress-es_ES.mo

Something may be getting lost in translation, but if you mean you want the user who has just logged in to be redirected to his/her profile, then check out https://wordpress.org/plugins/bp-redirect-to-profile/

thanks @henrywright for the swift reply … i was struggling with where to place these files, not seeing updates and generally wondering what I had been doing wrong. Basically I had been replacing the messages of the .po files when generating the new .mo translations … instead one should simply add a preferred translation as the following article suggests (https://wpalchemists.com/2014/05/buddypress-translation-files/)

oh the woes of .po & .mo ‘s … hope this helps someone else though!

This core function has no filter. The easiest way is to use a language translation file.

https://codex.buddypress.org/developer/customizing/customizing-labels-messages-and-urls/

In pot file, the concerned string Members is commented by [ component directory title ].

Hallo @rene-streber,

First of, i would recommend that you revert to a basic WP install using 2014 or 2015 theme and the WP’s german language activated and all plugins deactivated.

If you have a local install, suggest you do your test on it instead of the prod site.

Once this is done, you activate BuddyPress. German language will automatically be uploaded to the right folder (wp-content/languages/plugins/buddypress-de_DE.mo)
The original translation is here. It is complete to 100%. (and also the official translation).
FYI deckerweb provides a translation for bp 1.9 & 1.9.1. So seems to me it is outdated now.

Check if anything is correctly übersetzt. Theoretish sollte es jetzt funktionnieren.

If ok, you activate the main theme. Recheck everything. If ok, reactivate your plugins one by one and check each step to isolate an issue, if ever.

If everything is correct again, you can handle the specifics for your homepage. But remind one thing: BuddyPress components use a page system which is only in for internal purpose. This means that you can’t apply a page model like for an usual WP page. And if you use a special template just for the homepage, you have to adjust it to work with BuddyPress.

Each activated BP component should have a page assigned. And this page must be unique and empty, whithout any template or model settings, just a title.

I see that you have some issue with page names in your menu. Button show community2 and the permalink contains community-4. Check this too, to get community only everywhere. And probably clear your trash as it may contain some duplicates from previous attempts.

Once this is cleaned, und mit klarer aussicht, simply resave your permalinks to reinitialize all links.

When your custom language file doesn’t contain a correct header version, it will be overwriten at each BP update.

To avoid this, you have 2 solutions.
– completely deactivate automatic translation upload, which will affect the whole site: theme and plugins.
– keep a safe copy and upload it to the site AFTER the update. Tehn if something is missing or no more translated, you can update your version from the pot file shipped with BP.

If you use a cache, you have to clear it before installing a custom version. You must be sure that your wersion is running, in any case.

Chinese isn’t working for BP but works for WP.
Russian is ok for WP & BP

Have you a chinese translation for BP ?

The avaible zn_CN po header needs to be completed if you want to make your own version based on it.

there is no result

that’s because you use a wrong file name.
The language file must be named “buddypress-zn_cn.mo”

If WP site language is set to chinese (general > settings if on a single install), buddypress will aotomagically upload the avaible chinese translation.

Search also this forum if you need more information, they’re many topics related to translation.

Hi @arturamirov

See the Languages and Translations article to start with. There’s also the Translator Handbook.

– keep in mind that I’m not doing a full on translation, just this BuddyPress translation to change Friends to Connections.

you put only those strings into your custom po. If the concerned string is on a template file, you can also hardcode it there, and use a template overload to get in from your child-theme in that case. So you haven’t to struggle with poEdit. In this case also, you have to take care of the details given by @shanebp.

– does the language define statement in wp-config.php need to be set for this to work?

This is no more used since WP 4.0. You can remove it.

– buddypress-en_US.po and buddpress-en_US.mo files need to be in which folder?

/wp-content/languages/plugins/ (the po file is not used by gettext, it’s only a human readable work file – you can store it elsewhere if you want. You just have to remind where in that case 😉 ).

if you put it in /language/ (of course you can), you will see buddypress-en_US as a language setting. Which is of course not the site language.

But in any case, keep a copy of your work in a safe place outside of WP.

@prometheus-fire,

this is obvious, but unfortunately despite your details, difficult to help out, because you don’t tell which code is concerned… or what you used to do your change. 😉

Generally, when it doesn’t translate, it’s because a typo error. A custom function, a theme using outdated strings and a lot of little details like missing dots, comas or percent sign.

Here some tricky examples which can produce a missing translation.
Original code looks like this:

%d friends

Activity feed for %s's friends.

Friends <span class=\"%s\">%s</span>

If %d is typed %s, or if the end point after friends is missing or you forgot to anti-slash or a double cote in the html, gettext mismatch the source and the translation and doesn’t execute it.

First thing to do in your situation, is to compare what is in your po file to what is in the BP code. Assuming BP code is the master, and always right. Po can be wrong: old version, manually modified, corrupted. Po must in any case be saved as text format in utf8 without BOM. This is invisible, but a real source of issues, specially when anything seems the same and desperatly stays untranslated/unmodified.

To do this, open the po in a text editor. Search for the string, check the file position given above the string, and read carefully and triple check, that the original BP code and the string in the po are strictly identic.

If nothing found, ensure there is no custom function somwhere, or a theme playing around the buddybar or subnav.

Are you sure you’ve translated this label: Friends <span class="%s">%s</span>

Did you include this Sources Keyword when creating the translation .mo in poEdit: _x()

The Friends label is generated by __() and _x(), depending on the context.

More info re keywords: http://www.cssigniter.com/ignite/wordpress-poedit-translation-secrets/

Just to add to Roger’s brilliant post above…

Don’t be afraid of Poedit.

It can look a bit intimidating at first but it really isn’t.

I’ve always edited language files directly in a text editor but I decided to give Poedit a whirl.

What caught me out was the fact that when I first opened it I was editing the actual strings and then exporting the PO & MO files.

This wasn’t doing anything because it was the wrong way to do it.

For every string there is a blank translation box beneath it, this is where you need to put your “translation”, then export, upload and boom, works a treat 😉

Changing these titles isn’t the easiest thing, but BuddyPress does provide 2 ways you can do it. However, hacking core files like bp-activity-loader.php is definitely not one of them. [Never hack core files — have a Google if it’s not obvious to you why you shouldn’t]

Ok the 2 solutions are:

1. Use a language / translation file
2. Use the template hierarchy

The string “Site-Wide Activity” is translatable — all the strings are. You can implement a language file that translates ‘Site-Wide Activity’ into whatever string you’d like. Have a search for translating BuddyPress strings / POT files / poedit. There’s also a documentation (they call it the Codex) page on it: https://codex.buddypress.org/getting-started/customizing/customizing-labels-messages-and-urls/

The second solution is to use the template hierarchy. If you don’t provide a specific template for your activity directory, BuddyPress will use the page.php file from your theme and ‘inject’ the title “Site-Wide Activity” where page.php makes a call to the_title().

You can override this by implementing your own template — create a file called index-directory.php inside /buddypress/activity in your site’s theme. Copy the basics of page.php into that file, and replace the_title() with your hardcoded title for the page.

You can read more about the template hierarchy here: https://codex.buddypress.org/themes/theme-compatibility-1-7/template-hierarchy/

Neither solution is simple, you’ll either have to get your head around using poedit, or need some basic PHP coding skills and an understanding of the principles of templates and themes in WordPress. In the future, it would be nice to see a settings panel in wp-admin to configure these basic strings.

[p.s. if you don’t want to use poedit, you could take a look at plugin solutions for string translation, e.g. codestyling localisation]

Hi.

I am also using wordpress 4.1.1 and buddypress 2.2.1 and for all pages, which I need to map via the settings page I am getting a blank page: Groups, Members, Register and Activate. I am using the default theme. It is a multi-site setup, however buddypress is only used on the main site (first blog) and also only there activated.
I did only minor styling via the themes css and the header.php.

WP_Debug does not show any errors as well as the Apache log is empty.

It was working fine until i updated recently the connected bbpress for forum.

Besides that I am using following plugins:
bbP private groups
bbPress
bbPress Advanced Capabilities
BP Registration Options (DEACTIVATED CURRENTLY)
BuddyPress
BuddyPress Group Email Subscription
BuddyPress Like (DEACTIVATED CURRENTLY)
BuddyPress Multilingual
HookPress (DEACTIVATED CURRENTLY)
Nginx Helper (only on staging)
Page Builder by SiteOrigin (DEACTIVATED CURRENTLY)
Paid Memberships Pro
Paid Memberships Pro – bbPress Add On
Paid Memberships Pro – Register Helper Add On
Social Login

Network activated:
WordPress SEO
WPML Multilingual CMS
WPML String Translation
Events Manager

My dev environment is XAMPP on Mac and on the staging is a linode cloud server with Ubuntu on Nginx (I think). Both have the same issues.
It’s not a live site yet, just demo, therefore some of the plugins might get activated if I am back on track.

Tried it now to get it run for about 15 hours:
– I also deactivated all plugins except buddypress and still did not get any of those sites working.
– Actiavated / Deactivated the plugins
– Used the repair tools
– looked into all my codes and fixed file endings such as empty space after ?> in php files
– Reassigned all sites
– Researched a lot in million of forums

Any hint, idea, glimps or full stack solution is highly appreciated.

Thanks, Chris

The po file you used initially contains errors or missing strings. This file is on glotpress and indicate it is 100% translated. Problem is, that Glotpres doesn’t control the syntax and 100% translated doesn’t mean working to 100%.

If you use this po file as work base, you have already 95% translated and probably some typo errors. poEdit handle this and shows you which strings are not “completed” or have “changed”. In this case, you have to validate the translation. Such difference are highlighted in a different color, so they’re easy to see.

It’s not automated, but a kind of.

Similar topics
https://buddypress.org/support/topic/problem-with-spanish-translation/
https://buddypress.org/support/topic/po-not-working-on-registration-page/