Problem: The client is experiencing an issue with registering their website with WPML after migrating from a development URL to a commercial one. Despite resetting and deactivating other plugins, the error 'Unable to parse data from service response' persists. The hosting provider confirmed that their firewall does not block WPML server communication, but suggested that the client's IP might be restricted. Solution: We recommended that the client double-check with their hosting provider to ensure that the following domains are not blocked and are whitelisted:
If this solution does not resolve the issue or seems irrelevant due to being 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 at WPML support forum.
Problem: You are experiencing issues with WP All Import where products are being imported into a different language than the one you set during the import process. Solution: We are aware of this issue and it will be resolved in the next release of the WPML Export & Import plugin. Please keep an eye out for the upcoming release. We will announce it through a blog post and provide detailed documentation on how to implement this. We 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 this solution becomes outdated or does not apply to your case, please open a new support ticket. We highly recommend visiting our support forum for further assistance at WPML Support Forum.
Problem: The client is building a multilingual booking website using WPML, WooCommerce, and MotoPress Hotel Booking. The availability calendars in translated versions of the site often appear fully blocked, even though they display correctly in Spanish. This issue arises when Rates (mphb_rate) and Seasons (mphb_season) are set as 'Translatable'.
Solution: We reviewed the client's website and a test site to compare settings. We noticed discrepancies in the post type and custom field translation settings. We adjusted these settings to their correct configuration and advised the client not to change these settings further. We instructed the client to delete any duplicated translations for 'Accommodations' and 'Seasons', keeping only the content in the default language. After these adjustments, we asked the client to ensure that rates are translated and active for each language. Finally, we verified that the calendars displayed correctly in multiple languages.
If this solution 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 issues persist, please open a new support ticket at WPML support forum.
Problem: You are experiencing issues with ATE translations not completing, and those that do complete take many hours. The error log indicates an 'AMS Server Communication Api error missing resource: No sitekey found for this website.' Additionally, there is a concern about a base64-encoded data URI within an image source attribute that might not be intentional. Solution: First, ensure that your site is correctly registered with WPML and that your subscription for automatic translation credits is active, as these are prerequisites for the Advanced Translation Editor to function properly. If these are in order, the next step is to investigate the specific content causing the issue. In your case, there is an unusually large base64-encoded image URL within the content, which might be affecting the translation process. We recommend removing or replacing this image to see if it resolves the translation delays and errors. If the problem persists or if the solution provided here becomes outdated, 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. If necessary, do not hesitate to open a new support ticket.
Problem: If you're experiencing issues where slugs for translated content in WPML disappear about 30 minutes after being set, leading to redirections to the home page, this might be due to a conflict with the Event Manager plugin. This problem specifically affects the second site language, while the main language remains unaffected. Solution: We recommend deactivating all plugins on your staging site and then trying to reproduce the problem. If the issue persists, reactivate the plugins one by one to identify the conflict. According to a support thread on the WordPress forum (https://wordpress.org/support/topic/wpml-issue-with-eventsmanager/), the Event Manager plugin might be causing the issue. Until an update is available, you could consider downgrading or amending the plugin file directly as a temporary fix.
Please note that this solution might be 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. If the problem persists, please open a new support ticket at WPML support forum for further assistance.
Problem: The client was experiencing an issue where the Advanced Editor jobs synchronization failed when using PHP 8.4, redirecting them to the Translations queue instead of the translation tool. Solution: 1. We recommended downgrading the PHP version to 8.2 or 8.1 and ensuring that WPML is updated to version 4.8.1. 2. We advised activating the WordPress debug mode and checking the debug.log for errors when PHP 8.4 is active. The instructions for activating debug mode can be found here: https://developer.wordpress.org/advanced-administration/debug/debug-wordpress/ 3. We suggested deactivating all plugins, including WPML ones, activating a default WordPress theme like Twenty Twenty, and then reactivating the WPML plugins. If the issue disappeared, the client was to reactivate the theme and other plugins one by one to identify the culprit. 4. Since PHP 8.4 is not fully supported by some WordPress functionalities, we recommended contacting the hosting provider to check server-side logs for any errors.
Please note that this solution might be 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 at WPML support forum.
Problem: The client is trying to make their website multilingual with Armenian as the default language and English and Russian as additional languages. They used the WPML Translation Dashboard to translate the website. However, in the editor, the translated version is displayed correctly, but on the live page, it still shows the Armenian text instead of the translated text. Solution: First, ensure that the server meets the minimum requirements for running WPML, which can be found here: https://wpml.org/en/home/minimum-requirements/ Next, increase the WordPress memory limit to at least 256 MB by adding the following code to the
wp-config.php
file:
define ('WP_MEMORY_LIMIT', '128M');
Place this code just before the comment:
// That's all, stop editing! Happy blogging.
If your hosting provider restricts these settings, contact them to make the necessary changes. After adjusting the memory limits, follow these steps: 1. Edit the page in the default language and make a small edit then update. 2. Open the translation and re-save it. 3. Clear the cache. 4. Go to WPML->Support->Troubleshooting and clear WPML Cache. If the issue persists after these steps, we 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 still exists, please open a new support ticket at WPML support forum for further assistance.
Problem: The client is running a WooCommerce store with WPML in Slovak and Czech languages. The base currency is EUR, and CZK is enabled through WooCommerce Multilingual → Multi-currency. On the Slovak site (EUR), discounts and 'Sale' percentages are correct. However, on the Czech site (CZK), the same products show different prices and incorrect discount percentages.
Solution: 1. Go to WPML -> Languages -> Make themes work multilingual, select the option 'Adjust IDs for multilingual functionality' and click the Save button. 2. Make a small change to a product with this problem and click the Update button. 3. This will also cause a change for the translated product. (You should see the circled arrow icon.) 4. Update the translation of the product. 5. Also, update the translation of the page with the product loop. Check if this fixed the problem.
If the solution provided here does not resolve your issue or seems outdated, we 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 at WPML support forum.
Problem: If you're experiencing issues with translating content that starts with numbers followed by dots (e.g., '1.1.') using WPML's Advanced Translation Editor, where such text remains untranslated in other languages, this might be due to a formatting issue recognized by the editor. Solution: We recommend removing the last dot after the number sequence. For example, change '1.1.' to '1.1' without a dot after the second number. This adjustment should make the sentences appear for translation in the Advanced Translation Editor. You can also use the search field in the editor to locate these specific sentences by searching for the dot (.). Please note that this issue is fixed with the latest versions of the Advanced Translation Editor.
Please note that this solution might be 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. If the issue persists, please open a new support ticket.
Problem: You are trying to translate a page using WPML's Advanced Translation Editor (ATE) and encountering an issue where the ATE displays media from a previous version of the page, causing an unexpectedly high word count. Solution: We recommend checking your media library. Please switch to the list view in your media library, search for the media in question, and check the "Attached to" column. If the media is still attached to the page or post, you should unattach it. This action typically resolves the issue.
If this solution does not apply to your case, or if it seems outdated, we encourage you to 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, please visit our support forum at WPML Support Forum.
Problem: The client was trying to translate the word 'height' to German 'Höhe' under Taxonomy Translation in Label translation. However, the special character 'ö' was not translated correctly and was saved as an HTML entity.
Solution: We initially suggested that the issue might be caused by a third-party plugin or a database collation issue, which should be utf8mb4_unicode_ci. We requested temporary access to the site to investigate further. However, the client managed to resolve the issue by themselves. They found the word under String Translation and changed the translation to a different word to test if it would reflect the change. After confirming the change, they reverted it back to the correct translation 'Höhe'.
If you're experiencing a similar issue, we recommend checking your database collation and ensuring it is set to utf8mb4_unicode_ci. Additionally, try modifying the translation in String Translation to see if changes are reflected correctly.
Please note that this solution might be 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 at WPML support forum.
Problem: The client is trying to connect a staging site to the main website using the same site key for WPML, but encounters an error message 'Fehler beim Verbinden der Websites' (error connecting website) when inserting the key from the development site into the production site. Solution: 1. Each site must have its unique site key. If you're experiencing this issue, follow these steps: - Visit https://wpml.org/account/websites/ - If the site URL is already registered, delete it from the list. - Re-enter the site URL to generate a new site key. - Click "Show key" and copy it. - Enter the key under Plugins > Install > Commercial (tab) to re-register WPML. If WPML is still registered there, de-register it first. 2. If the staging site remains in use, use the "Copy" option on the migration banner to ensure each site uses a proper key. 3. Go to WPML > Support > Installer Support and click "Check now" on each site, then send screenshots of both reports.
If this solution does not resolve your issue or seems outdated, we 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: You are unable to log into the Dokan Pro Dashboard on the front end as a vendor when 'WPML Multilingual CMS' is activated. All menu links redirect to the Dashboard instead of functioning correctly. Solution: We recommend installing the 'Dokan WPML' plugin to ensure compatibility between WPML and Dokan Pro. You can download and install it from https://wordpress.org/plugins/dokan-wpml/.
If this solution does not resolve your issue or seems outdated, please check the related known issues at https://wpml.org/known-issues/, verify you have the latest versions of themes and plugins, and consider opening a new support ticket for further assistance at WPML support forum.
Problem: You are working on a site under development and trying to change the source language of a Gravity Form using WPML. When selecting all string translations for the form, you receive a message: 'You have selected strings belonging to a package. Please select all strings from the affected package or unselect these strings.' The message does not specify which package, preventing you from changing the language of the form. Solution: To resolve this issue, follow these steps: 1. Go to the WPML > String Translation page. 2. Use the search filter to find strings related to your Gravity Form. 3. Check the 'Belongs to a package' column to identify the package name associated with the strings. 4. Once identified, either select all strings from that package or deselect the strings as needed. 5. After adjusting your selections, try changing the source language again.
If this solution does not apply to your case, or if it seems outdated, we recommend opening a new support ticket. Also, check the related known issues and verify that you have installed the latest versions of themes and plugins. For further assistance, please visit our support forum.
Problem: The client is experiencing an infinite redirection loop when visiting the English version of their site with the WPML SEO plugin activated. This issue arises after changing their setup to have each language in its own directory, with an HTML page at the root URL that redirects based on browser language.
Solution: 1) Ensure you are following the steps in our documentation to set up the Language Directory for the default language: Redirect the root domain to the default language Language setup for directory default language 2) Upgrade to the latest version of WPML plugins (4.8.1 series). 3) Go to WPML >> Languages >> Languages URL format, and resave the settings. 4) Visit Settings >> Permalinks, and resave the settings. 5) Clear all types of caches. 6) Check for unexpected redirects set inside the "Redirection" plugin or other SEO plugins like Yoast SEO Premium, as these might conflict with WPML's settings.
If these steps do not resolve the issue, it might be due to specific configurations or conflicts within your site. We 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.
This page includes support tickets that are resolved and documented. Looking for tickets that are “in progress”? Visit the complete support tickets archive
