Problem: The client is experiencing issues with language assignments on their WordPress site using WPML and WooCommerce. Initially, all content was created in English, but after adding Greek and mistakenly setting it as the default language, WPML assigned all existing content, including WooCommerce product categories, as Greek. Changing the default language back to English did not resolve the issue, as many product categories are still assigned to Greek. Solution: We recommend resetting WPML and reconfiguring it with the correct language settings if the client has no translations yet or only a few that can be redone. Here are the steps: 1. Go to WPML → Support and click the Troubleshooting link. 2. In the Reset section of the Troubleshooting page, select the 'I am about to reset all translation and language data' checkbox. Then, click the 'Reset and deactivate WPML' button. Documentation on doing a WPML reset Please ensure to back up your database before making any changes.
If this solution does not apply to your case, or if it seems 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 issues persist, please open a new support ticket.
Problem: The client tries to translate the IDs and anchor links for Gutenberg Heading Blocks. Solution: This issue arises because WPML's XML configuration, on purpose, does not allow translating ID selectors for such blocks. If you have added a custom XML configuration, it will override the default configuration and affect how WPML handles the Gutenberg Block. To ensure that links continue to be translated, your custom XML configuration should include the necessary paths. Here is an example of how you can configure it:
Please test this configuration and let us know if you need further assistance.
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 at WPML support forum.
Problem: The language switcher in the footer offers three languages: Chinese, English, and Arabic. The site defaults to English, but users cannot switch back to English after selecting another language. Solution: We recommend checking if the solution from previous similar issues applies to your case. You can find the discussions and solutions on these links:
If these solutions do not resolve your issue, or if they seem outdated or irrelevant to your specific case, we highly recommend opening a new support ticket. Also, 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.
For further assistance, please contact us through the WPML support forum.
Problem: If you switch to Chinese Simplified on your homepage, you encounter a fatal error. Solution: We found that some strings contained placeholders like
%1$s
,
%3$s
which were either missing or incorrect in the Chinese translation. This discrepancy caused the fatal error. We corrected these placeholders in the affected strings, ensuring they are formatted correctly, such as changing
%1$
to
%1$s
.
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. 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 https://wpml.org/forums/forum/english-support/.
Problem: The client needs to translate custom HTML code using WPML. Solution: We asked the client to provide an example of the HTML code they are trying to translate, along with a screenshot showing where it has been added. We also enabled debug information for the support ticket to better assist the client. We recommended the client to follow the instructions on how to provide this information, which can be found here: http://wpml.org/faq/provide-debug-information-faster-support/
If this solution does not apply to your case, or if it seems 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 you still need assistance, please open a new support ticket at WPML support forum.
Problem: The client is unable to register their site with WPML after extending their subscription and creating a new account due to a 'Site key not matching' error. Solution: If you're experiencing this issue, we recommend following these steps to resolve it: 1. Visit https://wpml.org/account/sites/ and remove the current registration. 2. Navigate to Plugins → Add New and click the Commercial tab. Then, click 'Unregister WPML from this site'. 3. Once the page loads, click on 'Register WPML'. You will see a message asking you to enter the site key. Click on 'Get a key for this site'. 4. In your WPML account, complete the site key wizard and set it to 'Production site'. 5. Copy your new key and paste it in the Commercial tab.
Please ensure that you use the URL in lowercase when registering, such as https://vokeso.com/, to avoid any issues with case sensitivity.
If this solution does not resolve your 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 further assistance is needed, please open a new support ticket at WPML support forum.
Problem: The client is experiencing two issues after installing WPML on their bilingual site (English and Welsh). First, the Welsh translations for fields managed by Advanced Custom Fields (ACF) are not appearing on the front end. Second, all images, which are also managed via ACF, have disappeared from the site. Solution: We recommend the following steps to address these issues: 1. Make a minor edit to the affected page, update it, and then complete the translation. This can sometimes refresh the connection between WPML and the page elements. 2. Check the field translation settings in WPML: - Go to WPML → Settings → Custom Fields Translation. - Find the dynamic field used in Elementor and set it to 'Translate' if you want different content per language, or 'Copy' if the value should remain the same across languages. If these steps do not resolve the issues, we may need temporary access (wp-admin and FTP) to your site to investigate further. Ideally, provide access to a test site where the problem has been replicated.
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.
Problem: If you're experiencing an issue where WPML fails to translate a page and displays the error message: "WPML could not translate this page", and the "Retry" button does not resolve the issue, follow these steps. Solution: 1. Deactivate all plugins except WPML and make a small edit to the original page, update it, and then try to access the translation editor again. 2. If the problem persists, contact your hosting provider to ensure that the following domains are not blocked and are whitelisted if necessary:
wpml.org
cdn.wpml.org
api.wpml.org
api.toolset.com
cloudfront.net
For more details, refer to our guide on WPML plugin connection issues. 3. If the issue still occurs, it might be due to server-side security layers such as firewalls or mod_security. Contact your hosting provider to ensure the REST API is not blocked and temporarily disable any restrictive security layers for testing, or whitelist/exclude WPML-related requests from those protections. More information can be found here: REST API dependencies.
If these steps do not resolve your 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 needed, please open a new support ticket at WPML support forum for further assistance.
Problem: The client is setting up a development site and is unable to register the site to obtain a site key following the instructions provided in the WPML documentation. They are concerned about how to transfer translations using the translation memory. Solution: We explained that the client's current subscription is for end users, which is suitable when a developer or site owner transfers renewals for a single site. This model does not support obtaining a new site key for development sites. We clarified that the site key is primarily used for plugin updates and credit management. Therefore, the client can continue working on the development site without a new site key and use the production site key once the site is ready.
If this solution does not resolve your issue, or if it seems outdated or irrelevant 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 further assistance is needed, please open a new support ticket at WPML support forum.
Problem: After a recent WPML update, the Translation Editor no longer recognizes newly added or updated file links as translatable fields in both the Advanced Translation Editor (ATE) and the Classic Translation Editor. This issue affects file links embedded using Divi modules, where previously these links appeared as "Link Option Url, Url" fields allowing for language-specific versions. However, links embedded before the update are still recognized correctly.
Solution: If you're experiencing this issue, we recommend trying to locate the URLs by typing "http" in the top right section of the Advanced Translation Editor. This might help in identifying the links that are not automatically recognized as translatable fields post-update.
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.
Problem: If you're experiencing issues on your production site where custom fields like 'downloads_*_url_pardot' show a lock icon in WPML > Settings > Custom Fields Translation, preventing you from setting their translation behavior to "Copy", while on your staging environment these fields do not have this lock and can be set to Copy normally. Solution: First, ensure that the 'acf-field-group' post type is set to not translatable in WordPress Dashboard > WPML > Settings > Post Types Translation. If it's already set, no changes are needed there. Next, make a minor edit to the original page (like adding an extra space) and save it. This should prompt an update across translations. If the issue persists, check for any XML code under WordPress Dashboard > WPML > Settings > XML Custom Code tab that might be forcing the lock icon. Also, verify if such XML files exist in your theme or plugin files. If you find the settings are correct but the problem remains, it might be due to the field group settings in ACF > Field Groups > Knowledge Base group field translation option, which should be set to Expert mode to allow changes in custom field translation options. After adjusting these settings, make a small change on the page using the field in the original language and complete the translation to see the results.
If this solution does not resolve your issue, or if it seems outdated or irrelevant 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 needed, please open a new support ticket for personalized assistance at WPML support forum.
Problem: The client was concerned about the high cost of translating 266 words into 15 languages, which amounted to approximately 158€. They also inquired about the most cost-efficient way to translate all strings in their child theme text domain. Solution: 1. We explained that translation costs vary depending on the translation engine used. For instance, WPML AI charges 4 credits per word, while other services like Google Translate and Microsoft Translator may charge less. 2. To manage costs effectively, we recommended selecting the most economical translation engine, using WPML's Translation Memory to save on future translations, and checking the estimated costs on the WPML -> Translation Dashboard before proceeding. 3. For detailed pricing information, we provided a link to our documentation: https://wpml.org/documentation/automatic-translation/automatic-translation-pricing/ 4. We also addressed a specific issue with the translation cost display on the Translation Dashboard, which appeared to be a UX bug. Our 2nd-tier support team investigated and confirmed that the actual charges were correct, and the display issue was cosmetic.
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 problems persist, please open a new support ticket at WPML support forum.
Problem: The client is requesting clarification and missing invoices for several transactions labeled "OnTheGoSystems" on their bank statement, which are not reflected in their WPML account dashboard. Solution: We advised the client to contact our sales team directly for issues related to account transactions and invoices. The appropriate contact email is hello@wpml.org. We recommended sending an email to this address with all relevant details to receive the necessary documentation and support.
If the provided solution does not apply to your case, or if it seems 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. Should you need further assistance, please do not hesitate to open a new support ticket at WPML support forum.
Problem: If you're experiencing PHP warnings on every page load due to the WPML String Translation plugin, where the server logs show 'open_basedir restriction in effect' for files like action-scheduler-en_US.mo, this is due to the plugin attempting to access files using relative paths which conflict with open_basedir settings on your server. Solution: We recommend checking the workaround provided in our forum. Please visit https://wpml.org/forums/topic/warning-file_exists-open_basedir-restriction-in-effect/#post-17634500 for a detailed solution. Before implementing any changes, ensure that you back up your database to prevent any potential data loss.
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 reported an issue with WPML registration, receiving an error 'unable to parse data from service response' when entering their site key. Additionally, the WPML API server showed a red X in the Installer Support section. Solution: We discovered that the client's website domain was blocked by our servers due to an unusual amount of requests. We requested the system team to unblock the site, which they did. Here are the steps we recommended: 1. Unregister and then re-register WPML: - Log in to wpml.org. - Navigate to 'WordPress Dashboard > Plugins > Add New > Commercial (Tab)'. - Click 'Unregister WPML' and then 'Register WPML' on the right section of the screen. - Follow the prompts to get a new site key and enter it. 2. If unable to register, update WPML manually: - Create a backup of your website. - Download the latest version of WPML and its add-ons from https://wpml.org/account/downloads/. - Follow the manual update instructions at https://wpml.org/faq/updating-wpml-manually/.
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 the problem persists, we highly recommend opening a new support ticket at 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
