What happens is that if I have a Gender field. The word Gender is translated (this is the Caption of the gender select field) but the options “Male” and “Female” do not get translated. They do get translated when visiting a profile on the frontend but not when registering. Is there a way to achieve this?
Thank you for contacting WPML support. While you are waiting for one of my colleagues to take this ticket and work on it, let me provide you with the first debugging steps and try to help with the issue quickly.
Can you use the workaround from errata just add your gender field as type also, so adjust the code so it contains the next:
Languages: English (English )Spanish (Español )German (Deutsch )
Timezone: America/Lima (GMT-05:00)
Hello,
If you search on WPML > String Translation for "Male" and "Female" did you translate all the available results? The strings on the backend are likely not the same string that are used on the login form.
You might also try to search for additional strings at WPML > String Translation > Translate texts in admin screens (link on the bottom of the page).
If this does not solve the issue, then this might occur because the user is not registered, and there is no information saved in the browser about the user's language.
WPML has an option to set a language cookie for such cases. You can find this option at WPML > Languages > Language filtering for AJAX operations.
If you search on WPML > String Translation for "Male" and "Female" did you translate all the available results? The strings on the backend are likely not the same string that are used on the login form. === YES
You might also try to search for additional strings at WPML > String Translation > Translate texts in admin screens (link on the bottom of the page). === The strings don't show up
You could also try to use the following method to locate the string, by enabling the option and reloading the login page. This should register all strings found on this page: === This option is not working because the strings show up on the register an account page and that page isn't reachable when logged in.
If this does not solve the issue, then this might occur because the user is not registered, and there is no information saved in the browser about the user's language. === Does it need a cookie because === This is already enabled.
Languages: English (English )Spanish (Español )German (Deutsch )
Timezone: America/Lima (GMT-05:00)
I can not confirm such an issue on my test site: hidden link
Did you register the profile fields at Users > BuddyPress > SignUp? You also might see a banner on this page demanding that BuddyPress MUltilingual needs to register the fields.
The names of the strings are:
profile field 2 - option 'female' name
profile field 2 - option 'male' name
I'm so sorry, I wrote BuddyPress in the Topic but when I described my problem I wrote BuddyBoss. I use BuddyBoss. I've added the options here: BuddyBoss -> Profiles-> And on the Details (Signup) tab I've added a gender field.
So maybe it differs? I've translated the string in the stringtranslation but it doesn't work...
Languages: English (English )Spanish (Español )German (Deutsch )
Timezone: America/Lima (GMT-05:00)
On my test, this does not make a difference. BuddyBoss seems to be using the same strings.
hidden link
One-Click-Login: hidden link
I would like to offer to have a closer look at the problem and request temporary access (wp-admin and FTP) to the website to investigate this issue further.
You can find the required fields below the comment section when you log in to leave the next reply. The information you provide is private, which means only you and I can see and access it.
IMPORTANT
Please be sure to make a backup copy of the website and database before allowing us access.
If you can't see the wp-admin / FTP fields, your post and website credentials are set as PUBLIC. DO NOT publish the data unless you see the required wp-admin / FTP fields.
The private response form looks like this: hidden link
Next time you reply, click "I still need assistance."
Video: hidden link
Please note that we are obliged to request this information individually on each ticket. We may not access any access information not specifically submitted on this ticket in the private response form.
Languages: English (English )Spanish (Español )German (Deutsch )
Timezone: America/Lima (GMT-05:00)
I see in your case the strings are coming from BuddyBoss > Profiles.
Those strings are not showing up by default on String Translation. You can test this by adding different names to the fields. They will not be found on String Translation.
The issue seems to be related to the "Gender" fields. I can not confirm an issue with the "Dropdown" field.
I can now confirm that even on my test site the translation does now not work as expected if I use the "Gender" field:
hidden link
This seems to be an issue between BuddyBoss and WPML and I will need to take a closer look into the code of BuddyPress to figure out what is causing this issue.
If I do not find a quick solution for the issue, I will be escalating the issue tomorrow to our compatibility team.
This will make the option values translatable with String Translation. The only side effect that I was not yet able to solve, is that it will register a new string antime you edit the option, instead of overwriting the already registered string, which means you need to manuallt clean up old strings on WPML > String Translation.
I will be escalating this issue today internally so that our Developers can take care about implementing this properly into an upcoming version of BuddyPress Multilingual.
Languages: English (English )Spanish (Español )German (Deutsch )
Timezone: America/Lima (GMT-05:00)
This issue has been escalated for review to our Second Tier Support Team and from there should be escalated very soon to the BuddyPress Multilingual development team.
As soon I got news on this matter I will contact you again.
