Problem: The client is experiencing an issue where the translated version of their website does not match the original design, particularly the header and footer sections. Additionally, the flags and text at the bottom of the page appear incorrectly.
Solution: We found that the header template was not published. We recommend the following steps: 1. Go to the WordPress admin area. 2. Navigate to
Elementor > Templates
. 3. Ensure that the header template is published for the translated language. 4. Clear any caches by appending
?cache=false
to the URL of the translated page. 5. Check the translated page to confirm that the issue is resolved.
Problem: The client is trying to translate only three specific images on their website using the Media Translation plugin. However, after doing so, some other images that do not require translation are not displayed on the translated pages. The client noticed that missing images have a pencil icon in the Media Translation editor, while the images that are displayed correctly have a plus icon
Solution: If you're experiencing missing images on your translated pages after using Media Translation, we recommend the following steps: 1) Navigate to WPML >> Support page, and click on the Troubleshooting link. 2) On the Troubleshooting page, click on the following options in the Clean up section, waiting for confirmation after each: - Clear the cache in WPML - Remove ghost entries from the translation tables - Fix element_type collation - Set language information - Fix WPML tables collation - Assign translation status to duplicated content - Fix terms count - Fix post type assignment - Cleanup and optimize string tables 3) Go to WPML >> Settings >> Media Translation. 4) Click on the Start button and wait for the process to finish.
After completing these steps, delete the homepage translation on the staging site and translate it again. This should resolve the issue as it may have been caused by corruption of the images in the English language.
Problem: The client is experiencing an issue where the breadcrumb translations are not appearing correctly on their multilingual WordPress site when using the Yoast SEO plugin. Solution: We recommend installing the WPML SEO glue plugin, which is designed to integrate WPML with the Yoast SEO plugin. To do this, follow these steps: 1. Navigate to the Plugins > Add New > Commercial section in your WordPress Dashboard. 2. Install and activate the WPML SEO plugin. 3. After activation, translate the page where the breadcrumbs are not showing correctly. This should resolve the issue with the breadcrumb translations. If you find that this solution does not apply to your situation, please open a new support ticket with us.
Problem: The client is trying to import XLIFF files to their WordPress site, but some sections of the language pages are still displaying in English, despite being translated. Solution: If you're experiencing issues with parts of your language pages showing in English after importing XLIFF files, we recommend the following steps: 1. Send the affected page to translation. 2. Export the XLIFF file for that page. 3. Compare the original XLIFF file with the translated one. 4. Ensure that the
extradata
, including both
resname
and
package id
, are identical in both the exported and translated XLIFF files. For example:
5. Make any necessary changes to the translated XLIFF file, not the exported one. 6. Attempt to re-import the XLIFF file. If this solution does not seem relevant to your issue, please open a new support ticket with us.
Problem: The client received an automated email from WordPress indicating a fatal error caused by the WPML Multilingual CMS plugin. The error message specified an issue with the file
class-wpml-tm-icl-translations.php
and mentioned 'No translation entry found for query'. Solution: If you're experiencing a similar issue, we recommend searching for existing tickets that address this error. You can use this custom search URL to find relevant solutions: Google Search for WPML Support Forum. Additionally, you may find a solution in this specific ticket: WPML Support Forum Ticket. Following these steps should help you resolve the issue more quickly. If this solution doesn't seem relevant to your situation, please open a new support ticket in our support forum.
Problem: The client is receiving an error message indicating that a database table related to WPML does not exist. Solution: If you're experiencing a similar issue with a missing database table error, such as
Problem: The client is experiencing an issue where the top menu does not translate from French to English. Solution: We recommend translating all products or at least a few from the WordPress admin area under 'Products' or via WPML -> Translation Management. This action might resolve the issue with the top menu not translating correctly. If this solution does not seem relevant to your situation, please open a new support ticket with us.
Problem: The client's sitemap displays mixed pages from the default and translated versions, and when WPML SEO is active with Rank Math SEO. Solution: If you're experiencing issues with your sitemap showing both default and translated pages, it's important to note that when using language URL format directories, it's normal to have all pages and their translations on the sitemap. There should only be one sitemap for your site. Additionally, WPML automatically adds the
Problem: The client was trying to translate the phrase 'قمة{category} أخبار' and expected to see 'Top {category} news' in English. Instead, they saw 'same-{category} أخبار'. Additionally, there was a concern about the default language of strings. Solution: We requested temporary access (wp-admin and FTP) to the client's site to better understand the issue. We also mentioned the possibility of installing a plugin like "Duplicator" or "All in One WP Migration" to replicate the site locally, with the client's permission. We emphasized the importance of the client making a backup before providing access. After gaining access, we could not find the untranslated content on the English version of the page provided. We asked the client to confirm if the issue was resolved. Regarding the default language of strings, we opened a new support ticket to address that separately.
Problem: The client is unable to see the translated text on the right side when trying to translate a page using WPML. Solution: If you're experiencing an issue where no translated text appears on the right side while translating a page, it's likely because you are using the Classic Translation Editor (CTE). The CTE requires manual input of translations. To utilize automatic translation, you should switch to the Advanced Translation Editor (ATE). Here are the steps to set up the ATE for automatic translations: 1. Visit the WPML documentation on automatic translation: https://wpml.org/documentation/automatic-translation/ 2. Follow the instructions provided to enable and configure the ATE.
If this solution doesn't seem relevant to your issue, please open a new support ticket in our forum: WPML support forum.
Problem: The client is trying to translate the SEO page title and description set by Yoast SEO. Solution: We have created a video tutorial to help you find and translate the SEO metadata for product taxonomies (categories). You can watch the video here:
Problem: The client wants to use the .co.uk domain extension for the United Kingdom instead of the pre-defined language code /en/ to potentially increase organic traffic. Solution: We recommend setting the desired locale for the United Kingdom in WPML by navigating to WPML → Languages and clicking the Edit Languages link. If you wish to use /co-uk/ as a language code, you should add a custom language in WPML by going to WPML → Languages → Edit languages, where you can define your desired language code. For detailed instructions, please refer to our documentation on Adding your own languages using WPML's GUI.
Problem: The client is working on SEO for multiple countries and has encountered two issues. First, they are unable to save different product categories for the same product in different languages. Second, they are questioning the effectiveness of using '/en' for the United Kingdom and considering switching to a '.co.uk' domain extension. Solution: For the issue with product categories, we explained that product categories are synchronized across translations, meaning that if a product is in category 1 in the original language, it will also be in category 1 in the translated versions. To have a product in both categories 1&2 for a translation, the client must add it to both categories in the original language as well. Regarding the domain extension concern, we have opened a separate support ticket to address this issue in detail. The client can follow the discussion and find solutions at https://wpml.org/forums/topic/split-use-en-for-united-kingdom-but-i-dont-get-any-organic-traffic/.
If this solution doesn't look relevant, please open a new support ticket at WPML support forum.
Problem:
Client is unable to translate the links in the "Teaser Box" from the "Total Theme" using WPML. The links in the teaser boxes are not pointing to the translated FR pages but instead to the original EN language pages.
Solution:
First, we registered the
vcex_teaser
shortcode in WPML by adding custom XML configuration. Here is the XML code to add:
After adding this code, the URLs for the teaser box in the default language became available for translation in the Advanced Translation Editor (ATE) and String Translation (ST). To translate URLs in ATE, you can search for "https" and replace it with the translated version of the URL.
Additionally, to ensure the module is registered for translation, follow these steps:
1. Open the original page with the module on the front-end to trigger module registration.
2. Update the original page with a minor change and save it. This will update the translation and add the new module to the Translation Management.
After these steps, you should be able to search for URLs in ATE and translate them accordingly.
This page includes support tickets that are resolved and documented. Looking for tickets that are “in progress”? Visit the complete support tickets archive