Thanks for your reply well noted. I encounter an another issue. I translate my gravity forms and also use gravity wiz ( an official and one of the biggest gravity form addons on the market).
I use a "live populate" feature to populate some fields in my gravity form.
Yesterday support went into my website to see why i was encountering an issue as the setup worked on their end.
They mentionned that there is a conflict created with WPML strings translation and it doesnt let the field populate correctly.
They will investigate further.
My questions is the following :
1) I saw in the strings the full list that "can" be translated and there some part of the gravity form of hidden field like the following "@{:32:selected[0]}"
When i translate a form can it cause some issues with this ? As now gravity wiz told me to desactive WPML strings. Once desactivated the form works as intented and auto populate all the right information.
When WPML string is activated it doesnt work.
So my question is the following. What might WPML strings do when i auto translate a form ? especially when there are some hidden fields like i have shown you ""@{:32:selected[0]}" like these with different strings.
What do you recommend if i have a lot of strings and need to translate a form ? as now i cant use it . They will investigate further.
I’ve reviewed our internal notes and can confirm that we've not officially tested Gravity Wiz for compatibility with WPML. However, Gravity Forms is fully compatible with WPML itself.
Typically, when translating a Gravity Form, only the translatable text elements are included for the translation and can be translated either automatically or manually. However, Gravity Wiz may introduce custom functionality that WPML does not recognize by default.
I recommend sharing our Go Global program with the plugin’s authors so they can coordinate with our compatibility team to ensure full compatibility with WPML.
