Home›Support›English Support›[Resolved] Conditional Gravitiy forms translation not working after upgrade
[Resolved] Conditional Gravitiy forms translation not working after upgrade
This thread is resolved. Here is a description of the problem and solution.
Problem:
The translated conditional forms are not working correctly.
Solution:
This issue occurs when translate the "value" of the radio button at the wpml -> string translation .
Steps to resolve:
- Go to WPML -> String Translation.
- Search for the Radio button name.
- There will be two values, one for the radio button itself and the other one for the radio button value.
- Mark the value as not translated, and test your form again.
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.
Sorry but this is working fine like this with the oldies version of WPML for more than one year and now not working anymore with the last version...
We will try to solve this status on this dev version of the website but sure it will not change !
And we see that if we add this form again to the translation pipeline, all the actual translations are lost ...
Best regards
OB
For testing purpose, I have created a new test form called it "Test Condition Form", and I managed it to work correctly on your site through these steps:
- Create the form
- Go to WPML -> Translation Management and send it to translator (only tested with french ) as described here : https://wpml.org/documentation/related-projects/gravity-forms-multilingual/
- Go to WPML -> Translation and Translate the new form.
- Go to WPML -> String translation and search for the form strings by the form ID.
- Mark the Values as not translated. (see attached Screenshot)
You can view the test form using these links :
en : hidden link
fr: hidden link
So I think the best way now, if to remove the old Conditional form and create a new one following the previous steps and it will work correctly.
Please note that this is a temporary solution as this issues was escalated to the developer, to discuss it and find a final solution, but because I couldn't give you an ETA for that, please try the temporary one.
Please let me know if that helps you.
Best Regards.