Problem: The values in a form are set to numbers, which cannot be translated, and the plugin retrieves the label as the value. In English, the values are 0 or 1, but in the translated form, it shows the label value. Solution: 1. Navigate to WPML -> Strings Translation. 2. Select the domain gravity_from-6. 3. Locate the strings named radio-30-choice-1-No---$0 and radio-30-choice-0-Yes---$800-value. Change the translation of 1 and 0 to match the original strings. This issue has been resolved in the latest version of Gravity Forms Multilingual, version 1.8.0. So, there is no need to apply the above-suggested workaround. If you are still experiencing issues, we 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 do not hesitate to open a new support ticket at WPML support forum.
Problem: If you're experiencing an issue where after sending Gravity Forms for translation they do not appear in the translation queue, follow these steps to resolve the issue.
Solution: 1. Go to WPML > Support > Troubleshooting and apply the WPML Troubleshooting options. 2. Switch to manual translation in WPML > Settings. 3. Navigate to WPML > Translation Management > Jobs. 4. Cancel the existing translation job for the form. 5. Resend the form for manual translation from WPML > Translation Management and select your user as the translator. 6. Take and translate the job from WPML > Translations. If it opens in ATE, it may be automatically translated. 7. Complete the translation. 8. Switch back to Automatic Translation, and the forms should now appear in the Translations queue.
You now have two options: - Either go to WPML > Translations and click the "Translate" or "Take and Translate" buttons to translate the forms manually. - Or cancel the jobs, switch back to automatic translation, and send the forms for automatic translation.
Please note that this solution might be outdated or not applicable to your case. If the issue persists, we highly recommend checking the related known issues, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If necessary, do not hesitate to open a new support ticket on our support forum.
Problem: If you're experiencing issues with your website where changing the language results in too many redirects, it might be due to a conflict with custom code. Solution: We found that the issue was related to a custom snippet called "Gate for not logged in users". To resolve this, we recommend deactivating the snippet. Here are the steps to follow: 1. Locate the custom code snippet in your website's codebase. 2. Temporarily deactivate the snippet by commenting it out or removing it.
function custom_redirect_to_specific_page() {
if (!is_user_logged_in() && !is_page(109)) {
wp_redirect(home_url());
exit;
}
}
add_action('template_redirect', 'custom_redirect_to_specific_page');
3. Check if the language redirection issue is resolved. If you're not comfortable working with code or if the issue persists, we suggest reaching out to one of our certified partners for further assistance.
