Problem: You are trying to translate all strings of a form using Gravity Forms Multilingual, but some entries from a checklist are not showing translations on the frontend. Additionally, an HTML box doesn't translate well; it reverts to the default language when using the translation editor, despite being fully translated. Solution: 1. Edit the "Rezervační formulář - Aktivity" form. 2. Edit the problematic HTML field. 3. Copy the
<style>
tag content. 4. Delete the tag content and update the form. 5. Go to Appearance -> Customize -> Additional CSS. 6. Add the
<style>
tag content. 7. Go to WPML -> Translation Management. 8. Send the "Rezervační formulář - Aktivity" form to translation. 9. Update the form's translation. 10. Check the translated form on the front end.
If this solution does not resolve your issue or seems outdated, 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 open a new support ticket at WPML support forum.
Problem: You are trying to delete translations for languages that have been removed in WPML's language settings, but the system hangs with a rotating circle and the translations remain undeleted after refreshing the page. Solution: We recommend deleting all taxonomies and translated menus first, and then running the cleanup through WPML -> Languages. If this does not resolve the issue, you could use WP-CLI to delete the terms manually. Here is a script that might help:
#!/bin/bash<br /><br /># Function to get term IDs by taxonomy and language<br />get_term_ids_by_language() {<br />local taxonomy=$1<br />local language_code=$2<br />wp db query "<br />SELECT t.term_id<br />FROM $(wp db prefix)terms AS t<br />JOIN $(wp db prefix)term_taxonomy AS tt ON t.term_id = tt.term_id<br />JOIN $(wp db prefix)icl_translations AS icl ON tt.term_taxonomy_id = icl.element_id<br />WHERE tt.taxonomy = '${taxonomy}' AND icl.language_code = '${language_code}'<br />" --skip-column-names<br />}<br /><br /># Define the languages and taxonomies you want to delete<br />languages=("en" "fr" "es") # Replace with your language codes<br />taxonomies=("product_cat" "product_tag" "category" "post_tag" "nav_menu" "tax_translation_priority")<br /><br /># Loop through each language and taxonomy to delete terms<br />for lang in "${languages[@]}"; do<br />for tax in "${taxonomies[@]}"; do<br />term_ids=$(get_term_ids_by_language "$tax" "$lang")<br />if [ -n "$term_ids" ]; then<br />wp term delete "$tax" $term_ids<br />fi<br />done<br />done
If this solution does not apply to your case, or if it seems outdated, please check the 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. If you still need assistance, we highly recommend opening a new support ticket at WPML support forum.
Problem: The client was trying to redirect a Kadence form submission to a translated 'Thank you' page, but it was redirecting to the original language URL despite the URL being translated. Solution: We reviewed the Form block and confirmed that the Translation support for the Redirect field was correctly implemented. To fix the issue, we modified the link in the Redirect field on the Czech page to a relative format. After saving the changes and updating the English translation, the redirect started to work properly on the English version of the page. If you're experiencing a similar issue, we recommend you try updating the redirect link to a relative format and then updating your translations. Please note that this solution might be irrelevant if it's outdated or not applicable to your case. If the issue persists, we highly recommend checking related known issues, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If you still need assistance, please open a new support ticket.
Problem: The client reported that certain elements such as icon lists from Kadence and standard headings were not being recognized by the Advanced Translation Editor (ATE) in a specific post, despite being translated fine in other instances.
Solution: We recommended the following troubleshooting steps: 1) Navigate to WPML>>Support page and click on the Troubleshooting link. 2) On the Troubleshooting page, perform the following actions in the *Clean up* section, waiting for confirmation after each:
Clear the cache in WPML
Remove ghost entries from the translation tables
Fix element_type collation
Set language information
Fix WPML tables collation
Assign translation status to duplicated content
Fix terms count
Fix post type assignment
Cleanup and optimize string tables
Show custom MO Files Pre-generation dialog box and Generate .Mo files
3) Open the post for editing. 4) Make a minor edit to the post by adding temporary text. 5) Update the post to refresh the translation settings.
We emphasized that the client should try this after a full site backup (mandatory) and report back with their feedback.
Please note that this solution might be irrelevant due to being outdated or not applicable to your case. If so, we highly recommend checking related known issues, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If the issue persists, please open a new support ticket with us.
Problem: If you're experiencing issues with your translated pages showing raw URLs instead of pretty permalinks, such as 'https://example.com/de/?post_type=activity&p=123' instead of 'https://example.com/de/activity/sample-page/', and some menu items also have incorrect link formats, this might be due to the posts being set as drafts. Solution: First, check if the affected posts are set as drafts in the relevant language. If they are, you need to publish those posts.
Additionally, ensure that the 'Let me review it before it gets published' option in WPML>>Settings>>Automatic translation is managed correctly. After completing the translation, review and publish the post's translation.
If the solution provided here is not relevant to your case, because it's outdated or simply not applicable, we recommend opening a new support ticket. We also 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.
Problem: The client was unable to translate the URL of Kadence Advanced buttons using the Advanced Translation Editor (ATE). They expected to find a field to translate the button URL but couldn't locate it, even when searching for "HTTP" or "/". Solution: We recommended that internal site links should automatically adjust when using the WPML Editor for translating a post. We advised the client to update the URL as dynamic post links and then update the post. This should show the correct translation for Kadence Advanced buttons links.
If you're experiencing a similar issue, we recommend you try updating your URLs as dynamic post links and then update your post. If this solution does not apply to your case, or if it seems outdated, please check the related known issues and confirm that you have installed the latest versions of themes and plugins. If the problem persists, we highly recommend you open a new support ticket with us.
Problem:
use ATE to translate a post that contains Kadence Blocks "Testimonial" block Solution:
Please go to WPML->Settings->Custom XML Configuration (tab at the top) and add the following
