BuddyPress - Profile fields are not translated on the frontend

This is the technical support forum for WPML - the multilingual WordPress plugin.

Everyone can read, but only WPML clients can post here. WPML team is replying on the forum 6 days per week, 22 hours per day.

Sun	Mon	Tue	Wed	Thu	Fri	Sat
-	9:00 – 13:00	9:00 – 13:00	9:00 – 13:00	9:00 – 13:00	9:00 – 13:00	-
-	14:00 – 18:00	14:00 – 18:00	14:00 – 18:00	14:00 – 18:00	14:00 – 18:00	-

Supporter timezone: Europe/Kyiv (GMT+02:00)

Tagged: Known issue

This topic contains 2 replies, has 0 voices.

Last updated by Andrey 1 day, 16 hours ago.

Assisted by: Andrey.

Author	Posts
January 31, 2025 at 1:52 pm #16655910
marcM-23	<b>Background of the issue: </b> I am trying to translate BuddyPress profile fields on the frontend of my site hidden link. I am using BuddyBoss for member profile settings and WPML for translations. <b>Symptoms: </b> Profile fields such as First Name, Last Name, Nickname, Social Networks, and address fields are not translated on the frontend. I tried this: https://wpml.org/errata/buddypress-profile-fields-are-not-being-translated-on-the-frontend/ But no impact. <b>Questions: </b> Why are BuddyPress profile fields not translating on the frontend? How can I translate BuddyPress profile fields using WPML?
January 31, 2025 at 11:21 pm #16657443
Andrey Supporter Languages: English (English ) Russian (Русский ) Timezone: Europe/Kyiv (GMT+02:00)	Thank you for contacting WPML support. You may be experiencing a known issue. Please check the following workaround using the link below: https://wpml.org/errata/buddypress-profile-fields-are-not-being-translated-on-the-frontend/
January 31, 2025 at 11:23 pm #16657444
marcM-23	Did you read my request?
January 31, 2025 at 11:45 pm #16657459
Andrey Supporter Languages: English (English ) Russian (Русский ) Timezone: Europe/Kyiv (GMT+02:00)	Thank you for your feedback. I initially thought you were referring to the documentation. Have you clicked the "Register Fields" button in the notice that appears on the Profile Fields page? You can find an explanation in the link below. Did you translate them in the WPML → String Translation page? https://wpml.org/documentation/related-projects/buddypress-multilingual/#translating-profile-fields
January 31, 2025 at 11:56 pm #16657478
marcM-23	I don't have a "Profile Fields" item under "User" in my admin menu. All the fields are defined by BuddyBoss. And yes, I translated every possible version of it in String Translation.
February 1, 2025 at 9:38 am #16658054
Andrey Supporter Languages: English (English ) Russian (Русский ) Timezone: Europe/Kyiv (GMT+02:00)	I need to request temporary access (wp-admin and FTP) to your site – preferably to a test site where the problem has been replicated if possible – in order to be of better help. You will find the needed fields for this below the comment area when you log in to leave your next reply. The information you will enter is private, meaning only you and I can see and access it. Please provide an example of the page where the profile fields are displayed on the frontend.
February 3, 2025 at 10:47 pm #16664651
Andrey Supporter Languages: English (English ) Russian (Русский ) Timezone: Europe/Kyiv (GMT+02:00)	Thank you for the information. I visited your website and noticed that you are using outdated versions of the BuddyBoss and Elementor plugins. To determine if the outdated plugins are not causing the issue, please update them (including the current theme). Once the updates are complete, let me know if the issue persists so we can continue troubleshooting.
February 6, 2025 at 9:34 am #16674374
marcM-23	Hi, look I get it but my plugins are on a very recent version, just not THE latest. We are in the process of releasing the site and can't update just now. Are you really not look into this because it's not "the most" recent? Thanks, Marc
February 6, 2025 at 8:24 pm #16677215
Andrey Supporter Languages: English (English ) Russian (Русский ) Timezone: Europe/Kyiv (GMT+02:00)	Thank you for your feedback, Marc. I have reviewed your website already, and everything appears to be correct and properly translated. I recommend deleting the translations for those fields and then retranslating them to see if this resolves the issue. If the problem persists, could you please try to replicate it on a fresh installation with the latest versions of all components? While this step may not necessarily solve the issue, working with the most up-to-date code will help us troubleshoot more effectively. I have created a staging site, and I will share the link in a private following reply. Could you please try to replicate the issue there?