Problem: You are experiencing issues with product variations not being synced when resaving a product using the WPML editor, even after following a guide that temporarily fixed the issue. Solution: 1. Clear the object caches on your site. 2. Make a slight change to the title of the default product and update the product translation. 3. Clear the caches again to ensure all variations display correctly. If the issue persists across many products: - Disable object caching if possible. - Navigate to WooCommerce > WooCommerce Multilingual > Attributes, select the problematic attribute, and click "Synchronize Attribute". - Go to the Status tab and select troubleshooting options as shown here and start the process. For ongoing issues related to object cache compatibility with WPML, refer to the Errata page here and consider using the workaround plugin available here. For excluding specific cache groups, follow the guide here.
If this solution does not resolve your issue or 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 translate a form dropdown list from Jupiter X using WPML. Solution: We recommend the following steps if you're facing a similar issue: 1) Turn off the WPML translation editor for the specific page where the dropdown list appears. 2) Switch to the secondary language of your website. 3) Recreate the forms on the page, ensuring to include the translations for the dropdown list. For detailed guidance on disabling the WPML translation editor and translating content directly, 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 the issue persists, please open a new support ticket at WPML support forum.
Problem: When visiting the Spanish, German, or French versions of the website, the navigation links that should lead to the correct pages are incorrectly translated, resulting in 404 errors. This issue occurs because the URLs in the navigation are being automatically translated, leading to incorrect links. Solution: To resolve this issue, ensure that when translating a page or post that includes links, you also translate and correctly assign the link URL from the translation editor. Here are the steps to follow: 1. Open the default Megamenu template in the WordPress Editor. 2. Make a small change to the template and save the changes. 3. Update the translation. In the translation editor, adjust the relative links correctly for each language. For detailed guidance on how to translate links within WPML, please refer to this guide: How to translate URLs in the Advanced Translation Editor.
If this solution does not apply to your case, or if it seems outdated, we recommend opening 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, please visit our support forum at WPML Support Forum.
Problem: The client is experiencing issues with products not displaying correctly in all languages on their category page. Additionally, there are stylistic differences between the production and staging sites. Solution: 1) For the issue with products not showing in all languages, ensure that all product attributes are correctly translated. This can be done via WooCommerce > WooCommerce Multilingual & Multicurrency, focusing on taxonomies and attributes. After translating, update or re-translate the products to ensure the correct taxonomies and attributes are assigned. 2) Regarding the stylistic issues, these appear to be present in the default language and might not be related to WPML. We recommend disabling WPML temporarily to check if the issue persists. If it does, it suggests the problem is not caused by WPML, and the client should open a new ticket for further assistance.
If this solution does not resolve your issue or seems outdated, please check the related known issues and confirm that you have the latest versions of themes and plugins installed. If necessary, do not hesitate to open a new support ticket with us.
Problem: If you're experiencing a fatal error with translations related to ACF image fields, where an ID is returned instead of the expected image array, this might be similar to the issue discussed in the WPML forum thread: https://wpml.org/forums/topic/acf-galery-field-returns-array-in-main-language-and-id-in-secondary-language/. Solution: We recommend creating a staging site or a copy of your website for further investigation. This allows us to safely explore and resolve the issue without affecting your live site. If you need assistance creating a staging site, please consult your hosting provider. Remember to register WPML on the staging site as well. If providing a staging site is not possible, please inform us in your support ticket.
Please note that the 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, we encourage you to open a new support ticket at WPML support forum for further assistance.
Problem: The client was testing the pay-as-you-go automatic translations option and encountered two issues: (1) an unexpectedly high number of translation credits were used, and (2) the content of the translated page was not visible when trying to review it. Solution: For the first issue, it was clarified that metadata attached to the page was also translated, which increased the word count and thus the credits used. To prevent this, the client can add the following line to their wp-config.php file:
For the second issue, the fields on the page needed to be set to 'Translate' to appear in the translation editor. The client was advised to update the ACF field settings according to the guides on translating sites built with ACF, available here: Setting Field Group Translation Option Expert Translation Option
If these solutions do not resolve your issues or seem outdated, we 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, feel free to contact us directly at the WPML support forum.
Problem: The client was experiencing issues with their sitemap displaying pages that do not exist, specifically URLs containing "/en/" which were remnants of an old language setup. The client had already tried resetting Yoast sitemap and indexables without success.
Solution: We recommended the following steps: 1. Re-enable English as a language temporarily in WPML > Languages. 2. Manually delete all media, pages, custom posts, taxonomies, and menus associated with English using the WordPress User Interface and the language switcher. 3. Remove the English language again and run the cleanup dialog. 4. Check WPML > Settings > Post Type Translation to ensure that any post types that should not be translatable are set correctly. 5. If necessary, temporarily set certain post types (like ACF Field Groups) to 'Translatable' to delete specific entries, then revert them to 'Not translatable'. 6. Run a MySQL query to clean up leftover entries in the database:
DELETE FROM `wp_icl_translations` WHERE `language_code` = 'en'
If these steps do not resolve the issue or if the solution seems outdated or irrelevant to your case, 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 the problem persists, please open a new support ticket.
Problem: If you're experiencing issues with ACF blocks not functioning correctly, it might be due to a conflict with field names that are commonly used in multiple places. Solution: We recommend changing the field name to something unique to avoid conflicts. For example, if your field name is 'title', you could rename it to 'title_new' or use a block slug like 'title_welcome'. After renaming, you will need to re-enter the field data. If this solution does not resolve your issue or seems irrelevant due to being outdated or not applicable to your case, please check the related known issues and confirm that you have installed the latest versions of themes and plugins. If the problem persists, we highly recommend opening a new support ticket with us for further assistance. You can do so at WPML support forum.
Problem: If you're experiencing issues where your translations are stuck in progress for an extended period, often more than an hour, and you encounter errors in the ATE Error Logs indicating that the uploaded XLIFF file is not properly formed with missing or wrong data specifically in the target field. Solution: First, confirm whether you are sending jobs to automatic translation or using the translate everything feature. Try editing a page and updating it, then send it for automatic translation again to see if the issue persists. If the problem continues, navigate to WPML->Troubleshooting -> ATE Error Logs and check the top five errors. If these steps do not resolve the issue, it might be necessary to provide temporary access (wp-admin and FTP) to your site for further investigation, ensuring that you have taken a full backup of your database and website beforehand. We recommend using the Duplicator plugin for this purpose.
Please note that the solution provided 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 was experiencing issues with the WPML sitekey on their staging site, which was set up as a copy of the production site. They were unable to use the same sitekey for both environments due to their deployment process, which overwrites the production database with the staging database. Solution: We advised the client to register separate sitekeys for their production and staging sites. This can be done by unregistering WPML on the staging site through Plugins -> Add New -> Commercial and then registering it with a new sitekey. Additionally, we recommended coding the sitekeys into the
wp-config.php
file for easier management between environments. Detailed steps for this process can be found here: Automatic WPML Registration Using PHP. For sharing translation credits between staging and production, we provided guidance on setting up an automatic translation subscription for multiple sites, which can be accessed here: Automatic Translation Subscription for Multiple Sites.
If this solution does not resolve your issue, or if it seems outdated or irrelevant 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. Should you need further assistance, please do not hesitate to open a new support ticket at WPML Support Forum.
Problem: The client made changes to the menu, and the new pages do not display the menu item anymore. Solution: If you're experiencing this issue, we recommend trying to synchronize the menu in WPML → WP Menus Sync. Ensure that the new pages are also translated. For more detailed guidance, please refer to our documentation on Translating Menus.
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 was experiencing an issue where the Dutch version of a page was not displaying correctly when accessed from the menu, despite the page existing in Dutch. The issue persisted even after creating additional pages and attempting translations. The client suspected a compatibility issue with the Divi theme or a misconfiguration.
Solution: We recommended the following steps to resolve the issue: 1. Verify that the Divi theme version matches the one used in our sandbox environment. If not, update Divi to the latest version. 2. Remove the current custom XML configuration in WPML->Settings->Custom XML configuration and replace it with a new configuration that ensures proper handling of shortcodes and attributes related to the Divi theme. 3. Ensure all URLs include 'www.' to facilitate correct automatic translation of URLs. 4. Update and save the default language page for the payment methods, then access the translation to check if the links are now visible and correctly translated.
If these steps do not resolve the issue or if the solution seems outdated or irrelevant 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 at WPML support forum for further assistance.
Problem: The client has set up a new WordPress installation in a separate directory for a media page and wants to use WPML to manage multiple language versions of the site across different domains. Solution: We recommend installing and registering WPML on the new WordPress installation dedicated to the media page. After installation, configure WPML to use the 'domain per language' setting. This setup will allow the client to manage translations and switch between languages effectively across the domains: https://www.domain.jp/media, https://www.domain.com/media, and https://ch.domain.com/media.
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.
Solution: We recommend updating the Slider Revolution plugin to the latest version, 6.7.11, to ensure compatibility with WPML. Additionally, please verify that you have translated the slides correctly by checking the translated content on your screenshots. If the issue persists, especially with CSS not updating, it might be due to specific settings or conflicts within your theme or other plugins.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your case, we highly recommend opening a new support ticket. 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 https://wpml.org/forums/forum/english-support/.
Problem: You are trying to set up WooCommerce Multilingual to translate your store but encountered a blank page instead of the settings page. Solution: We recommend testing with a minimal setup, using a default theme and disabling all non-WPML plugins to see if the error persists or if you're able to finish the WCML setup. Additionally, it could be that the WordPress memory limit needs to be increased if the current setting is insufficient for WPML's requirements. You can increase the memory limit by adding the following code in your wp-config.php file right before the /* That's all, stop editing! Happy publishing. */ line:
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 our 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
