The client was experiencing issues with automatic translations getting stuck in the queue after moving their webshop to a new host. Despite trying several troubleshooting steps such as deregistering and registering the site with a new key, and enabling auto translation, the problem persisted.
Solution:
We discovered that the issue was due to a conflict between the IDs of translation jobs and the site ID on our ATE server. Our developers resolved this conflict, ensuring that the automatic translation functioned correctly.
If you're experiencing similar issues, we recommend checking for potential ID conflicts or reaching out for support.
Please note that this solution might be outdated or not applicable to your specific case. We highly 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 issue persists, please open a new support ticket at WPML support forum.
Problem: The client updated their website URL and noticed that the site still appeared to be in development mode despite having a production license. They were expecting not to see a development mode banner but it was still visible. Solution: If you're experiencing this issue, we recommend you try re-registering your website with WPML. Here are the steps to follow: 1. Visit https://wpml.org/account/sites and remove your website from the list. 2. Add it again as a production website and copy the newly generated key. 3. In your website's admin panel, go to Plugins > Add New > Commercial Tab and click on "Unregister WPML from this site". 4. Register the website again using the key you copied in step 2.
This process should help your site recognize the correct license status. If this solution does not resolve your issue or seems outdated, we highly 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.
Problem: The client is trying to use WPML's AI translation feature but finds the available language options limited. Additionally, they are experiencing an issue with an unwanted globe icon appearing next to the menu language switcher in the Buddyboss platform. Solution: For the AI translation feature, WPML AI is currently available in a limited number of languages, and more are being added over time. Clients can check the list of available languages here. If the current languages do not meet the client's needs, it is recommended to use other translation engines like DeepL. Instructions for changing translation engines can be found here. For the issue with the Buddyboss platform, the client should try the workaround provided in the WPML errata here. If that does not resolve the issue, a CSS solution is available here.
If these solutions do not resolve your issues or if they seem outdated, we recommend opening a new support ticket. We also highly recommend checking related known issues here, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. For further assistance, please visit our support forum here.
Problem: You are trying to add new translations to the header, footer, and contact form using WPML > Translations, but the page does not stop loading, and you encounter error messages stating 'Something went wrong, please try again' and 'Unable to retrieve job details'. Solution: We recommend canceling the problematic translation job in WPML under Translation Management → Translation Jobs. After canceling, resend the job from the Translation Management. Once done, you should be able to access and complete the translation from WPML → Translations.
If this solution does not resolve your issue or seems outdated, we highly 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 for further assistance.
Problem: The client is using Elementor and has encountered an issue where images in the default language are not syncing correctly across translations. Despite enabling Media Duplication Settings in the WPML Media Translation plugin and attempting to duplicate media for existing translations, the old images still appear instead of the new ones.
Solution: We recommend the following steps to resolve the image synchronization issue: 1. Perform a bulk translation to all languages using the method 'Self'. 2. Navigate to translation tasks and export the content to XLIFF. 3. Import the same XLIFF file back. This process should update the images across all translations.
Please note that this solution might be outdated or not applicable to your specific case. 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 the issue persists, please open a new support ticket.
Problem: The client is experiencing issues with WPML on their website where some words are not translated into Arabic, and some details are missing in the Arabic version of the property details section. Solution: 1. We recommended following the steps in the WPML documentation to find and translate untranslated strings. For more details, visit https://wpml.org/documentation/getting-started-guide/string-translation/finding-strings-that-dont-appear-on-the-string-translation-page/ 2. Ensure all steps are followed as described in the WP Residence theme's specific WPML guide at https://help.wpresidence.net/article/wpml-help/ 3. We checked the site and found that the strings appear translated when accessing the site in incognito mode, indicating a cache issue. We advised the client to consult with the theme authors to resolve the cache issue caused by the theme.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your case, we highly 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 problems persist, please open a new support ticket.
Problem: The client reported issues with WPML where translations were not appearing correctly, and there was unexpected content on pages that should have been fully translated. The problem seemed related to the translation of strings and iframes. The client also noted that updating WPML and clearing the cache did not resolve the issue. Solution: 1. We recommended updating to the latest versions of WPML Multilingual CMS and WPML String Translation, which can be downloaded from https://wpml.org/account/downloads/. 2. After updating, the client should edit the original content, save the page, and complete the translation again. 3. If the issue persists, we suggested setting up a test site for further investigation by our team. 4. It was also clarified that editing the original content after its translation can clear translated segments and their translation memory, which is expected behavior.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your case, we highly 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 problems continue, please open a new support ticket at WPML support forum.
Problem: You are trying to activate the WPML Multilingual CMS plugin on your WordPress site, but encounter an issue where the Plugins page and Back Office load endlessly. This occurs with both versions 4.7.3 and 4.7.2 of the plugin. Solution: The issue might be due to an outdated theme or a conflict with it. We recommend the following steps: 1. Update your theme and any related plugins. 2. If the problem persists, temporarily switch to a default WordPress theme. 3. Try activating the WPML plugin again. 4. If successful, switch back to your original theme. Please ensure to back up your database before making these changes. If these steps do not resolve the issue, it might be helpful to allow us to create a copy of your site for further testing.
This solution might be outdated or not applicable to your specific case. We highly 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.
Problem: You are using Elementor with WPML on your site and have encountered an issue where updating a custom field in one language affects the other language in an Elementor Loop Carousel. Specifically, when you update the custom field setting in the English version, it also changes the setting for the Polish version, due to shared widget configuration across languages. Solution: To resolve this issue, we recommend using a manual translation approach to prevent synchronization of the custom fields across different languages. You can find detailed instructions on how to implement this by visiting the following documentation: Using Different Translation Editors for Different Pages.
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. We highly recommend opening a new support ticket if you continue to experience issues.
Problem: You want to add HTML 'alt' attributes to flag images in the language switcher on your WPML-powered website, but the current setup only allows modifications directly in core files, which are overwritten during updates. Solution: Currently, there is no permanent solution to add 'alt' attributes to flag images without modifying core files. We acknowledge this limitation and have detailed the issue here: Missing alt tag for flag image in a language switcher.
If this solution does not apply to your case, or if it becomes 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. Additionally, if you need further assistance, please open a new support ticket at WPML support forum.
Problem: You are trying to activate WPML on your site, but updating the site past PHP version 7.4 breaks the theme. Additionally, activating WPML causes a critical error and crashes the site when accessing the translation dashboard. Solution: We have examined the issue and found that the WPML String Translation plugin causes the dashboard to become unavailable due to a critical error, although no errors are shown in the debug.log. We recommend increasing both the PHP memory limit and the WordPress memory limit to 512 MB to potentially resolve this issue. You can find instructions on how to increase the WordPress memory limit here.
If this solution does not resolve your issue or seems irrelevant due to being outdated or not applicable to your case, we highly 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 here.
Problem: You are trying to select the WPML AI translation engine in the option panel, but it is not appearing. Instead, only DEEPL, GOOGLE, and MICROSOFT options are visible. Solution: If you're experiencing this issue, we recommend creating a new support ticket. We highly 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 issue persists, please open a new support ticket.
Problem: You are trying to translate products on your site using WPML and find the new product translation method, which requires assigning translators, unsuitable for your needs. You prefer a method where every admin can translate content directly without needing to be assigned as a translator. Solution: If you're experiencing this issue, we recommend the following steps: 1. Ensure that the classic translation method is selected in WPML. This can be done by navigating to WPML -> Translation Management and checking the settings. 2. If you want administrators on your site to translate products directly, they should go to WPML -> Translation Management, select the products, and assign them to themselves. 3. Alternatively, you can translate products by editing a product in the original language and then clicking on the translation icon that appears in the right column under the Languages block.
Please note that this solution might be irrelevant if it's outdated or not applicable to your case. We highly 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 issue persists, please open a new support ticket.
Problem: The client is working on a site where WPML was set up to use automatic translation, but they prefer to use manual translation and wish to disable the automatic translation feature. Solution: If you're experiencing this issue, the steps to disable automatic translation depend on your WPML version: For WPML 4.7 or greater: Go to WPML > Translation Management and disable the option at the very top. For WPML 4.6 or older: Go to WPML > Settings > Translation Mode and select "Translate what you choose".
Please note that disabling these options does not prevent you from sending content for automatic translation if you have credits or are using Pay as You Go. Also, if you have credits available and open the translation editor, some segments might still be translated automatically. In such cases, we recommend removing all credits from the website.
If this solution does not apply to your case, or if it seems outdated, we highly 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 you still need assistance, please open a new support ticket at WPML support forum.
Problem: You are working on a site and want to exclude certain paragraphs or headings on specific pages from automatic translation using WPML. You have encountered issues where you cannot clear a translation field and save it empty in the ATE, and editing through the WP editor causes the translation to disappear. Solution: Excluding specific paragraphs or headings from automatic translation within the same page using WPML's automatic translation system is not directly possible. To achieve different content on specific translated pages, you can switch from using ATE to the WP editor for those specific pages. This allows you to fully customize the translated versions, including removing content altogether. For detailed steps on how to switch editors and customize translations, please visit Using Different Translation Editors for Different Pages.
Please note that this solution might be outdated or not applicable to your specific case. We highly 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 this does not resolve your issue, please open a new support ticket at WPML support forum.
This page includes support tickets that are resolved and documented. Looking for tickets that are “in progress”? Visit the complete support tickets archive
