Problem: O cliente estava enfrentando um erro no site já com a maioria dos conteúdos traduzidos. Solution: Primeiramente, solicitamos acesso temporário ao site do cliente para poder identificar e resolver o problema. Após obter o acesso, seguimos os seguintes passos para resolver o problema: 1. Navegue até WPML -> Apoio -> Resolução de problemas. 2. Clique nas seguintes opções: - Limpar a cache no WPML - Corrigir o agrupamento de tabelas do WPML - Definir informação de idioma - Repor idiomas - Limpar e otimizar tabelas de strings - Remover todas as mensagens e notificações Estas ferramentas ajudam a corrigir pequenas inconsistências que podem surgir ocasionalmente. A opção 'Remover todas as mensagens e notificações' garante que o erro não seja exibido se não houver realmente um problema, como em casos de cache ou falsos positivos.
Se a solução apresentada não resolver o seu problema, ou se parecer irrelevante devido a atualizações ou diferenças no seu caso, recomendamos que abra um novo ticket de suporte. É altamente recomendável verificar os problemas conhecidos, confirmar a versão da correção permanente e certificar-se de que você instalou as versões mais recentes de temas e plugins. Para assistência adicional, visite nosso fórum de suporte.
Problem: You want to set a minimum order amount in multiple currencies on your WooCommerce site using WPML. Solution: We recommend adding custom code to handle multi-currency minimum order amounts. Follow these steps: 1. Open the
functions.php
file of your theme using a code editor. 2. Insert the following code at the end of the file:
3. Save the changes to the file. This code snippet adjusts the minimum cart total to support multiple currencies through WPML. Additionally, we suggest contacting the developers of the 'Minimum Purchase Amount For Woo Cart – For WooCommerce' plugin and encourage them to participate in our Go Global Program. This will help ensure their plugin's compatibility with WPML.
If this solution does not apply to your situation, or if it seems outdated, please check the related known issues and confirm that you have the latest versions of themes and plugins installed. If issues persist, we highly recommend opening a new support ticket at WPML support forum.
Problem: The client is experiencing issues with the menu structure not being translated, even though the settings are on automatic. Solution: If you're experiencing this issue with your menu not being translated, we recommend that you manually translate the custom menu items. You can do this in WPML -> Strings Translation. For detailed guidance, please refer to our documentation on Translating Menus. Additionally, we have manually edited the English and German menus to correct this issue. It's important to manually translate the menus when using custom items, especially when adding relative links instead of full links. Note that the 'TH Advance Search bar' option should only exist in Dutch.
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 further assistance is needed, please open a new support ticket at WPML support forum.
Problem:
I am working on a site under development and trying to translate internal link of the button using WPML, but the internal links do not show up in the Advanced Translation page.
If you need to translate the slug of the page itself, use these steps: 1) Activate the option "Translate (this will include the slug in the translation and not create it automatically from the title)" in WPML → Settings → Translated documents options. 2) Then, edit the page. Make a minor modification to the page, save it, and navigate to the WPML translation editor. The slug will be added to the translation. Translate or change it and save it.
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 this does not resolve your issue, please open a new support ticket.
Problem: The client is trying to understand how the WPML Translation Editor handles new fields for translation in Elementor, and whether changes in one language automatically reflect in another. Solution: If you're experiencing issues with WPML and Elementor where changes in one language do not automatically sync with other translations, you will need to manually edit the translation of the page to reflect changes made in the original. For a different layout in translations using Elementor, avoid using WPML's Translation Editor. Instead, use Elementor's editor directly for the translations. This approach allows for different layouts in different languages. However, ensure to select this method before translating pages built with Elementor. If translations already exist and were done using WPML's Translation Editor, you should move them to the trash and delete them permanently before starting the translation again using Elementor. Follow the steps in this guide for more details: Using Different Translation Editors for Different Pages.
Please make a full site backup before proceeding with these steps.
If this solution does not apply to your case, or if it seems outdated, we recommend opening a new support ticket. Also, 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. For further assistance, please visit our support forum at WPML support forum.
Problem: The client is unable to approve translation reviews on the translations queue page due to a console error: TypeError: Failed to construct 'URL': Invalid URL. Additionally, there were issues with the WordPress memory limit settings. Solution: We recommended the client to perform a conflict test by: 1. Setting a default WordPress theme. 2. Keeping only WPML Plugins and essential plugins active. 3. Disabling all other plugins. This step helps in identifying if there's any theme or plugin conflict. We also advised ensuring a full backup before making any changes. Furthermore, we noticed that the WordPress Memory Limit was below the minimum requirement for WPML. We suggested increasing the memory limit by adding the following code in the wp-config.php file:
If these steps do not resolve the issue or if the solution seems outdated or irrelevant, 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 further assistance is needed, please open a new support ticket at WPML support forum.
Problem: The client had manually translated their website pages and implemented a custom URL structure for language versions before installing the WPML plugin. After installation, the translated pages were breaking despite disabling translation features in the plugin settings. Additionally, the client wanted to use a basic language switcher without affecting the existing URL structure. Solution: We suggested checking the website from a different browser or device to ensure that the issue was not related to cached data, as the pages appeared to function correctly from our end. For the issue of translating the navigation which was not allowing new menu items to be added, we created a separate support ticket to address it specifically, ensuring focused assistance and better tracking of the issue.
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. Should you need further assistance, please do not hesitate to open a new support ticket at WPML support forum.
Problem: The client needed to change links in a translated page and was unsure whether to use the WordPress editor or another method. They also inquired about the potential issues of editing the translated page with the WordPress editor and how to set the advanced editor after using automatic translation. Solution: We advised the client to manually translate the links using the Advanced Translation Editor. To do this, they should first switch off "Automatic Translation" and select "Translate what you choose" mode. Then, navigate to the primary language page and initiate the translation. In the Advanced Translation Editor, they should type "HTTP" into the search box to locate the links that need translation. For further guidance, we provided a link to a video tutorial on how to translate links: Translating Links with Advanced Translation Editor.
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 wanted to deactivate translations temporarily to import properties in English without incurring additional translation costs. They were unsure if they should deactivate the WPML plugin or if there was another method. Solution: We advised the client against deactivating the WPML plugin as it could lead to confusion with unfiltered translations appearing on the site. Instead, we recommended changing the translation settings in WPML to 'Translate what you choose' from 'Translate everything automatically'. This adjustment can be made in WPML > Settings. This way, the client can control what gets translated and avoid unnecessary costs. Additionally, we provided a link to hide languages from the front end if needed: https://wpml.org/documentation/getting-started-guide/language-setup/hiding-languages-on-the-front-end/
If this solution does not apply to your situation, 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. Should you need further assistance, please open a new support ticket at WPML support forum.
Problem: The client wants to override the language redirection based on the country's IP address using a custom plugin, but it is not consistently working. Solution: We explained that WPML does not support redirection based on the country's IP address nor does it provide a hook for such functionality. We only support redirection based on browser language, which can be found here: Automatic redirect based on browser language. For custom requirements like redirecting users from specific countries to specific languages, we recommended seeking assistance from developers who specialize in custom coding. You can find qualified contractors on our page: WPML Contractors. Additionally, reviewing similar cases might be beneficial, such as this one: Country-based redirect discussion.
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. Should you need further assistance, please do not hesitate to open a new support ticket or visit our support forum at WPML Support Forum.
Problem: The client is using the Klarna Payments for WooCommerce plugin and is unable to find the plugin's strings translated into Greek in the string translation to translate them into English, despite scanning the plugin and theme and using various translation options. Solution: We recommend modifying the plugin's code to ensure WPML correctly identifies and translates the strings. Follow these steps: 1. Edit the file at
Please ensure to back up your site before implementing these changes.
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: Translated Trips are not shown on the Destination (taxonomy) archive pages. The WP Travel Engine plugin, which declares its compatibility with WPML, is not officially compatible as per our list. Solution: We recommend two workarounds: A. Create Trips in each language without translating the Trip from one language to another using the Language Switcher at the top admin bar. B. Manually translate the Trips by duplicating the Trip from one language to another and then clicking the "Translate Independently" button. For more details on this process, please visit https://wpml.org/documentation/translating-your-contents/using-different-translation-editors-for-different-pages/, see section 3.2. Additionally, we suggest contacting WP Travel Engine's support for further assistance and encourage them to join our Go Global Program for official compatibility. Details can be found here: https://wpml.org/documentation/theme-compatibility/go-global-program/. We have also set up a test site to replicate the issue on a fresh WordPress installation. Please install the WP Travel Engine plugin there and check if the issue persists.
If this solution does not resolve your issue or seems outdated, 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. If needed, do not hesitate to open a new support ticket for further assistance.
Problem: The client is using WPML on their site and is unsure why WPML translates row names and images, even though row names are not displayed on the frontend. Solution: We checked the client's website and noticed that some plugins required updating. We recommend updating all plugins to ensure smooth functionality. WPML translates row names to ensure a consistent and comprehensive translation across the entire site, including backend elements that might be used in various contexts. It also translates images to enhance the user experience and improve SEO by providing localized metadata for search engines.
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 further assistance is needed, please open a new support ticket at WPML support forum.
Problem: The client is experiencing an issue where some customized fields are not appearing in the WPML editor for translation. This problem is possibly related to the field size limitation in the database. Solution: We recommend increasing the field size in the database to accommodate larger data. You can do this by executing the following SQL command:
ALTER TABLE `wp_icl_translate`<br />CHANGE `field_type` `field_type` varchar(264) COLLATE 'utf8mb4_unicode_520_ci' NOT NULL AFTER `timestamp`;
Please ensure to replace `wp_icl_translate` with your actual table prefix and make a backup before applying this change. After updating the database, make a minor edit to the main language page to resynchronize the content.
If this solution does not resolve your issue or seems irrelevant due to updates or differences in your setup, 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 experiencing an issue where they receive an error stating 'qEUCHUA is not supported' which prevents automatic translation on their website. Additionally, when clicking on the error, it shows a list of languages without any options to delete or edit.
Solution: If you're encountering the 'qEUCHUA is not supported' error, we recommend mapping Quechua to a supported language in the Automatic Translation Engine. You can find the list of languages supported by the translation engines at https://ate.wpml.org/mt_langs. For more detailed guidance on editing WPML's languages table and using automatic translation with custom languages, please refer to the following documents:
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 further assistance is needed, 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
