Problem: The client was experiencing layout changes when switching languages on their website, specifically from Dutch to English on a particular page.
Solution: We reviewed the page in the Translation Editor and confirmed that the translations were correct. The issue was identified as being caused by HTML output, particularly the use of
<br>
tags that were breaking the layout. We advised the client to open the page with the layout issue directly and switch to the "Text" mode in the affected section to remove all unnecessary HTML formatting. We also provided links to documentation on HTML markers to assist the client in making these changes without breaking the HTML structure.
Please note that this solution might be irrelevant if it's outdated or not applicable to your case. If you're still experiencing issues, 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 problem persists, please open a new support ticket with us.
Problem: The client needed to set different slugs for a custom post type (CPT) archive page in different languages. The default slug was in Spanish, and translating it directly using WPML's String Translation caused issues, resulting in pages not relating properly and 404 errors.
Solution: We informed the client that WPML currently has a limitation when it comes to translating the 'has_archive' option for a unique value, meaning that a direct translation of the CPT archive slug is not possible at this time. We provided a guide for a better understanding of this limitation:
We suggested that if the client enables the 'Has archive' and uses the default CPT's slug, they can then translate that slug from "WPML > Settings > Post Type Translation".
We also mentioned that our development team is aware of this issue and is working on a solution for a future version of WPML, but we do not have an estimated time of arrival for this update.
If this solution is not relevant to your case, either because it's outdated or not applicable, we recommend opening 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 you need further assistance, please contact us in the WPML support forum.
Problem: The client is using WPML to manage multiple language versions of their website and wants to update the URL structure from a two-letter language code (e.g., domain.com/th) to a language-country format (e.g., domain.com/th-th) for SEO purposes. Solution: We recommend navigating to WPML -> Languages -> Edit Languages. Here, you may need to add custom languages to achieve the desired URL format. For detailed instructions on how to add or edit custom languages, please refer to our documentation: Editing WPML's Languages Table.
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: The client wants to have the same slug for a page across different languages in a WordPress site using WPML, where the language URL format is set to different languages in directories.
Solution: If you're experiencing this issue, we recommend adjusting the page URL setting to "Translate" to include the slug in the translation. Then, manually copy the slug from the original language to its translation for new pages. For existing translations, you can use the following workaround:
1. Ensure you have a backup of your site. 2. Navigate to "WPML > Languages" and click on "Edit Languages". 3. Set the "Encode URLs" option to YES for all languages (except the original). 4. Select "Copy from original language if translation language uses encoded URLs". 5. Test by sending a new page to translation. 6. For already translated pages, make a minor edit to the original page and resave it, then resave the translation.
This process allows you to have consistent slugs across different language versions of your site. However, please note that this solution might not be relevant if it's outdated or not applicable to your case. If you encounter any issues or if the solution does not work for you, 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 Visual tab in the Classic Translation Editor is white and not displaying content in some posts. Solution: If you're experiencing this issue, we recommend trying the following steps: 1- Edit the file at
This solution might be 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 at WPML support forum.
Problem: The client is using WPML with WooCommerce Multilingual & Multicurrency and has installed the WooCommerce Product Catalog Feed by PixelYourSite. They are facing an issue where the fields within the Product Catalog tab are not being automatically translated by WPML and are not visible in the String Translation section or the WPML Translation Editor.
Solution: 1) We recommend going to WPML-> Settings-> Custom Fields Translation section, searching for those fields, and setting them as Translatable. After doing so, update the product in the default language and then update its translation to check if the strings appear in the translation editor.
related known issues, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If necessary, do not hesitate to open a new support ticket in the WPML support forum.
Problem: The client was experiencing an issue where Toolset repeat fields were not consistently showing the correct manual translation across multiple pages. Instead, automatic translations were sometimes loaded. Additionally, there were problems with translations not appearing in WPML>Translations for certain languages, and a message indicating a failure to synchronize with the professional translation system was displayed.
Solution: We recommended the client to make minor edits to the primary language page and then re-translate the affected pages. This process should resynchronize the translations and ensure that the correct manual translations are displayed instead of the automatic ones. Specifically, we advised editing the primary language page at
If this solution does not apply to your case, or if it seems outdated, 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. Should the problem persist, please do not hesitate to open a new support ticket with us for further assistance. You can do so by visiting the WPML support forum.
Problem: The client is experiencing an issue after changing WPML configuration to use different domains per language. The Live Composer plugin is not loading when editing a page using the .cat domain, and the WordPress administration top bar is not appearing on the .cat domain.
Solution: We recommend the following steps to resolve the issue: 1. Navigate to WPML > Languages. 2. Under the "A different domain per language" option, ensure the "Auto sign-in and sign-out users from all domains" is selected and save the settings. 3. Go to "Settings > Permalinks" and resave the permalink structure. 4. Log out from your site and log in again to copy the session data and cookies to the secondary domain. 5. Clear the caches from your site and browser. After completing these steps, the admin bar should appear in the secondary language domain.
Please note that the solution provided might be irrelevant due to being outdated or not applicable to your case. If the issue persists, 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 our support forum.
If this solution does not apply or is outdated, or if further assistance is needed, we recommend checking related known issues at https://wpml.org/known-issues/, verifying the version of the permanent fix, and confirming that the latest versions of themes and plugins are installed. If the issue persists, please open a new support ticket in the WPML support forum.
Problem: The client wanted to cancel several translation jobs but was unable to do so, leading to unwanted charges for translations. Solution: We have cancelled the Pay-As-You-Go account for the client and cleared the debt. We explained that translations do not trigger automatically; there must be an action from the client. We also recommended using prepaid credits for future translations to avoid unexpected costs. Prepaid credits can be purchased here: https://wpml.org/account/buy-credits-for-automatic-translation/
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 issues persist, please open a new support ticket at WPML support forum.
Problem: If you're experiencing issues with items not being translated or images not displaying on your translated pages, such as the Shop and Gallery pages, here are the steps to resolve these issues. Solution: 1) For the Shop page where images are not displaying: - Navigate to WPML > Settings and locate the Custom field translation section. - Click on Show System Fields. - Search for '_thumbnail_id'. If found, set its translation preference to 'copy'. - Visit Products > Categories, make a minor edit to any default category, and save to update the image field data across translations.
2) For the Gallery page where posts are not translated: - Ensure the 'Galerie' post type is set to "Translatable - only show translated contents" under WPML > Settings in the 'Post type translation' section. - Translate the posts within the 'Galerie' post type and update the Gallery page translation.
If these steps do not resolve your issues or if the problem persists, 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 solution seems outdated or not applicable to your case, please open a new support ticket at WPML support forum for further assistance.
Problem: The client was unable to add a language switcher to the navigation menus in a custom Full Site Editing (FSE) theme because WPML could not detect the menus.
Solution: We recommended the client to follow the instructions for translating menus in site editor templates, which can be found in our documentation:
We also provided a video demonstrating that the navigation menu and anchor links were working correctly on the French version of the site.
If the solution provided here does not resolve your issue or seems irrelevant due to being outdated or not applicable to your 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 you still need assistance, please open a new support ticket.
Problem: The client is using the 'Motors' theme with WPML to build a multilanguage website and has set the 'Listing' post type to 'non translatable' so that listings are available in all languages. However, when taxonomies are translated, filters do not show listings created in other languages.
Solution: We recommend ensuring that listings in all languages have the taxonomy terms linked to them. If a listing is created in German with the term 'Weiß', it should also include the English term 'White' to appear when filtering by 'White'. If the post type is set to 'Don't Translate', it's usually best to set the taxonomy to 'Do Not Translate' to avoid synchronization issues. Alternatively, you can set the translation preference for the 'Listing' post type to 'Translatable - use translation if available or fallback to default language'.
For automatic translation of listings, WPML does not support automatic duplication, but you can enable automatic translation. Refer to the guide on automatic translation.
If you decide not to translate taxonomies and instead use String Translation for terms like 'White', ensure that the translations are consistent across the site. If you cannot find certain strings, check the Admin Screens section or use the String Translation documentation. For registering individual strings, the wpml_register_single_string hook might be necessary.
Please note that this solution might be irrelevant due to being outdated or not applicable to your case. If the issue persists, 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 needed, do not hesitate to open a new support ticket for further assistance. You can reach out to us on the WPML support forum.
Problem: If you're experiencing issues with product variations disappearing or being duplicated in different languages after updating WooCommerce Multilingual, it might be due to a language mismatch in the icl_translations table.
Solution: First, ensure that the post type
product_variation
is set to "Translatable - only show translated items" in WPML > Settings > Post Types Translation. If the variations are still incorrect, you may need to: 1. Remove all translated variations. This can be done by removing all translated products, which will also remove their variations. 2. Change the language of the affected variations to match the original product language using an SQL query:
#First we obtain the language and store it as a variable
SET @language_code = ( SELECT language_code FROM wp_icl_translations WHERE element_type = 'post_product' AND source_language_code IS NULL LIMIT 1 );
#We get here the post_product IDs for ease of use
CREATE TEMPORARY TABLE temp_ids AS
SELECT element_id
FROM wp_icl_translations
WHERE element_type = 'post_product' AND source_language_code IS NULL;
# We update the post_product_variations based on the post_parent in wp_posts
UPDATE wp_icl_translations
SET language_code = @language_code
WHERE element_id IN (
SELECT ID
FROM wp_posts
WHERE post_parent IN (SELECT element_id FROM temp_ids)
) AND element_type LIKE "post_product_variation";
#Here we clear the temporary table so that we leave no trace
DROP TEMPORARY TABLE IF EXISTS temp_ids;
Alternatively, you can remove and re-create the variations in the original language products. 3. After making these changes, you can update WooCommerce Multilingual to the latest version and re-update products in the original language.
Please ensure you back up your database and website before making any changes. If the variations are still not displaying correctly after following these steps, you may need to re-translate the product to ensure the variations are correct in the secondary languages.
If this solution does not apply to your situation, or if it seems outdated, 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 with us.
This page includes support tickets that are resolved and documented. Looking for tickets that are “in progress”? Visit the complete support tickets archive
