BuddyPress.org

There isn’t a filter for that text but you can use the buddypress textdomain to add a translation.

Customizing Labels, Messages, and URLs

Fr translation has no issue, nor german one.
The issue may be in your language selector or multilingual plugin…

May I ask, would this be a multi-lingual site?

I think what you want done with the profiles is doable, you could configure the profile to display the families profile information and then ave a section for comments below that data. It would take a bit of coding but is achieveable.

The multi-lingual aspect worries me as some translation plugins can be really complex and tend to slow down the site too much, but it depends how far you are looking to go with that translation.

How are you going to handle these payments? Will they be managed through the site or completely separate from it?

@r-a-y The danish locale for moment.js use “da” extension. As you ask for check, i assume it is confusing when BP translation is using “da_DK” ? 🙂

https://github.com/moment/moment/blob/develop/locale/da.js

BP 2.7 introduced dynamic timestamps using livestamp.js and moment.js.

For dynamic timestamp localization to work correctly, we try to load the moment.js localization file.

It is quite possible that moment.js does not come with a Danish translation.

@adjunkten – Can you check to see if there is a Danish translation here?
https://github.com/moment/moment/tree/develop/locale

If so, can you output your WordPress locale using get_locale()? There might be a bug in how we are checking for the moment.js locale file.

Your time stamps looks correct, I’m guessing you mean the Danish translation isn’t working correctly?

You can grab the newest Danish Buddypress translation here https://translate.wordpress.org/locale/da/default/wp-plugins/buddypress followed by merging your current buddypress-da_DK.po file in poedit like this http://www.marketpressthemes.com/blog/how-to-merge-two-po-files-using-poedit/, translate the words you needs to translate, save it as both buddypress-da_DK.po and buddypress-da_DK.mo – and reupload it to your server in your language folder.

I guess that means that when a user registers on one of the multi-sites he can use his account on all the other websites of the Multi-site installation, right ?

Yes, but understand that you have to give that user access to those other sites (in wp-admin) to write blog posts, for example. If a user does not have explicit permissions to a specific multisite site, they won’t have any special access; they’ll only be able to read the content as if they were another normal visitor. You can test this right now, without BuddyPress, and see how it works.

meaning it takes him out of the French Website to put him onto the English on

You seem to be using multisite to have your content localised into different languages. This is a common approach for WordPress multisite, but BuddyPress does not work the way you want it to in this situation.

You can activate BuddyPress in a few different ways. Simply, on multisite, you can activate the plugin on a specific site, or network-wide. There is lots more detail at https://codex.buddypress.org/getting-started/installation-in-wordpress-multisite/ but if BuddyPress is activated network-wide, all the BuddyPress content will only appear on one site (we call this the “root blog”). We use redirects to support this, exactly as you’ve found.

You can’t have BuddyPress active on a multisite that uses the sub-sites as different languages, and have the BuddyPress social network appear on all of them and work in the same way, except with different translations. It doesn’t work that way out the box…

…however here is an advanced setting you can use to make BuddyPress behave like this: BP_ENABLE_MULTIBLOG

See https://codex.buddypress.org/getting-started/customizing/bp_enable_multiblog/
I would encourage you fully test this setting out if you enable it, before you start building the rest of your site, just to understand and confirm its behaviour.

🙂

Check your theme files. You need to find the “ago” part and modify it (via child theme) to what BP use for it.

Or maybe you can get a german version for your theme or search the string in the existing theme translation.

Eventually ask for help on the theme support, as it is not a BP issue.

Hi,

check the code you used for “16 minutes ago”. You will find it in the buddypress-de_DE.po file. Normally, you should have %s ago -> vor %s. If you omit % or s, the string won’t be translated.

If it’s not a typo error of yours:
– where is this untranslated “ago” string showing ? Site activity, profile, widget, other ?

– do you use a specific “buddypress” theme ?

– does the issue remain when using the “official” translation file ? If not, download it here (po & mo). Don’t forget to remove your version before adding the original one into wp-content/languages/plugins/

