Problem: You are using WPML to translate articles on your website and have switched to the Pay-as-you-go plan. After reaching the €100 limit, the translation stops, and you receive an 'Insufficient funds' message. Solution: If you're experiencing this issue, it's important to understand that there are two safety limits in place when using the Pay-as-you-go plan. These limits are set at $100 and $4,000 to prevent accidental overspending and protect against fraud. Once you reach the first limit of $100, you will be prompted to make a payment before you can continue translating. The amount you pay will then be deducted from your monthly invoice. To check for any open amounts and make a payment, please visit your WPML account.
If this solution does not apply to your situation, or if it seems outdated, 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. Should you need further assistance, please do not hesitate to open a new support ticket.
Problem: The menu shows left-aligned in Spanish, which was not the case before starting the Dutch translation. Solution: We found that a CSS attribute is causing the alignment issue. We recommend removing the following CSS attribute from your site's stylesheet:
display: -webkit-box;
After removing this attribute, the Spanish menu should appear correctly aligned.
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 at WPML support forum.
The client needed editors on their WordPress site to be able to translate their own posts and edit the translations of any other posts using WPML. The editors were encountering a pop-up indicating that they didn't have the necessary permissions to use WPML on posts they initiate.
Solution:
We recommended that the client should assign the editor as both a Translation Manager and Translator under WPML>>Translation Management>>Translator tab. This setup would allow the editor to translate their posts and manage translations of posts initiated by others.
For detailed guidance on setting up and understanding the capabilities of different WPML roles, we advised checking the following documentation:
If this solution does not resolve your issue or 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: The client is trying to register WPML on their site but encounters a connection error stating 'Unable to get data from service. Detailed error: cURL error 28: Operation timed out after 45001 milliseconds with 0 bytes received.'
Solution:
If you're experiencing this issue, it might be due to a temporary problem blocking the connection to our servers. We recommend trying the workaround suggested in a similar case. Please ensure to back up your site before proceeding. You can find the detailed steps here: WPML support forum post.
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. Additionally, please feel free to open a new support ticket for further assistance at WPML support forum.
Problem: The client is experiencing an issue where some elements in the WordPress admin area are displayed in Serbian instead of English, despite the user's language being set to English. Solution: 1) We recommend checking if the issue persists in a minimal environment. Please follow these steps: - Deactivate all plugins except for WPML CMS and String Translation. - Switch to a default WordPress theme, such as Twenty Twenty-One. - If the issue resolves, reactivate the plugins one by one to identify the one causing the issue. Please ensure to back up your database before performing these tests. 2) After the above test, the problem was caused by the "WP Data Access Premium" plugin.
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. Additionally, you can open a new support ticket for further assistance at WPML support forum.
Problem: You are experiencing issues with redirects on your website, where Google Search Console shows problems, and the last redirect done by WPML is incorrect. You are also concerned about the canonical URL settings for different languages as suggested by Yoast SEO. Solution: 1) If you are trying to redirect a trashed URL, ensure the item is not in the trash, is existing, and is published. After confirming this, you can remove the existing redirect rule. 2) Regarding canonical URLs, these should indicate to Google which page is the original to avoid duplicate content issues. This is standard behavior and should not be changed to prevent SEO problems. 3) Ensure you are using the WPML SEO addon from WPML for optimal integration with SEO functionalities. 4) If you have doubts about the SEO settings for the default language, consulting with Yoast SEO is recommended.
If this solution does not resolve your issue or seems outdated, or if it does not apply to your specific case, we recommend opening 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:
You are experiencing issues with missing WPML icons and links on your site, even after deactivating all plugins except WPML and WPML String Translation, and switching themes.
Solution:
We recommend renaming your .htaccess file and check if the problem appears to be solved.
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 the problem persists, please open a new support ticket at WPML support forum.
Problem: The client was unable to point to the correct site URL on their account after copying their live site to a staging environment. The plugin automatically changed the account site URL to the staging site instead of leaving it as the live site. The client also faced issues with changing the Site URL back to the live site URL manually and needed assistance with moving credits linked to the Staging Site URL back into the main credit pool. Solution: If you're experiencing issues with your site URL changing automatically after migrating to a staging environment, we recommend the following steps: 1. Verify that the current site key is valid by navigating to WPML > Support > Installer Support and clicking on "Check now". 2. If the site is not valid, you need to re-register WPML. First, visit https://wpml.org/account/websites/ 3. If the site URL is already registered, delete it from the list. 4. Enter the site URL again or use a new site URL to create a new site key. 5. Click on "Show key" and copy it. 6. Enter the key under Plugins > Install > Commercial (tab) to re-register WPML. If WPML is still registered here, de-register it first. 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 this solution does not resolve your issue or seems irrelevant, please open a new support ticket at WPML support forum.
If these steps do not resolve your issue or if the solution seems outdated or irrelevant to your specific case, we recommend opening a new support ticket. Additionally, 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. For further assistance, please visit our support forum at WPML Support Forum.
Problem: When using the WordPress Gallery core block element with the 'Expand on Click' feature for a lightbox effect, the lightbox displays the original image instead of the translated one, even though the images have been translated using WPML Media Translation. Solution: To ensure that the lightbox displays the translated images, you need to add the following XML configuration to WPML > Settings > Custom XML:
After adding this XML, update or re-translate the page for the configuration to take effect.
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 at WPML support forum.
Problem: If you're experiencing issues with translating 'comparison table' modules in the Rehub theme using WPML, where the table does not translate from French to other languages and the content does not appear in the WPML Advanced Translation Editor. Solution: We recommend adding the following XML configuration to your WP Dashboard > WPML > Settings > XML Configuration (tab):
After adding the code, follow these steps: 1. Go to your Dashboard > Pages. 2. Open the edit screen of the original page and make a minor edit, like adding an extra space. 3. Save the changes. This should trigger an update for translations. 4. Edit the translation again and ensure it is saved up to 100% translated. For more details on making custom Gutenberg blocks translatable, visit https://wpml.org/documentation/support/language-configuration-files/make-custom-gutenberg-blocks-translatable/
If this solution does not resolve your issue or 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 the problem persists, please open a new support ticket at https://wpml.org/forums/forum/english-support/.
Problem: The client needed to synchronize products between Dutch and German versions on their website, using the same SKU for each product. They encountered issues where the German version of a page was not displaying correctly, even though it was published. Solution: We advised the client to use the WPML export and import tool to link translations together, which can be found here: WPML Export and Import documentation. Additionally, for the issue with the German page not displaying, it was discovered that the page was still in drafts, and we recommended publishing it through the language switcher on the admin bar. For the broader issue of synchronizing products, we suggested exporting all feeds and merging them into a single CSV file for each language. This approach allows for the use of the 'Automatic Record Matching to Translate' feature during the import process. We recommended testing this solution on a sandbox site to ensure the correct setup of the 'import template'.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your case, please check the related known issues at WPML Known Issues and confirm that you have installed the latest versions of themes and plugins. If further assistance is needed, we highly recommend opening a new support ticket at WPML Support Forum.
Problem: After moving to a new server and activating the WPML plugin, you are experiencing PHP warnings related to open_basedir restrictions on every page load. This issue started after the server migration, despite using WPML String Translation 3.2.18. Solution: We recommend clearing your logs and cache to ensure that no old server paths are being cached erroneously. It's also important to double-check the logs after performing these steps. If the problem persists, it might be related to specific server settings or configurations that were changed during the server migration. For detailed guidance, please refer to our documentation on this issue: open_basedir restriction issue.
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. Additionally, you can open a new support ticket for further assistance at WPML support forum.
Problem: You are experiencing a Divi Timeout Error when trying to edit translated Divi Builder Template pages in the backend, resulting in a 404 page instead of the template. This issue occurs when the WPML plugin is active. Solution: To resolve this issue, follow these steps: 1. Ensure you edit the Divi Template in the site's default language using the Divi Theme Builder. 2. To translate the template, go to WPML > Translation Management. Use the post type filter to select your template's post type (Header, Body, or Footer Template). 3. Create a translation job for the template and access it at WPML > Translation to translate the template using the WPML Translation Editor. 4. Avoid editing translations directly in Divi when using the WPML Translation Editor as your translation method. If you prefer to create translations directly in Divi, change the translation method to "WordPress Editor" in the right sidebar of the WordPress Editor.
If this solution does not apply to your case, or if it 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 issues persist, please open a new support ticket at WPML support forum.
Problem: You are unable to publish translations for old pages that were previously translated using WPML. These pages remain 'in progress' even though they show 100% completion. Solution: 1. First, try saving the translation inside the WordPress Editor to see if this changes the status from 'in progress' to 'Completed'. This should allow you to open the WPML Translation Editor. 2. If the issue persists, take a backup of your site and then navigate to WPML > Support > Troubleshooting. Use the following options: - Clear the Cache in WPML For more details, visit WPML Troubleshooting Options.
If these steps do not resolve the issue, it 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.
This page includes support tickets that are resolved and documented. Looking for tickets that are “in progress”? Visit the complete support tickets archive
