BuddyPress.org

Deactivate loco translate and redo what i described previously.
Search also for evtl. issues mentionned on loco translate support.

Aside there is no reason to use that plugin if you don’t translated scecificcally BuddyPress to your nedd. sv_SE.po/mo are loaded automatically.
If despite this, you use your own translation version, see how to prevent your translation to be overidden. It’s explained in one of the sticky topics on the plugin support.

I’m unable to reproduce your issue. WP and BP language update is working properly.

BuddyPress har uppdaterats utan problem.

Guess it is this who genrate now an issue.
I have tried to update the po file with a new mo file but no difference

Po & mo are not the same file, and mo is compiled…

Remove all bp language files from /language/
Deactivate and reactivate BP – this will force BP to reach his translation.

Hello Buddypress,

today on 23.06.2016 , there was a new update of (version 2.6.0) and here are the translations of notifications, messeges and friends on the tab were in german forgotten. can you please make it?

That was a surprise for me, as yesterday BuddyPress ru_RU was 100% translated by me – both dev and stable.
I re-imported translations, so now everything is 100%.

Добрый день @valery-kondakoff,

no it’s not a regression ! Just a question of delay after BP’s update. Translations are made by volonteers, which are humans, not programmed machines. You have to wait that the translation is completed.

Or you can download the trunk version, which is already completed to 100%.
https://translate.wordpress.org/projects/wp-plugins/buddypress/dev/ru/default

At the page bottom you have a download button and a file type selector. Select po and mo format and rename both files to buddypress-ru_RU

BuddyPress share the DB with WordPress (the wp where it is activated).

An association between Polylang and Lingotek could be a good compromise.

If you really want 3 WP, it’s possible for them to use one DB.

Read also the documentation about installing BuddyPress on multisite.

> I just changed the template and the translations works fine.

Which template did you changed ? What do you want to fix if it works now ?
Have you tried with a Twenty theme ?

Unable to reproduce. It’s working for me. Here’s what i see on my test site.

What i did:
– set site language to español de argentina
– downloaded venezuela’s version of po/mo
– renammed both file to buddypress-es_AR (
– added the file to this directory wp-content/languages/plugins/buddypress-es_AR.mo

That worked without changing header information, as ID is still “stable”. Sorry, my fault.

Perhaps try to change the theme to see if something get different. Apparently there are some missing tabs aside “subir”. Compare pictures.

Do you use a child-theme where you changed a profile template ?

In PoEdit > Catalog > Property.

Or open the po with a text editor and check the header. Looks like this:
(that’s the header of the Glotpress version for fr_FR)

# Translation of Stable (latest release) in French (France)
# This file is distributed under the same license as the Stable (latest release) package.
msgid ""
msgstr ""
"PO-Revision-Date: 2016-05-24 17:53:59+0000\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: GlotPress/2.1.0-alpha\n"
"Project-Id-Version: Stable (latest release)\n"

Important things are:
"PO-Revision-Date: 2016-05-24 17:53:59+0000\n"
and
"Project-Id-Version: Stable (latest release)\n"

Id can be text or numeric (ie. stable or 2.5.2).

Site language is the reference. Go to Settings > General and choose your site language.

If you use es_AR, you should use buddypress-es_AR.mo
If you use es_ES, you should use buddypress-es_ES.mo
and so on…

At each update, language files are also updated. This means that if you use bp-es_VE and the site is declared as using es_AR, your bp file will be updated to es_AR and BP will use this one instead bp-es_VE.

It would be better you use same language for site and plugins. What you can do, is to rename es_VE to buddypress-es_AR.po/mo. You need also to modify accordingly the header information in the po file. To do that you need to use poEdit to compile it to mo and get the correct header in it.

Note also that BP translation should be installed in wp-content/languages/plugins/buddypress-xx_XX.mo

Languages and Translations

Hi @paulrooms

The Italian translation of BuddyPress is up to date: https://translate.wordpress.org/locale/it/default/wp-plugins/buddypress

For the menu items (at least what I think you mean), you’ll need to go into wp-admin > Pages > Edit, and just rename/translate the pages yourself.

try the language file.. check the buddypress codex for translation

@lekins101 great stuff 🙂

Hi @pattiearnold

If you need help with translations, please feel free to open a new topic with any questions you have.

The po file is the working copy, it’s not the translation. The only file you need is the compiled .mo format file.

1) i’m not aware of this behave and i doubt you can get this to work.
2) yes
3) yes
4) you understood wrong. I said the inverse.

To resume the situation:
WP stays in english and you want BP in a different language. This is not possible with the automatic translation system.

Maybe you have to use some multilanguage plugin ?
https://wordpress.org/plugins/search.php?q=translation

Common usage

To get automatically a buddypress translation for your site, you have nothing special to do, except setting up WordPress to a custom language.

Note that the language should exist on GlotPress and must be completed to 100%.
https://translate.wordpress.org/projects/wp-plugins/buddypress

In this case, which is default situation, the translation will be automatically uploaded to wp-content/languages/plugins/

For each new BP version (at least any major releases), you will receive the latest translation available. And the existing po/mo files are then overiden.

Custom usage

If you use a custom translation, you have to protect your work from automatic updates which continues to work. To do that, you need to create a buddypress folder in the default location:

wp-content/languages/plugins/buddypress

Once this location exist, it receives priority when a new translation is available. From this point, you continue to receive the translation in the new directory and you can store your custom version in the first directory wp-content/languages/plugins/.

This is how it works actually for BuddyPress. Will perhaps be modified in the future. But no idea when and how.