Problem:
The client was trying to translate a page into Chinese, but the content is not visible on the translated page.
Solution:
We have discovered that the content on the Chinese translated page is hidden due to CSS rules. Specifically, the following CSS was causing the issue:
This CSS rule is likely added with the page builder. We recommended checking the custom CSS sections to locate and remove this rule. Once removed, the translated content should display correctly.
If this solution does not seem relevant to your issue, please open a new support ticket with us for further assistance.
Problem: The client is experiencing issues with links on translated pages pointing to the English versions despite running the 'Translate Link Targets' function and clearing the cache. Additionally, the client wants to change all translated URLs to use the English alphabet to avoid unicode characters in URLs. Lastly, there is a specific link to the homepage that, even when translated, redirects to the English homepage instead of the translated versions.
Solution: For the general link translation issue: 1. Open the page in the default language for editing. 2. Edit the translation. 3. In the Advanced Translation Editor (ATE), search for the links (i.e., 'http' or 'https'). 4. Correct the link to the translated version manually. For more details, see how to translate URLs with the Advanced Translation Editor.
Regarding the unicode characters in URLs, this is not an issue as browsers convert them to readable formats automatically. For more information, see Unicode characters in URLs and URL Encoding Reference.
For the specific link to the homepage: 1. Register the Kadence block in WPML -> Settings -> Custom XML Configuration using the following code:
For more details, see how to make custom Gutenberg blocks translatable. 2. Update the English page to trigger the changes. 3. Update Greek and Russian translations. 4. Search for 'http' in ATE and fix the home link as per the translation. 5. Repeat for other pages using this block for the home link.
If this solution doesn't look relevant, please open a new support ticket at WPML support forum.
Problem: The client is unable to activate the OTGS Installer plugin. Solution: We explained that the OTGS Installer plugin is only necessary for the initial installation of the WPML Multilingual CMS plugin. Once WPML is activated, the OTGS Installer is not needed because its functionality is included in WPML. To install or update WPML plugins, the client should go to the Plugins >> Add New Plugin page and click on the Commercial tab. We provided documentation for further guidance:
Problem: The client is experiencing an issue where clicking on categories in the mobile interface in Arabic does not show any categories.
Solution: First, we recommend activating the WooCommerce Multilingual plugin, which is essential for translating WooCommerce Products and their categories. You can install and activate the plugin from the "Plugins > Add new > Commercial" tab.
After activation, translate the categories by following the instructions provided in the documentation.
It's important to translate all products into Arabic and ensure that the categories are translated, which will be done when you fully translate the product. After translating, click on the "Synchronize Product categories assignment in content" button found in the "WooCommerce > WooCommerce Multilingual > Categories" tab.
Solution:
In order to complete the registration process and get a site key, you need to complete all the steps. For example, the user didn't select the type of site, either production or development when registering.
Once completed, you can find a site key to register in your site.
Problem: The client is experiencing difficulty with the process of using the 'Translation Basket' feature in the String Translation section. Solution: To use the translation basket, please follow these steps: 1. Navigate to WPML >> Translation Management. 2. Click on the 'Translation Basket' tab. 3. Select a translator. 4. Click the 'Send all items for translation' button. 5. Go to WPML >> Translations and click the 'Translate' button to start translating using the WPML Translation Editor. Please refer to our documentation:
Problem:
I am trying to update the YouTube video link in English with the Spanish version in the translation editor but it's not added there.
Solution:
The video module from Divi wasn't registered for translation. To make the video link available for translation, please add this code to WPML > Settings > Custom XML configuration:
Problem: If you're experiencing a critical error when switching your WooCommerce product page to a second language, it may be due to a translation issue with placeholders in your theme files.
Solution: We found a fatal error related to incorrect placeholder translation in the theme file
on line 1014. The correct format for translating placeholders like "%1$sarticle%2$s" should maintain the 's' after the dollar sign. If the 's' is missing, it will cause an error.
To resolve this, we recommend you: 1. Visit the WPML > String Translation section. 2. Search for the problematic string. 3. Re-translate it using the correct placeholder format.
For more information on translating placeholders, please refer to the WordPress documentation.
We have already fixed the issue for the reported instance, and the translated product should now display correctly on the front end.
Problem: The client was experiencing issues with WPML, indicated by an error message and malfunctioning of WPML and MO files. Solution: We resolved the issue by manually creating a 'languages' folder within the wp-content directory of the client's WordPress installation. After this step, we confirmed that the error message was no longer present and that WPML and MO files were functioning correctly. If this solution doesn't seem relevant to your issue, please feel free to open a new support ticket with us.
Problem: The client needs to find the corresponding media for another language on a bilingual site (German and English). They have custom meta fields 'photographer' and 'copyright' for media, which are usually the same but sometimes require different texts in English and German. The client wants to display the German fields by default and the English fields only if they are set.
Solution: We recommend using the
wpml_object_id
filter hook to programmatically retrieve the German version ID of a given English media. Here's how you can implement this:
// Assuming $english_media_id is the ID of the English media<br />$german_media_id = apply_filters('wpml_object_id', $english_media_id, 'attachment', true, 'de');<br /><br />// Now $german_media_id holds the corresponding German media ID
You should place this code in the relevant section of your child theme files where you need to access the German media ID. For more information, you can refer to our documentation on wpml_object_id and language-dependent IDs.
Please note that custom coding is beyond our support scope, and it's your responsibility to maintain it. For our support policy, please see here.
If this solution doesn't look relevant, please open a new support ticket in our support forum.
Problem: The client is experiencing slow site performance and suspects that the WPML plugin is consuming a significant amount of resources. Solution: We have analyzed the site's performance and determined that the difference in mobile performance scores with WPML turned on or off is only 2-4 points. This indicates that WPML has a minimal impact on site speed. To improve the site's performance, we recommend focusing on general mobile optimization strategies. If the site's performance does not improve after these optimizations, or if this solution does not seem relevant to your situation, please open a new support ticket with us.
Problem: The client is trying to use automatic translation for their website, but the translations are not being processed automatically and are ending up in the queue for manual translation. Additionally, when attempting to manually translate, no translations are appearing in the fields. Solution: We recommend switching from the Classic Translation Editor to the Advanced Translation Editor (ATE), as automatic translation is only available through ATE. To switch, navigate to WPML -> Settings -> Translation Editor. After switching to ATE, the automatic translation should function correctly.
It is also important to review the documentation on automatic translation and Translation Editors to fully understand the feature:
This page includes support tickets that are resolved and documented. Looking for tickets that are “in progress”? Visit the complete support tickets archive
