Problem: The client is trying to translate website content using Memsource/Phrase translation software but is encountering issues with the XLIFF files containing too much code, making it difficult to analyze and translate. Solution: We recommend removing any HTML tags from the content of the specific page or post before exporting it as an XLIFF file. This way, when the XLIFF file is imported into the translation software, it will contain only the textual content without the HTML tags. Unfortunately, we are not aware of any filter within Memsource/Phrase that can hide HTML tags after importing XLIFF files. We suggest reaching out to the Memsource/Phrase support team for specialized assistance in this matter.
If this solution does not seem relevant to your situation, please open a new support ticket with us, and we will be happy to help.
Problem: The client is experiencing issues with certain string translations not working as expected on the checkout page, specifically within the Credit Card details section.
Solution: We recommend the following steps to resolve the issue: 1. Navigate to WPML-> Theme and plugins localization, select your theme/plugin, and scan for strings. 2. Go to WPML-> String Translation. 3. Scroll down and click on the "Translate texts in admin screens »" link. 4. Search for the needed strings. 5. Select the strings you wish to translate. 6. Click on the "Add to String Translation" button. 7. Then click on the "« Return to String Translation" link. 8. Translate the strings, clear the cache, and check if the translations are reflected on the front end.
Problem: The client was experiencing an issue where the product price would change from Euro to Thai Baht during the checkout process, and the currency was not being converted correctly. Solution: We recommended the following troubleshooting steps: 1. Navigate to WPML > Support > Troubleshooting. 2. Click on the following buttons: -
Bookable Resource Synchronize posts taxonomies
-
Clear the cache in WPML
-
Remove ghost entries from the translation tables
-
Fix element_type collation
-
Fix WPML tables collation
-
Set language information
-
Fix terms count
-
Fix post type assignment for translations
After performing these steps, the Euro price should display correctly on the Cart page. We asked the client to recheck the issue on the staging site and inform us of the results.
Problem: After moving a site from a development server to a live URL, the translation panel still shows the development URL in the default language left panel on some pages.
Solution: 1. Check the default content for any links pointing to the development site and replace them with the live site URL. 2. If no such URLs are found, the issue might be due to cached data or entries in the database. Follow these steps: - Back up your site. - Navigate to WPML > Support > Troubleshooting. - Click on the buttons indicated in the provided screenshot to clear any cached data or incorrect database entries. - Open the default page in the Elementor Editor and re-add the link. - Update the translation and check if the development site URL still appears in the translation editor.
If this solution does not resolve your issue, please open a new support ticket with us and we will be happy to assist you further.
Problem: The client needed assistance with translating attribute names, such as "Varianti", into different languages using the WooCommerce REST API. Solution: We informed the client that while the REST API allows for the translation of attribute terms (like 'Blue'), it does not support the direct translation of attribute names (such as 'Color'). To translate attribute names, we advised the client to navigate to WooCommerce → WooCommerce Multilingual & Multicurrency. Within the Attributes tab, they should scroll to the Translations of taxonomy labels and slug section and input the translations there. For more information on using the REST API with WooCommerce Multilingual, we provided a documentation link:
Problem:
ACF custom taxonomy (i.e. using %season% as a URL tag in permalinks) slug translation not working.
Solution:
It turns out that unlike standard permalink tags (i.e. %postname%, %category%, %post_id% and etc), the %season% is a custom permalink tag. Thus it needs to be incorporate and be handled using custom code.
Unfortunately, custom coding is out of scope of this forum. However, following these examples, you can use to register your custom URL tag in WordPress and achieve the purpose. Please see the following articles:
Alternate Solution: (Shared by WPML User)
"After installing the following free version of the plugin, one is able to set the desired translations at the plugins settings and the links work properly now: https://wordpress.org/plugins/permalink-manager/"
Problem: The client encountered a critical error while translating a post using WPML. The error message indicated that the class
WPML_Translation_Jobs_Migration_Repository
was not found in a specific file on their site. Solution: If you're experiencing a similar issue where a class is not found, we recommend checking the file where the class should be located. In this case, the class
. Please download a fresh copy of the WPML plugin and compare the files to ensure they are correct. After verifying the files, reinstall the plugin on your site to see if the issue is resolved. For detailed instructions on how to provide debug information, you can follow our documentation: https://wpml.org/faq/provide-debug-information-faster-support/
Problem: The client is experiencing an issue where the cart banner is not appearing in Divi theme after adding the product to the cart on the Russian version of the website, while it works correctly on the Estonian and English versions. Solution: If you're experiencing a similar issue where a product banner is not appearing after adding a product to the cart in a specific language, we recommend checking the 'product' slug in the WPML → String Translation section. Changing the slug from 'tovar' to 'product' might resolve the issue. If you need to retrieve debug information from your website to provide us with more details, please follow the instructions in this documentation: http://wpml.org/faq/provide-debug-information-faster-support/.
Problem: The client is unable to translate the footer copyright text, even after searching and updating values in the String Translation section of WPML.
Solution: We recommend following these steps: 1. Go to WPML → String Translation. 2. Enable the option "Look for strings while pages are rendered". 3. Visit the page where the untranslated strings are visible. 4. Return to WPML → String Translation and check if the string has been registered. 5. Translate the string.
Problem: The client is experiencing an issue where clicking "Edit" on a post that has a translation redirects to the Advanced Translation Tool instead of the WordPress Editor. The post shows a "gear" icon, indicating that the translation is in progress. Solution: 1. To resolve the issue with the gear icon and redirect, we recommend checking the translation status. If the translation is stuck in the 'in-progress' state, you should cancel the in-progress translation jobs from WPML > Translation Management > Jobs section. For detailed steps, please refer to our documentation: Editing the stuck pages based on the translation mode you use.
2. If you receive a warning after starting to translate a post in our Translation Editor and then trying to edit it manually, you can disable this warning by selecting the checkbox "Don't show this again". If you prefer to edit translations manually, you may need to cancel or delete the existing translations and start a new manual translation. For instructions on how to delete translations, please visit: How to delete the translation of a page.
If this solution does not seem relevant to your situation, please do not hesitate to open a new support ticket with us for further assistance.
Problem: The client was unable to translate the sections "Tienda", "Loop producto", and "Loop tienda" in the Divi Library. Solution: We reviewed the client's website and completed the automatic translation jobs by clicking on the "+" icon. We recommend the client to check if the issue is resolved now.
Problem: The client needed assistance with configuring the WPML plugin to always display the language code in the URL, with "fr" as the default language. Solution: We recommended the following steps: 1) Perform a full site backup. 2) Navigate to WPML>>Languages. 3) Scroll down to Languages URL format. 4) Select the Use directory for default language option under Different languages in directories. 5) Save the changes. 6) Go to Settings>>Permalinks and save the changes again. For more detailed instructions, please refer to our documentation: Setting language URL format.
If this solution does not seem relevant to your issue, please do not hesitate to open a new support ticket with us here.
Problem: The client is attempting to import two product translations into their shop using the WP All Import extension. The import process indicates that two new products have been imported, but the client cannot find them in the shop. The main language of the site is Finnish, and imports for products in this language work correctly. Solution: We reviewed the client's website and import files and confirmed that they are correctly set up. We were able to import and locate the products in WooCommerce. It appears the client may have missed an important step in the importation process. Specifically, during the third step of the import, it is crucial to drag and drop the data from the right column to the left column. If this step is not completed, the imported products will be empty and not visible in the shop. Since this is not an issue with WPML, we recommend the client to carefully review step #3 of the import process and to contact WP All Import support for further assistance if needed.
If this solution does not seem relevant to your situation, please feel free to open a new support ticket with us.
Problem: The client is experiencing a WPML error notice in the troubleshooting page in both their production and test environments. Solution: If you're encountering similar issues, we recommend the following steps after ensuring you have a full site backup: 1) Access your database using a tool like PHPMyAdmin. 2) Navigate to the wp_options table (note that your table prefix may differ). 3) Locate and delete the option keys
icl_admin_messages
and
wpml_notices
. 4) Clear all types of caches on your site.
If this solution doesn't seem relevant to your issue, please feel free to open a new support ticket by visiting our WPML support forum.
Problem: The client's log file is full of database errors indicating 'Duplicate entry' issues, and the server was overloaded, with CPU usage at 100%. The client also mentioned that they are unable to access the Translation Management tab and encountered an error 500 when trying to filter to posts. Solution: IThis is caused by a known error:
WordPress database error Duplicate entry. You can try running this query and see if it helps
DELETE FROM `wp_postmeta`
WHERE `meta_key` = '_icl_lang_duplicate_of';
DELETE FROM `wp_icl_translations`
WHERE `language_code` = '';
This page includes support tickets that are resolved and documented. Looking for tickets that are “in progress”? Visit the complete support tickets archive
