Problem: If you're experiencing an 'Out of Credits for Automatic Translation' error while using the pay-as-you-go translation service with WPML, it might be because you have reached the automatic translation safety limit of €100 per month. Solution: We recommend trying to add a new translation by clicking the plus icon on a page. In the Translation Editor (ATE), you will see a 'Not enough credits' message with a link to purchase more credits. Use that link to top up your account and continue translating.
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 at WPML support forum.
Problem: You purchased WPML but found that your website is already configured with Polylang. Activating WPML alongside Polylang causes critical errors due to conflicts between the two translation plugins. Solution: If you're experiencing critical errors due to both WPML and Polylang being activated at the same time, we recommend following these steps: 1. To migrate from Polylang to WPML, please consult our documentation here: https://wpml.org/documentation/migrate-polylang-wpml/ 2. If you decide that you would prefer a refund, you can request it through this link: https://wpml.org/purchase/refunds/
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 at WPML support forum.
Problem: If you're trying to translate your website using WPML and encounter a fatal error when previewing or accessing the translated version, it might be due to incorrect string loading in the Doctery theme's add-ons file. Solution: We recommend the following steps: 1. Open the file
plugins/doctery-addons/doctery-addons.php
. 2. Navigate to line 291. 3. Identify any text that might be translated. 4. Use WPML's String Translation to search for that text and delete the problematic string. 5. Additionally, search for the string 'Search %1$s' and ensure there is no space causing the '$' to not parse correctly.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your case, please visit our known issues page and check if there's a permanent fix available. Ensure you have the latest versions of your themes and plugins installed. If the problem persists, we highly recommend opening a new support ticket with us for further assistance.
Problem: You are trying to install the WPML plugin using the OTGS Installer, but it is not working across multiple websites. Solution: If you're experiencing this issue, we recommend following these steps to resolve it: 1) Visit https://wpml.org/account/websites/ 2) If the site URL is already registered, delete it from the list. 3) Re-enter the site URL to create a new site key. 4) Click "Show key" and copy it. 5) Go to Plugins > Install > Commercial (tab) on your WordPress dashboard and enter the key to re-register WPML. If WPML is still registered there, de-register it first.
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 you still need help, please open a new support ticket at WPML support forum.
Problem: You are trying to translate a post on your website, but not all content, including images and text from ACF fields, is appearing in the translated version. Solution: First, ensure that your ACF Field Groups are set to "Same fields across languages" in the WPML settings. This configuration allows all fields to be automatically prepared for translation using the WPML Translation Editor. You can find a guide on how to translate ACF with WPML here: https://wpml.org/documentation/related-projects/translate-sites-built-with-acf/ Additionally, check that the ACF Field Groups in WPML > Settings > Post Type translation are set to "Not translatable" and that there are no translated field groups in the backend. The ACF Field Groups should only exist in the site's default language. After adjusting these settings, edit the original content, save the post or page, and then update the translation. If these steps do not resolve the issue, we recommend opening a new support ticket. Also, 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: WPML Support Forum.
Problem: The client is experiencing translation errors on their website and has issues with the WPML plugin not showing updates due to incorrect site registration. Solution: 1. Visit your WPML account at https://wpml.org/account/sites/ 2. Remove any existing registrations for the site. 3. Unregister the site from the WPML plugin by navigating to your-domain.com/wp-admin/plugin-install.php?tab=commercial and clicking 'Unregister this site'. 4. Re-register the site by clicking 'Register this site', which will redirect you to your WPML account to complete the registration. 5. Copy the new site key provided and enter it back on your site's WPML plugin page.
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 further assistance is needed, please open a new support ticket at WPML support forum.
Problem: The client reported that when logging in as a WordPress Editor role user, they received an error message stating "Sorry, you are not allowed to access this page." Solution: We resolved the issue by assigning the 'Editor Test' as the translator and setting the Chinese language for them. This adjustment allowed the editor to access and edit the translations successfully.
If you're experiencing similar issues, we recommend checking the user roles and permissions in your WPML settings. Ensure that the appropriate roles are assigned the necessary permissions to edit translations. For more detailed guidance, please visit our documentation on managing translator roles and permissions: Managing Translator Roles and Permissions.
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.
Problem: The client is experiencing an issue where the inventory quantity on the English version of a WooCommerce site is not synchronized with the Greek version. All Greek products incorrectly show only 1 item in inventory, despite attempts to synchronize product taxonomies. Solution: 1. Navigate to WPML -> Settings -> Custom fields and click on Show System Fields. Search for 'stock' to check if it is set as 'copy'. 2. Go to WooCommerce -> WooCommerce Multilingual and click on the Status tab. At the bottom of the page, click on the 'troubleshooting' link and run through the options on this page. Ensure you have a full backup of your site before proceeding. 3. Update your WPML plugin and add-ons to the latest version, 4.8, to ensure you have the latest bug fixes and improvements. You can find the latest versions under My Account -> Downloads. Remember to backup your database before updating. 4. After updating, check if the inventory issue persists. If it does, try disabling all plugins except WPML, WooCommerce Multilingual & Multicurrency, and WooCommerce to see if the problem still occurs.
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 the problem persists, please open a new support ticket.
Problem: The client is trying to configure the WPML plugin for automatic translations with the Leksa theme but is facing issues as many elements do not automatically appear in the WPML translation editor. The client needs help setting up the wpml-config.xml file correctly. Solution: We recommended using the Multilingual Tools add-on to generate the XML configuration. Detailed guidance on setting up the XML file can be found in our documentation: https://wpml.org/documentation/support/language-configuration-files/ We also advised the client to ensure that a full backup of the site is created before making any changes. After updating all plugins and themes to their latest versions, we registered the homepage elements following the steps described in our guide: https://wpml.org/documentation/support/multilingual-tools/ The client was then instructed to go to WPML -> Translation Management, select the homepage, and send it for translation to check if all elements now appear.
If this solution does not resolve your issue, or if it 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 further assistance is needed, please do not hesitate to open a new support ticket at WPML support forum.
Problem: The client is experiencing an issue where the
$_POST
variable returns empty when the WPML plugin is active. This problem occurs because the 'action' parameter of the form includes a language parameter (?lang=en), causing a redirect that fails to forward the form data to the intended destination. Solution: We recommend removing the language parameter from the 'action' URL if the default language is English, as this will prevent unnecessary redirects. For handling multiple languages, consider setting up the 'Different languages in directories' option available in WPML -> Languages. This setup helps manage language-specific URLs more effectively. Before making changes, ensure to back up your website and database, and if possible, test these changes on a staging site first.
If this solution does not resolve your issue or seems outdated, please check the related known issues 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.
Problem: If you're experiencing an issue where the WooCommerce lateral menu in the My Account section is not visible in the Spanish version of your site, this summary might help. Solution: We recommend following these steps to resolve the visibility issue: 1. Edit the English page using the UX Builder. 2. Access the post settings. 3. Change the template from 'Default Template' to 'WooCommerce - My Account' template. 4. Save the changes and exit the settings. After these adjustments, refresh the Spanish My Account page to check if the sidebar is now visible.
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 link already translated pages to multiple languages on your site using the 'connect with translations' link, but you can only connect one other language instead of the two additional languages. Solution: Here are the steps to connect each translated page to your default language page: A) Connect "French page" as French (FR) translation of "Dutch page": - Edit your "French page". - Expand the Language section and set the language of your page to French. - Switch to WordPress Editor, and in the popup that appears, leave the selection at This Post. Click Apply. - Click on Connect with translations. A popup will appear. Search for the "Dutch page" and click Ok. - Another dialog will appear. Uncheck the box if you do not want to set the current page as the default language. B) Connect "English page" as English (EN) translation of "Dutch page": - Repeat the steps as above, setting the language to English. C) Connect "German page" as German (DE) translation of "Dutch page": - Repeat the steps as above, setting the language to German. After following these steps, your pages (French, English, German) will be linked as translations of the Dutch page.
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 trying to translate the placeholder text in Contact Form 7 using WPML, but the placeholder does not appear on the translation page as expected. Solution: If you're experiencing this issue, we recommend checking the syntax used for your placeholders. Contact Form 7 requires double quotes for placeholder text. For example, if your form code looks like this:
[text* yourname placeholder 'YOUR NAME*']
You should update it to:
[text* yourname placeholder "YOUR NAME*"]
After updating, retranslate the form. This should resolve the issue and the translated placeholder should appear correctly on the frontend.
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 at WPML support forum.
Problem: You are experiencing a technical problem with your Language Switcher plugin causing an E_PARSE error in langswitch.php, making your WordPress site unavailable. Solution: First, ensure that your WordPress debugging is enabled to capture detailed error information. Modify your
wp-config.php
file by changing
define('WP_DEBUG', false);
to
define('WP_DEBUG', true);
. Then, add the following lines just before the 'stop editing here' comment in your
file in your site's root directory, which will log all errors. Please review this log to identify and resolve issues.
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 with us.
Problem: The client was experiencing persistent loading and sporadic 404 errors on translated pages of their website after using WPML. The issues included pages not displaying after translation and random 404 errors when switching languages. Solution: We recommended the following steps to troubleshoot and resolve the issues: 1. Ensure all pages are correctly translated by making a minor edit in the original language, saving it, and then updating the translation. 2. Check and flush cache settings, as stale cache data might lead to pages not loading correctly. 3. Deactivate and reactivate plugins to identify any that might be causing conflicts, particularly focusing on the 'Razorpay for WooCommerce' and 'Categories Images' plugins, which were found to be problematic. 4. Switch the language URL format settings in WPML to see if this affects the 404 errors. 5. Increase the WordPress memory limit to ensure sufficient resources are available for operations. 6. If issues persist, especially with specific plugins like 'WooCommerce PayPal Payments', deactivate them to check if the problem resolves.
If these steps do not resolve the issues, or if the 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. For further assistance, 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
