Skip Navigation

This thread is resolved. Here is a description of the problem and solution.

Problem:
You are using WPML's String Translation to translate a field in the Theme options found in Customizer. While other fields translate correctly and show on the front-end, one specific field does not appear after translation.
Solution:
First, ensure that your theme supports the translation of this specific field. If the issue persists, follow these steps:
1. When adding a string from the admin text, select to export XML configuration.
2. Add the exported XML to WPML > Settings > Custom XML Configuration.
This method helps WPML to manually detect and register the strings for translation, ensuring they display correctly on the front-end.

If this solution does not resolve your issue, or if it seems outdated or irrelevant to your case, we highly recommend checking related known issues at https://wpml.org/known-issues/, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If further assistance is needed, please open a new support ticket at WPML support forum.

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.

Tagged: 

This topic contains 3 replies, has 1 voice.

Last updated by Gregory 2 months, 3 weeks ago.

Assisted by: Prosenjit Barman.

Author Posts
December 2, 2024 at 12:24 pm #16465875

Gregory

Background of the issue:
I'm trying to use WPML's String translation to translate a field found in the Theme options, in Customizer. Other field translations show in the front-end correctly, but in one particular case this doesn't seem to be working. The process we follow involves going to the 'Admin Texts Translation' page, locating the field, then going to the 'String translation' page and translating it.

Symptoms:
The 'Admin Texts Translation' field is not showing in the front-end.

Questions:
Why is the translated field not appearing on the front-end?
Is there a specific step missing in the translation process for this field?

December 2, 2024 at 2:55 pm #16466922

Dražen
Supporter

Languages: English (English )

Timezone: Europe/Zagreb (GMT+01:00)

Hello,

Thanks for contacting us.

While you wait for my colleague to take over the ticket, let me try to help you with the issue quickly.

It can depend on the theme and if it supports such translation, but can you try one more thing: when adding a string from admin text, select to export XML configuration and then add it to WPML > Settings > Custom XML configuration and check if this helps?

Regards,
Drazen

December 2, 2024 at 3:42 pm #16467350

Gregory

Dear Drazen,

Thank you very much for your reply and for your assistance.
We have followed the steps you mentioned and it worked! May I ask why in this particular case the default method isn't wokring?

Best Regards
Sociality

December 3, 2024 at 7:28 am #16469618

Prosenjit Barman
Supporter

Languages: English (English )

Timezone: Asia/Dhaka (GMT+06:00)

Hi There!
I hope you're doing well!

Thank you for the update! I'm glad to hear that Drazen's advice helped resolve the issue.

The default method might not be working in this particular case due to how the theme or plugin handles the specific field. Some themes or plugins register strings dynamically or in a non-standard way that WPML cannot detect automatically through the "Admin Texts Translation" interface. The XML configuration allows you to manually instruct WPML to look for and register these strings for translation and display the translation correctly in the frontend.

I hope you now have a clear understanding of what to do if a translation doesn't appear on the front-end despite being registered for translation. If you have any further questions or need additional clarification, feel free to reach out. I'm here to help!

Best regards,
Prosenjit

December 3, 2024 at 9:43 am #16470642

Gregory

Hi Prosenjit!

Thank you very much for taking the time to explain the process so we can understand a bit better why this happened. We feel a more confident now as to how to deal with this in the future 🙂 .

Best regards,
Sociality