Problem: The client reported issues after downloading the OTs installer, noting that the WPML plugin was missing and encountering a database error indicating that certain tables did not exist. Additionally, the client was unable to view content for translation when clicking the '+' in the WPML interface.
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 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.
Problem: The client is unable to translate some fields in their post after migrating their site, receiving an error due to unassigned translation credits. Solution: If you're experiencing this issue after migrating your site, we recommend the following steps: 1. Visit your WPML.org account and go to the List of registered sites page (https://wpml.org/account/sites/). 2. Delete the current sitekey to return the credits to your WPML.org account. 3. Create a new sitekey for your site. 4. In your site admin area, navigate to Plugins > Add new > Commercial tab, then unregister and re-register your site with the new sitekey. 5. Assign credits to your site from your WPML.org account. For more detailed guidance, refer to the following documentation:
If this solution does not resolve your issue or seems irrelevant due to being outdated or not applicable to your case, please open a new support ticket. We also highly recommend checking related known issues (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, you can contact us directly at the WPML support forum.
Problem: The client is experiencing issues with the WPML plugin on their WordPress site, specifically with translating ACF Gutenberg blocks into German. The auto-translate feature inconsistently translates certain headings and the link field text within many blocks remains untranslated. Solution: We recommend the following steps to address the translation issues: 1. Change the field group mode to
Same fields across languages
. 2. Assign a unique field name, such as
boxes_title
, to avoid conflicts and ensure visibility in the Advanced Translation Editor. 3. Make a minor edit to the post (like altering the post title or content), save it, and then update the translation post. 4. If these steps do not resolve the issue, consider using a staging site to perform these changes without affecting the live site. If the problem persists, we suggest 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 solution provided here is outdated or not applicable to your case, please open a new support ticket at WPML support forum.
Problem: The client is experiencing slow site response times of 10-12 seconds when using the WPML and String Translation plugins. The issue persists even after upgrading the server, enabling caching, and creating a staging site. Deactivating the String Translation plugin resolves the issue, indicating it as the source of the slowdown. Solution: We performed several steps to address the issue: 1. Ran the WPML troubleshooting option to "Cleanup and optimize string tables" at WPML > Support > Troubleshooting, and created the necessary custom language MO files at /wp-content/languages/wpml, which improved site performance. 2. Suggested cleaning up the database by following the steps outlined in this documentation. This includes installing a recommended plugin and running the cleanup process multiple times. 3. Provided a SQL query to delete untranslated strings from the WPML String Translation:
DELETE FROM wp_icl_strings WHERE status = 0;
4. Identified that the custom theme significantly increases load times when enabled. Recommended switching to a default theme like Twenty Twenty-Four, which reduced load times to about 2 seconds. 5. Noted an issue in the custom theme's code and provided the correct usage:
If these solutions do not resolve the issue or if they seem 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 the problem persists, please open a new support ticket.
Problem: The client is preparing the translation of a page and encounters an issue where a suffix '-2' is added to the permalink for one of the languages, resulting in incorrect URLs like /data-trends-report-2/?lang=de. Solution: This issue might be due to WordPress's default behavior where it adds '-2' to avoid URL duplication. Possible causes include a deleted translation still in the WordPress 'trash', another page using the same URL, or caching issues. To resolve this, we recommend: 1. Switch the language from the top black bar in the backend of the site. 2. Navigate to Pages, hover over the translated version, and select 'quick edit'. 3. Manually update the URL. If this solution does not resolve the issue or seems irrelevant due to being outdated or not applicable to your case, 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. If the problem persists, we highly recommend opening a new support ticket for further assistance at WPML support forum.
Problem: The client is experiencing an issue where an anchor link that works on their Finnish site does not function on the English version. Specifically, the link on the Finnish site (https://privaon.fi/yritys/#tiimi) works, but its counterpart on the English site (https://privaon.com/company/#team) does not. Solution: We found that the issue with the anchor link not working on the English site is due to case sensitivity in the URL. The anchor was set up as "Team" instead of "team". To resolve this, you should edit the anchor in the Menu button URL to match the case used in the working Finnish site link. For example, if the Finnish site uses lower case (e.g., "team"), ensure the English site uses the same.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your current setup, we recommend opening a new support ticket. Additionally, 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. For further assistance, please visit our support forum at WPML support forum.
Problem: The client is experiencing a fatal error when trying to update WPML String Translation using otgs-installer-plugin.3.1.3.zip, resulting in a frozen screen during the 'activating' process and subsequent fatal errors and notices about incorrect function calls. Solution: We recommend updating the plugins manually. First, download the latest versions from https://wpml.org/downloads/. If your site is down due to the error, navigate to wp-content/plugins/wpml-string-translation, rename the folder to 'wpml-string-translation.deactivate' to regain backend access, then delete and replace the plugin with the downloaded version. Always update the main WPML plugin before updating WPML String Translation. Additionally, ensure you have a recent and working backup before making any changes.
If this solution does not resolve your issue or seems outdated, 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. If problems persist, we highly recommend opening a new support ticket for further assistance.
Problem: You are experiencing an issue where the multi-currency feature is not displaying on your website. Solution: We recommend checking our documentation on Multi-Currency support for WooCommerce to understand how this feature should work: Multi-Currency Support for WooCommerce.
If the solution provided here is not relevant due to it being 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. Should you need further assistance, please do not hesitate to open a new support ticket or visit our support forum at WPML Support Forum.
Problem: The client is experiencing an issue where adding a Currency Switcher to the footer causes the Language Switcher to disappear from the top menu, despite being assigned in the backend. Solution: We first asked the client if they were adding the Currency Switcher from the backend or using a shortcode, and whether the Language Switcher reappeared when the Currency Switcher was removed. We confirmed that there should be no incompatibility between the two switchers and no known issues reported. We requested temporary access to the site to further investigate the issue, suggesting the use of the Duplicator plugin for creating a backup before providing access.
If this solution seems 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: You have translated a PO file using WPML, and it shows as translated, but the translated strings are not reflected on the site. Solution: First, ensure that you have translated the correct strings. Here's how you can verify and correct this: 1. Navigate to WPML >> String Translation. 2. Enable the "Look for strings while pages are rendered" option. 3. Open the page where the untranslated strings are displayed. 4. Return to WPML >> String Translation and check if the string has been registered. 5. Make the necessary translation. For more detailed guidance, visit Finding Strings that Don’t Appear on the String Translation Page.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your case, 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.
Problem: You want to bulk publish over 1900 automatically translated pages on your site, but you can only select 100 pages at a time for translation. Solution: We recommend going to the Screen Options on your dashboard and adjusting the number of items per page to the desired amount. However, please be aware that we limit the number of items displayed at a time to prevent performance issues. It's crucial to backup your database before making these changes. For more details on translating your contents, visit our documentation.
If this solution does not apply to your situation, or if it seems outdated, please open 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, you can contact us directly at our support forum.
Problem: The client is experiencing issues with WooCommerce product variations not syncing correctly between different language versions of their site, even after installing the WPML Non-Persistent Cache as previously advised. Solution: We recommend manually editing each variation in the original product and saving it again. This action should resolve the syncing issue. It appears that the translations may have been damaged, and updating the variations can rectify this problem. If you're experiencing this issue, try the following steps: 1. Go to the original product. 2. Edit each variation. 3. Save the changes. This method has proven effective in similar cases, as demonstrated in the example provided by our support team.
Please note that this solution might be outdated or not applicable to your specific case. If the problem 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 necessary, please open a new support ticket at WPML support forum for further assistance.
Problem: The client is experiencing a critical error when opening the products section in the Arabic interface of their website. The error was traced back to an invalid character in the Arabic translation of a string used in WooCommerce.
'Uncaught ValueError: Unknown format specifier "�" in /wordpress/plugins/woocommerce/8.9.2/includes/class-wc-breadcrumb.php:377'
Solution: We recommended to correct the Arabic translation for the string "ID: %d " in WPML → String Translation. If you're experiencing this issue, we recommend you check the translation for any unrecognized characters and correct them accordingly.
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 problem persists, please open a new support ticket.
Problem: The client needs to translate the consent banner from the GetTerms plugin into Arabic but is unable to find where to add or update the text for translation using WPML. Solution: We checked the GetTerms plugin settings and found no fields to add or update text directly on the cookie popup. The text for the banner seems to be managed externally, as indicated by the redirection to an external site when attempting to update the banner. Since WPML can only translate content stored in the current site's database, it's not possible to translate text managed externally through WPML. We recommend contacting the GetTerms plugin author to inquire if they have a method to display translated content based on the current language setting.
If the solution provided here does not resolve your issue, or if it seems outdated or irrelevant 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 WPML support forum.
Problem: The client was unable to see the language options in the menu after adding the menu language switcher on their site using WPML. Solution: We recommended the client to clear their website's cache to resolve the issue. Additionally, we suggested checking and adjusting the settings for the "Menu Language Switcher" to ensure the navigation menu intended for the language switcher becomes visible. If the problem persists, we advised the client to provide temporary access (WP-Admin and FTP) to a test site where the problem has been replicated for further investigation. It is also important to ensure that the site is backed up before making any changes. For backing up, we recommended using the UpdraftPlus plugin.
If this solution does not apply to your situation, or if it seems outdated, please check the 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. We highly recommend opening a new support ticket if the issue persists.
This page includes support tickets that are resolved and documented. Looking for tickets that are “in progress”? Visit the complete support tickets archive
