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.
Problem: The client is unable to translate new Divi pages fully; only the title appears in the WPML Advanced Translation Editor. Solution: First, we recommend completing the translation of the page and then making a small change to the page content in the original language (English). After saving these changes, update the translation to see if the full content appears in the translation editor. If this does not resolve the issue, it might be related to the use of a child theme. Try switching to the main Divi theme, make a small change to the page title or content, save it, and then update the translation page. This should make the page content available in the Advanced Translation Editor.
If these steps do not solve the problem, we suggest checking for any known issues related to this on WPML known issues page, verifying the version of the permanent fix, and ensuring that you have installed the latest versions of themes and plugins. If the issue persists, please open a new support ticket with us for further assistance.
Problem: The client is unable to connect product categories to the correct links in a secondary language using Elementor's mega menu feature. The links remain in the default language after switching languages. Solution: We recommend using the Dynamic content option in Elementor. Go to Dynamic content > Internal URL > Select the category. Make necessary changes to the footer content and save these changes. Afterwards, update the translation to allow WPML to automatically adjust the internal URL when using the Elementor widget Icon List. For further guidance on translating menus, please refer to our documentation: Translating Menus.
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. 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 experiencing an error with the WPML String Translation plugin during the WooCommerce checkout process. The error persists even when the WPML Multilingual plugin is activated. Solution: We recommend ensuring that WooCommerce Multilingual is activated, as it is necessary for WooCommerce to function correctly with WPML. For guidance on activating and configuring this, please refer to our documentation: WooCommerce Multilingual setup guide. If the problem continues, it might be due to a missing file or incorrect setup. Checking the server for missing files or configuration issues that might be causing the error can resolve the issue. If these steps do not resolve the problem, or if the information provided here is outdated or does not directly address your specific situation, 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 issues with translating nested Custom Post Types (CPTs) such as 'quote' or 'contact-person' within a parent CPT post using ACF Pro and WPML. Even though these nested CPTs are translated, they do not always display in the translated version of the parent CPT. Solution: We recommended adding specific HTML to the Gutenberg block code to make the nested CPTs translatable. Here is the code that needs to be added:
<!-- wp:acf/contact {"name":"acf/contact","data":{"block_margin":"margin_default","_block_margin":"field_632ad768f82b2","block_margin2":"","_block_margin2":"field_66226c6c5c17f","composition":"select-contactperson","_composition":"field_662672b951a80","select-contactperson":2342,"_select-contactperson":"field_663cbb0667643"},"mode":"auto"} /--><br /><div class="abcd">here is the block content</div><br /><!-- end block settings wp:acf/contact -->
If this solution does not resolve the 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 further assistance is needed, please open a new support ticket at our support forum.
Problem: The client wants to restart the translation of their website without translating the slugs. They are also concerned about whether they will be charged again for the translation and how to handle already translated slugs. Solution: To restart the translation process without affecting the slugs, we recommend performing a WPML reset. This can be done by following the steps outlined here: WPML Reset Guide. For managing slug translations, you can prevent slugs from being translated by following the guidance in this forum post: Stop Slug Translation. Additionally, to edit an already translated slug, use the quick edit options as detailed here: Change WordPress Page Slug and here for taxonomies: Change WordPress Tag and Category Slug.
If these solutions do not apply to your case, or if they seem outdated, please check the related known issues at WPML Known Issues. We also recommend confirming that you have installed the latest versions of themes and plugins. If further assistance is needed, feel free to open a new support ticket at WPML Support Forum.
Problem: The client is experiencing issues where the English and Chinese versions of their listings are not connected, and images are not being copied to the Chinese version after using WPML All Import. Solution: We recommend using the same unique identifier for both the English and Chinese versions during the import process. This identifier should be set in both the import template and settings for each language. Here are the steps to follow: 1. Ensure that the unique identifier is correctly configured in your WPML All Import settings for both languages. More details can be found in the guide on importing multiple languages with WP All Import and WPML. 2. Delete any previously imported listings that were not connected correctly. 3. Re-import the listings for both languages using the new settings.
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 problems persist, please open a new support ticket.
This page includes support tickets that are resolved and documented. Looking for tickets that are “in progress”? Visit the complete support tickets archive
