Skip Navigation

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

Problem:
The client has translated a formidable form using WPML, but some translations are not displaying correctly. Specifically, certain fields remain in the original language despite being translated.
Solution:
We recommend checking the WPML -> Strings Translation section to ensure all necessary strings are translated. For fields not showing as translated, such as '147_field-2941-description', it's crucial to verify their translation status in WPML and update them if they are incomplete. Additionally, if encountering issues with specific strings like '[2850]', which refers to another field ID, it may help to remove and re-add the entry or adjust the string directly in the formidable form settings or WPML string editor. If duplicate strings are found in the string editor, deleting the outdated versions can resolve display issues.

Please note that this solution might be outdated or not applicable to your specific 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 the problem persists, please open a new support ticket at WPML support forum for further assistance.

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 2 voices.

Last updated by christopherW-28 9 months, 3 weeks ago.

Assisted by: Itamar.

Author Posts
June 25, 2024 at 1:28 pm

christopherW-28

Background of the issue:
I have translated a formidable form using WPML. I tried the knowledge base and also the documentation on the formidable forms site.

Symptoms:
Most of the translations show but a few remain in the original language.

Questions:
Why are some translations of the formidable form not showing?
How can I ensure all parts of the formidable form are translated?

June 25, 2024 at 2:15 pm
June 25, 2024 at 7:06 pm #15824622

Itamar
WPML Supporter since 02/2016

Languages: English (English ) Hebrew (עברית )

Timezone: Asia/Jerusalem (GMT+03:00)

Hi,

You told me to check, as an example, the string 147_field-2941-description. I can see that it is not translated in WPML -> Strings Translation. Please see the attached screenshot 147_field-2941-description.jpg. In Strings Translation, for form 147_field, I can also see that not all the strings are translated. Please see the attached screenshot untranslated-strings.jpg. I can also see in the form settings that not all the strings are translated. Please see the attached screenshot not-translated-in-settings.jpg.

Can you please complete all those translations and see if it solved at least some of the strings?

As for the string, "I am a citizen of [2850]", I cannot make it to show in Russian.

I suspect that the problem is [2850].
Can you please explain to me what [2850] is?

Thanks,
Itamar.

147_field-2941-description.jpg
untranslated-strings.jpg
not-translated-in-settings.jpg
June 26, 2024 at 9:05 am #15831668

christopherW-28

Hi Istmar

Thanks for your reply.

In my version of the website, 47_field-2941-description was translated but was not showing in the front end, see attached image (ending 733).

However, today I added some missing translations (using WPML string editor) and edited field 2941 by adding a space and removing it and it is now showing correctly, I assume somehow something has been updated.

With regards to 147_field-2925 in which you see [2850], this is still not working.

[2850] refers to the field ID of another field on the form (the country they will be applying for their visa in).

If you see the attached images, you can see these strings are translated, and then see the front-end image that only this one field is not showing as translated.

Would it be worth deleting this entry somehow and adding it again, or maybe it doesn't work for choice options in the form but works OK in names and descriptions?

Many thanks

Chris

Screenshot 2024-06-26 100257.png
Screenshot 2024-06-26 095830.png
Screenshot 2024-06-26 094733.png
June 26, 2024 at 9:47 am #15832188

christopherW-28

Update.

I edited the choice in formidable to remove [2850], and it didn't work. So I checked in the string editor and there were two versions of the same string showing!!

I deleted the "old" version and everything seems to work for now.

Thanks for your help.