[Resolved] Split: user meta fields

Hello,

Thanks.

You also need to add custom code to make that field translatable. In this case, the field is `about_company`.

- https://wpml.org/documentation/getting-started-guide/string-translation/translating-user-meta-information-with-wpml/

I added the code via the Theme Editor and did not receive any warnings during the process. However, after saving the changes, I was no longer able to access the WordPress admin area. This suggests there may be another custom code snippet already on the site that is conflicting with the code I added.

Could you please provide FTP access details so I can investigate further?

Alternatively, you can try removing the code snippet I added to functions.php. Once access is restored, add only the custom code required for the `about_company` user field, and it should work correctly.

Regards,
Dražen

Hello,

Great, thank you!

I have now gone to WPML → String Translation and configured the Vendor Plus role to be translatable. If you check now, you should see that the `about_company` field can be translated.

The original value was in English, so I switched it to Spanish, added the translation, and translated it to English.

The only remaining step is to add the code snippet mentioned in our documentation:

To enable WPML to return the translated value when user meta is retrieved via get_user_meta() or get_userdata() — including by plugins and page builders — add the following filter:

add_filter( 'wpml_translate_get_user_meta', '__return_true' );

Once this code is added, the translated values should be displayed correctly on the front end.

Let me know how it goes.

Best regards,
Dražen

Hello,

I checked, and that is the translation you added, as shown in the attached screenshot.

If you add the remaining translations, everything should work correctly. I only added the Spanish (ES) translation for testing purposes, and it is working fine on my end.

Best regards,
Dražen

Hello,

It does support automatic translation.

Although this field is not translated through the Translation Editor, it is registered as a string and can be translated automatically through WPML's String Translation workflow.

Once the string is registered, you can go to WPML → Translation Dashboard → Other texts (strings), select the strings you wish to translate, and send them for automatic translation just like any other translatable content.

Please see the attached screenshot for an example of where these strings can be found in the Translation Dashboard.

For more details, please refer to our documentation:
https://wpml.org/documentation/getting-started-guide/string-translation/

If you have a large number of users, this approach should still scale well, as the strings can be translated in bulk through the Translation Dashboard rather than manually one by one.

Please let me know if anything is unclear.

Regards,
Dražen

Hello,

Yes, that is correct.

At the moment, String Translation content is not included in the "Translate Everything" workflow. While strings can be translated automatically using WPML's automatic translation engine, they still need to be sent for translation from the Translation Dashboard.

I understand this may not be ideal for your workflow, especially if new user-generated content is being created regularly. Unfortunately, there is currently no way to have String Translation items automatically translated without first sending them through the Translation Dashboard.

Regards,
Dražen