Problem: After installing WPML plugins, the WooCommerce default product page is not displayed correctly, with vertical text on the far right. Solution: If you're experiencing this issue, it's not caused by WPML or the WPML SEO plugin. The problem arises because the product table has many columns, which reduces the space for text, causing it to appear vertically. To resolve this, you can hide the unnecessary columns by using the "Screen Options" at the top right corner of the page. For more details, please check this article: https://jeswebdevelopment.com/vertical-text-when-viewing-posts-in-wordpress/.
Please note that this solution 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 with us.
Problem: The tools tab in the Translation Management section shows an error message "There is a problem connecting to automatic translation. Please check your internet connection and try again in a few minutes". Solution: The problem was caused by a known compatibility issue with the "Email Encoder" plugin. Please create a full backup of your site. Then, visit our errata page for the "Email Encoder" plugin at https://wpml.org/errata/email-encoder-protect-email-addresses-and-phone-numbers-there-is-a-problem-connecting-to-automatic-translation/ and try the workarounds provided there.
If you still need assistance, don't hesitate to open a new support ticket with us.
Problem: The client added custom code to the functions.php file in their child theme to display stock status in a WooCommerce product dropdown but was unable to translate the 'In Stock' and 'Out of Stock' text.
Solution: 1. We advised the client to wrap the hardcoded strings with the gettext function
__()
to make them translatable. Specifically, replace:
return $stock == 1 ? ' - (In Stock)' : ' - (Out of Stock)';
2. We instructed the client to scan the theme for strings from the WPML > Theme and plugins localization page. 3. We directed the client to go to WPML > String Translation, search for the 'In Stock' and 'Out of Stock' strings, and add the translations.
For more details, we provided documentation links:
Problem: The client was adding translations for various languages to a page built with Elementor. While most content translated correctly, the basic text editor widget in Elementor did not translate for the Indonesian language, displaying what appeared to be the widget's ID instead. The WPML translation editor showed the text as translated, but it was not reflected on the front end. Solution: We recommended the client to back up their website and deactivate any additional Elementor plugins one by one to identify which one was causing the issue with the text not displaying in the original language. Once identified, we asked the client to install the problematic plugin on a test site we provided (https://rustic-guitar.sandbox.otgs.work) where Elementor and WPML were already set up with English and Indonesian languages. The client was to create a sample page using the widget so that we could check and provide the proper XML code to make the widget translatable with WPML.
Please note that the solution provided might be outdated or not applicable to your case. If the issue persists, 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 do not hesitate to open a new support ticket. For further assistance, visit our support forum.
Problem: The client is experiencing an issue where the accommodation pricing on their website is correctly displayed in English as "price for 2 nights" but incorrectly in Portuguese, showing "xx per night" even though the price is set for 2 nights. This issue occurs on both the accommodations page and the search availability results on the homepage.
Solution: We recommend the following steps to resolve the issue: 1) Go to WPML > Theme and plugins localization. 2) Scroll down to the *Strings in the plugins* section. 3) Select the *Hotel Booking* plugin. 4) Click to scan for strings and wait until the process is complete. 5) Navigate to WPML > String Translation. 6) Search for the string "for %d nights" or "%d nights". 7) Translate the string into Portuguese, as the original string is in English.
Please ensure to clear all types of caches after performing these steps and check if the issue is resolved.
If the solution provided here is not relevant to your case, possibly because it's outdated or not applicable, we highly recommend opening a new support ticket. Before doing so, please check the related 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 reach out to us on the WPML support forum.
Problem:
After using the "Look for strings while pages are rendered" feature and translating custom strings, the client disabled the feature and encountered a fatal error that prevented access to both the admin area and the site. The error was caused by strings from the Kadence plugin with "%TEXTDOMAIN%" as a context in the
wp_icl_strings
table.
Solution:
We recommended changing the context of the problematic strings in the
wp_icl_strings
table from "%TEXTDOMAIN%" to "kadence" to resolve the issue. Additionally, we advised using the gettext functions
__()
or
_e()
according to WordPress standards for future string translations.
Please note that this solution might be irrelevant if it's outdated or not applicable to your case. If the issue persists, 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 client is experiencing an issue where the menu in the English dashboard does not match the menu on the website. Solution: We recommend using WPML's WP Menus Sync feature located in WPML → WP Menus Sync to synchronize menus across all languages. This will match the translated menus to the default language menu. After synchronization, use String Translation to translate URLs and labels for any custom links. For more information about the WP Menus Sync feature, please visit Translating Menus documentation.
Please note that this solution might be irrelevant if it's 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 in our support forum.
Problem: The client was trying to translate updated information on several pages but encountered an issue where only a few segments of the translation were visible, instead of the entire content.
Solution: First, we advised the client to click on the 'gear' icon and complete the translation of the current fields to 100%. Then, we suggested making a small edit to the default language page/post and updating it. After that, the client should check the translation again to see if the issue persists.
Upon further investigation, we discovered that the custom field 'mfn-page-items' for the builder was set to 'Copy once' instead of 'Translate' in WPML → Settings → Custom Fields Translation. We changed this setting for the client, and after they modified the original page and saved it, the missing builder text appeared in the WPML translation editor for translation.
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 experienced a Fatal Error after attempting to update the WPML Multilingual CMS plugin, which resulted in the WordPress back-end/admin side entering Recovery Mode. Solution: We recommend deleting the WPML Multilingual CMS and WPML String Translation plugins from the WordPress plugins list. Before doing so, ensure to back up your site. Your translations are safe as they are stored in the database and will not be affected by this process. After backing up, download and reinstall the latest versions of the plugins from https://wpml.org/account/downloads/.
Please note that this solution might be irrelevant if it's outdated or not applicable to your specific 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.
Problem: The client is trying to move a development site into production and is unable to find the gear icon on their account page to change the site key settings, as described in the WPML documentation. Solution: If you're experiencing an issue where the gear icon is not visible when trying to move your development site into production, it's likely because the key is already set as a production key. We recommend the following steps: 1. Remove the existing key if it's no longer needed. 2. Generate a new WPML key for the correct domain. 3. Set the new key as a production key in your account settings. 4. Navigate to your site's backend, go to Plugins > Add New > Commercial. 5. Unregister WPML if necessary. 6. Re-register WPML with the new key.
Please note that this solution might be irrelevant if it's outdated or not applicable to your case. If the issue persists, 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 unable to update the WPML String Translation plugin to version 3.2.7. Solution: 1. We recommend trying to update the plugin via the WordPress backend by navigating to Plugins > Add New > Commercial, checking for updates, selecting the plugin, and updating it. 2. If the first method does not work, we suggest the following steps: - First, create a full backup of your website. - Then, deactivate and delete the WPML String Translation plugin. - Next, manually download the latest version of the plugin from WPML downloads. - Finally, go to your website's backend under Plugins > Add New > Upload, upload the zip file, install, and activate the latest version of the plugin.
Please try these steps and let us know how it goes.
Keep in mind that the solution provided might be outdated or not applicable to your case. If the issue persists, 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 do not hesitate to open a new support ticket in the WPML support forum.
Problem: The client is inquiring about the release date of the next WPML version. Solution: We do not have a specific release date for the next major WPML version as our developers are still conducting tests. However, we have released the WPML 4.6.10 beta version, which you can download from the WPML changelog page. Keep an eye on our blog announcements for any updates regarding the release.
Please note that this solution might not be relevant if it's outdated or not applicable to your case. If so, we encourage you to open a new support ticket. We also highly recommend checking related known issues on the WPML known issues page, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins.
Problem: The client reported that their balance of 90,000 WPML credits had unexpectedly dropped to zero without their knowledge, suspecting a technical issue as they had not used the auto-translation feature and the word count of their website did not justify such a high consumption of credits.
Solution: 1. We advised the client to check their Automatic Translation Usage Report by navigating to WPML > Translation Management > Tools > Payment and settings > Automatic Translation Usage Reports. This would allow them to see on what content the credits were used. Documentation on finding past invoices.
2. We provided a screenshot showing the usage of 90,006 credits and explained that the 'Tools' tab might not be visible if the 'Classic Translation Editor' is active. We suggested switching to the 'Advanced Translation Editor' to view the 'Tools' tab. We also considered the possibility that the 'Translate Everything' feature was active and then disabled, which could have led to the high credit usage. Documentation on Translate Everything.
3. Upon further investigation, we discovered a discrepancy in the report where some pages showed FALSE for credit usage, indicating a potential error. We restored the 90,000 credits to the client's account. We also provided additional documentation to help the client understand how Automatic Translation works, its pricing, and how to estimate costs and get a word count of their website.
If the solution provided here is not relevant to your case, because it might be outdated or not applicable, 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 you still need assistance, please open a new support ticket. Contact WPML support.
Problem: The client noticed server activity logs showing an "Unknown Guest" with an IP address (44.213.71.100) suspected to be related to WPML. This activity was recorded when the client's developer was editing translations through WPML's Advanced Translator.
Solution: We investigated the issue and determined that the IP address is from the United States - Virginia, which could be an AWS server or someone using a VPN. We asked the client to consider if anyone else had access to the site, if credentials were shared publicly, or if they worked with a supporter who might be from the United States or using a VPN. We also recommended changing credentials for safety. After further investigation and communication with our development team, we concluded that the activity might not be related to WPML. The client's hosting service, Rocket.net, uses a server-side tool that we do not have control over, and it is difficult to determine the source of the activity. Our team also noted that during translation updates, multiple requests are sent, not just two, which the tool logged. Since the tool operates server-side and not within WordPress, and there are no other similar reports, it is challenging for us to provide a definitive solution.
If you're experiencing similar issues with activity logs and suspect it might be related to WPML, we recommend checking your server logs for any unusual activity and considering the points we raised with the client. However, 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, 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 open a new support ticket.
Problem: The client is experiencing a significant slowdown in the WordPress dashboard when using WPML, particularly when saving menus, which can take over 50 seconds to load.
Solution: First, we recommend updating to the latest version of WPML Multilingual CMS, as version 4.6.9 includes performance improvements. To update, navigate to Plugins > Add New > Commercial and click on "Search for WPML Updates". You can also download the latest versions directly from your WPML account downloads page.
If updating does not resolve the issue, we suggest running WPML > WP Menus Sync to reduce the number of duplicated queries. You can find a guide on how to do this here: Translating Menus.
Additionally, use the troubleshooting options under WPML > Support > Troubleshooting to sync post taxonomies and clear the WPML cache. More information on these options can be found here: WPML Troubleshooting Options.
After these steps, the client should see a significant reduction in duplicated queries and improved performance.
Please note that this solution might be outdated or not applicable to your specific case. If the issue persists, 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 necessary, do not hesitate to open a new support ticket with us for further assistance: WPML 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
