Problem: You are experiencing issues with translating content created using the Revolution Slider and various widgets (e.g., Section Slider) on your WordPress site using the WPML plugin. Despite following standard procedures, you are unable to locate and translate certain strings from the Revolution Slider and widgets in the WPML String Translation section. Solution: We recommend following these guides to resolve your issue:
These guides provide detailed steps to find and translate the missing strings in the Revolution Slider and widgets.
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 you still need assistance, please open a new support ticket at WPML support forum.
Problem: The client is unable to translate their menu into different English variants such as en-au and en-gb. Solution: If you're experiencing this issue, we recommend following the steps outlined in our guide on translating menus with WPML. You can find the guide here: Translating Menus.
If this solution does not resolve your issue or seems irrelevant due to being outdated or not applicable to your case, please open a new support ticket. We also 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. For further assistance, you can contact us directly through our support forum at WPML Support Forum.
Problem: The client wants to exclude some blocks from autotranslation in WPML, using WPBakery and Gutenberg editors, and inquires whether adding a class to a block can prohibit its translation. Solution: If you're experiencing this issue, we recommend using the manual translation method. This approach allows you to control the translation process more directly, including the ability to add or remove blocks or change styling as needed. For detailed guidance on how to implement manual translation, please visit our documentation: Using Different Translation Editors for Different Pages.
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 at WPML support forum.
Problem: The client is unable to edit conditionals in a translated contact form and is facing an issue with an extra dropdown being created in another form, which copies options from the original dropdown. Additionally, when attempting to review translations, the client is redirected to a preview of the fields instead of the strings. Solution: We suspect this might be a compatibility issue. The client resolved the issue by creating a new contact form in English and adding it only to the English page.
Additionally, to enhance your site's performance, we suggest increasing the WP Memory Limit to 256 MB and the MaxInputVars in your PHP settings to 10000. For more details on increasing memory limits, visit WPML Minimum Requirements and for MaxInputVars, refer to Setting MaxInputVars.
If this solution does not apply to your case, or if it seems outdated, we highly recommend checking related known issues at WPML Known Issues, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If issues persist, please open a new support ticket.
Problem: The client's homepage has been translated from English to Italian, and while the SEO text was translated, the page share image does not appear for the Italian version (/staging/it) when shared on WhatsApp. Solution: We recommend checking if the WPML SEO plugin is active on your site, as it is essential for managing SEO meta information correctly with WPML. If it is not installed, please install it by navigating to Plugins > Add New > Commercial Tab. After activating the plugin, go to the default page, re-add the share image, save the changes, and update the translation. This should ensure the image is copied to the Italian version.
If this solution does not resolve your issue or seems irrelevant due to being outdated or not applicable to your case, we highly recommend opening a new support ticket. Additionally, 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. For further assistance, you can also visit our support forum at WPML Support Forum.
Problem: The client is experiencing a recurring 'WPML detected a new address for this site' message after importing the database and performing search and replace operations during the migration of their site from a local environment to a live server. Solution: We recommend following the steps outlined in the WPML documentation to manage site migrations effectively. This involves ensuring that WPML settings are correctly configured to handle changes in the site URL during migrations. Please start by taking a full site backup. Then, refer to the documentation on using the Advanced Translation Editor during site moves or when using a copy of your site. You can find detailed instructions here: Using Advanced Translation Editor when you move or use a copy of your site Using WPML on two domains
If this solution does not resolve your issue or seems irrelevant due to being 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 further assistance is needed, please open a new support ticket at WPML support forum.
Problem: The client is working on a site under development and is trying to use translation hints in their code. However, they do not see the hint in the translation dialog when using the following PHP code:
printf(esc_html(// translators: %s is a year __( 'Active since %s', 'cnmd' ),), esc_html( $year ));
Solution: The solution in this case would be using the _x() Function which will allow you to add a context to a sting. WPML String Translation does have a column to display this context.
Source: https://developer.wordpress.org/reference/functions/_x/
We further explained that the comment
/* translators: %s: %s is a year */
is intended to provide context to translators who are translating the theme or plugin into different languages. It helps in understanding what the string represents, especially when creating .po language files that accompany the theme or plugin. However, PHP comments, whether single-line (//) or multi-line (/* */), are ignored by the PHP interpreter during script execution. They are meant only for documentation and do not appear on the website or affect the program's execution. For more details on PHP comments, you can visit https://www.w3schools.com/php/php_comments.asp.
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. Should you need further assistance, please open a new support ticket with us.
Problem: The client was unable to complete translations for a page because the translation editor was not accepting edits for an email and a phone number formatted with HTML. The issue persisted across three languages, and all edits for the Khmer language were lost after saving a draft. Solution: We advised the client to ensure that HTML formatting in the default language is replicated in the translation editor to save the translation successfully. Here are the steps we recommended: 1. Navigate to WPML > Settings and locate the Page builders options section. 2. Toggle the option Send to translation the content of raw HTML cells and click Save. If it is already disabled, enable it and save the changes. 3. Make a minor edit to the default page and save the changes. 4. Update the translation and attempt to save the two text elements again, ensuring to format the text as per the guidelines in our documentation: Advanced Translation Editor HTML Markers.
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 or visit our support forum at WPML support forum.
Problem: O cliente estava enfrentando um problema onde, após editar a versão original de uma página no Elementor, algumas das versões traduzidas (ES e EN) eram substituídas pelo conteúdo original. Isso ocorria de forma aleatória. Solution: Nós recomendamos que o cliente realizasse os seguintes passos para resolver o problema: 1. Acesse WPML > Suporte > Solução de problemas. 2. Clique nos seguintes botões: - Sincronizar taxonomias de posts (selecione 'páginas'/'posts' antes de clicar no botão) - Limpar o cache no WPML - Remover entradas fantasmas das tabelas de tradução - Sincronizar IDs de trabalho locais com trabalhos ATE - Sincronizar tradutores e gerentes de tradução com ATE - Atribuir status de tradução ao conteúdo duplicado - Definir informações de idioma - Corrigir atribuição de tipo de post para traduções 3. Limpe os caches do seu site e navegador. 4. Abra a página/post original no editor do WordPress. 5. Faça um pequeno ajuste no título e salve as alterações. 6. Atualize a tradução e verifique se o problema persiste.
Se o problema parecer aleatório, é uma boa ideia realizar mais testes. Se surgirem problemas, sinta-se à vontade para criar um novo ticket e adicionar o link para este ticket como referência. Estaremos felizes em ajudar.
Se a solução fornecida se tornar irrelevante, seja porque está desatualizada ou não se aplica ao seu caso, recomendamos que abra um novo ticket de suporte. Também é altamente recomendável verificar os problemas conhecidos, verificar a versão da correção permanente e confirmar que você instalou as versões mais recentes de temas e plugins. Para assistência adicional, por favor, visite nosso fórum de suporte.
Problem: The client is experiencing site crashes when attempting to update the WPML Multilingual CMS plugin beyond version 4.4.0. Additionally, deactivating the WPML plugin or the theme as suggested causes the site to crash, preventing the use of the OTGS Installer plugin. Solution: We recommend the following troubleshooting steps: 1. Navigate to WPML -> Support -> Troubleshooting. 2. On the troubleshooting screen, sequentially press the following buttons, waiting for each process to complete before proceeding: - 'Disable cache for language switcher templates' - 'Clear the cache in WPML' - 'Remove ghost entries from the translation tables' - 'Fix element_type collation' - 'Set language information' - 'Assign translation status to duplicated content' - 'Set language information' - 'Fix terms count' - 'Fix post type assignment for translations' 3. Go to Woocommerce -> Woocommerce Multilingual -> Settings tab -> Troubleshooting link (bottom right). Select the following options: - 'Sync products variations' - 'Fix translated variations relationships' After completing these steps, generate two CSV files with WooCommerce for Italian and English products to ensure all products are listed correctly.
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 needs to retrieve a value from the converted price of WCML to use it with another plugin, specifically for setting up product feeds in USD for Google Merchant and Snapchat catalogs. Additionally, the client is unable to locate the 'wcml_load_multi_currency' function. Solution: We recommended using the wcml_product_price_by_currency hook to fetch product prices in a specific currency. Here is an example on how to use this hook:
// Get the EUR price of the product ID = 80
$product_id = 80;
$currency = 'EUR';
echo apply_filters('wcml_product_price_by_currency', $product_id, $currency);
This code allows selecting a product and specifying the desired currency to get its price. The client should integrate this hook within the Product Feed PRO Plugin to achieve the desired functionality. Additionally, we suggested that the client check if the Elite version of the Product Feed PRO plugin, which supports WPML, also supports the WCML Currency Switcher or if there are plans for its integration.
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 further assistance is needed, please open a new support ticket at WPML support forum.
Problem: If you're trying to see the WPML plugin in the Plugins page but can't find it after installing WPML string translation, it might be due to another plugin restricting visibility. Solution: We found that the 'Admin Menu Editor Pro' plugin was preventing the WPML plugins from appearing on the Plugins page. We recommend temporarily deactivating 'Admin Menu Editor Pro' to test if this resolves the issue. If you need this plugin, you might need to configure it to allow WPML plugins to show up. If this solution does not apply to your case, or if it 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 you still need assistance, we highly recommend opening a new support ticket at WPML support forum.
Problem: You are trying to import custom post types (CPTs) using XLIFF, but the taxonomies are not being assigned to the posts during the import process. Solution: This issue is already known and is being discussed in an existing support ticket. We recommend following the ongoing discussion and updates on this topic at https://wpml.org/forums/topic/taxonomies-havent-been-added-correctly-if-i-translate-via-xliff. Please avoid opening additional tickets on the same issue as it may affect the priority and handling of your original ticket.
If this solution does not apply to your case, or if it becomes 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 or visit our support forum at WPML support forum.
Problem: The client is developing a site and needs to auto-translate product titles that are in Lithuanian, a language not available on their website, into English. Solution: We recommended creating a Lithuanian language option for the purpose of importing products and then auto-translating them to other languages. The client can hide the Lithuanian language from the website's front end and set English as the default language after completing the translations. For ongoing product imports, the client can use the WPML Translation Management Dashboard to automatically translate batches of content. Additionally, we advised the client to use the WPML translation memory to leverage previous translations and reduce costs. For more details on using automatic translation with custom languages, visit https://wpml.org/documentation/automatic-translation/using-automatic-translation-with-custom-languages/.
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 further assistance is needed, please open a new support ticket at WPML support forum.
Problem: The client's website has pages translated into Chinese, but untranslated pages are incorrectly showing a URL with the Chinese language code (e.g., domain.com/zh-hant/postname) instead of remaining in the default English URL (e.g., domain.com/postname). This issue is believed to be harming SEO. Solution: If you're experiencing this issue, we recommend checking your WPML settings. You might have selected the Translatable - use translation if available or fallback to default language option for Posts and Pages in WPML>>Settings>>Post Types Translation. To resolve this, switch to the Translatable - only show translated items option after performing a site backup. This change should ensure that untranslated pages retain the default language URL. For more detailed guidance, please refer to our documentation on displaying untranslated content: Displaying Untranslated Content on Pages in Secondary Languages.
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 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