hi,

it’s because you didn’t right.
The translation, or word change, use a msg ID which contains the original string and a msg string, for the new wording.

In your case, you should use

msgid "Site Wide Activity RSS Feed" // the original string
msgstr "Rich Site Summary" // the custom string

Note also to get this to work, you need to compile the po file to mo file.
And if you don’t want to redo that after each BP update, i recommand you use this plugin, so your custom language file remain untouched, while the default language will be updated.

– I know nothing about Loco translate as i never used it. And i can’t read chinese, so i can’t help you with this specific translation.

– I never seen a error 500 after modifying a translation.

– The only thing i’m sure (because of the error messages) is that it is Loco who doesn’t find a file or can’t access to it properly.

– Re-check Loco Settings and try another path option… Or maybe use a custom path called MyTranslation and use the plugin only to translate. Once done, deactivate Loco and move the mo file manually to the right folder. By doing this you eliminate the eventual plugin issue and still have a mo file you can use (hopefully).

– Ensure your BP’s po/mo files have correct file extension and use the correct path to file:

/wp-content/languages/plugins/buddypress-zh_CN.mo & buddypress-zh_CN.po

Personnaly, i use poEdit and only on my computer and never directly on a site.

Hi,

you are on the BuddyPress support.
bbpress questions should be asked on bbpress support.
And as you use Loco Translate plugin, and apparently have an issue with it, you have to ask on the LT plugin support.

To get more about chinese translation, help and much more, please read the Polyglots blog.

Hi,

all you have to do is to use a custom translation for BuddyPress !
This can be done with help of this plugin.

Actually, WP uploads automatically all available translation for itself and any of his dependencies: themes and plugins(when exist) accordingly to the site language. Ie. brazilian portugue (pt_BR.mo)

In your case, while using the plugin, WP will remain in portuguese and as you will use buddypress-en_US.mo or buddypress_en_GB.mo as custom translation, anything related to BP will be in english.

Of course, this behave will always be used even AFTER an update of WP or BP and both updated to portuguese.

The avantage of the plugin is that you haven’t to struggle with complicated domain settings and hacks, because he does it for you by using a different path for any custom translation (in your case, BP’s english version). The file is stored in /uploads/wpt-custom-mo-file/buddypress-what_EVER.mo

You simply need to remember to download manually the english BP version.
Translation files can be downloaded here.

Hope to be clear. 😉

hi Henry @henrywright,

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

this path is the one used by GlotPress’s official automated translation updates for BP (and any other plugin translation if it exist). Same behave for the languages/themes/ directory.

If you add a customized po/mo there, it will be overwritten at next update !

Since i18n new improvements in WP 4.6, the only way to keep the integrity of a custom translation actually, so far i know, is to use this plugin: wpt-custom-mo-file, who allows you to override and use your own translation files for any WordPress themes or plugins.

Just to let you know. 🙂

i checked the hebrew translation available on GlotPress. It seems to me it is correctly translated.

Copy/pasting RTL strings doesn’t work here… anyway here what i get (href is LTR here – but is ok in poEdit)
החשבון שלך הופעל בהצלחה! אתה עכשיו יכול <a href="%s">להתחבר</a> עם שם המשתמש והסיסמא שהכנסת כשנרשמת לאתר.

Hi!

1. presuming you dl the translation file (po & mo) ?
2. what have you renamed ? Normally there is nothing to rename for po/mo file names.
3. which code did you added to functions.php? Usually there is nothing to add there for translation.

See here for details: https://codex.buddypress.org/translations/

Note: Hebrew language file (buddypress_he_IL.mo) is uncomplete (72%), that’s probably why your register page is still in english.
There is also no PTE for hebrew which makes difficult for users to get the awaiting for validation strings.

The only solution for you is to download what is currently available in hebrew and to complete this translation yourself or to get in touch with this guy.

Perhaps you want to contribute to translation in your language? Read here if interested.