Skip Navigation

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

Problem:
The client is experiencing issues with the 'live populate' feature of Gravity Wiz when used with WPML's string translation. The feature works correctly when WPML strings are deactivated, but fails to populate fields correctly when activated. The client is concerned about the impact of WPML strings on hidden fields within the form, such as "@{:32:selected[0]}".
Solution:
We have not officially tested Gravity Wiz for compatibility with WPML, although Gravity Forms itself is fully compatible. When translating a form, WPML typically includes only the text elements that are marked as translatable. Custom functionalities introduced by Gravity Wiz might not be recognized by WPML by default. We recommend that the client encourages the authors of Gravity Wiz to join our Go Global program to work with our compatibility team for ensuring full compatibility.

If this solution does not resolve your issue, or if it seems outdated or irrelevant to your specific case, please check related known issues at https://wpml.org/known-issues/, verify the version of the permanent fix, and confirm that you have installed the latest versions of themes and plugins. We highly recommend opening a new support ticket for further assistance 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.

This topic contains 1 reply, has 0 voices.

Last updated by Andrey 1 week ago.

Assisted by: Andrey.

Author Posts
June 27, 2025 at 9:23 am #17176733

christianL-79

Hi Andrey,

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.

June 27, 2025 at 9:33 am #17176762

Andrey
WPML Supporter since 06/2013

Languages: English (English ) Russian (Русский )

Timezone: Europe/Kyiv (GMT+03:00)

Thank you for your message.

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.