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 is split from https://wpml.org/forums/topic/translation-88/