Problem: The client is experiencing issues with WPML where the translation process used almost all their credits without translating as expected. Despite the system indicating only a few credits would be used, it depleted nearly all available credits. Additionally, the client noticed that some navigation items and products were not translated, even though credits were charged. Solution: We cannot offer refunds for translation credits once they are used, as detailed in our documentation: https://wpml.org/faq/can-i-get-a-refund-for-automatic-translation-credits/. To understand where and how many credits were used, the client can view their Automatic Translation Usage Report by navigating to WPML > Translation Management > Tools > Payment and Settings > Automatic Translation Usage Reports. For guidance, refer to: https://wpml.org/documentation/automatic-translation/automatic-translation-invoices/#where-to-find-your-past-pay-as-you-go-invoices. To avoid unintended use of credits, we recommend switching from "Translate everything automatically" to "Translate what you choose" in WPML > Settings, allowing more control over what content is submitted for translation. For issues with untranslated navigation items, the client needs to click the eye icon to accept and publish the translations. If problems persist, we suggest opening a new ticket for specific issues. For estimating the number of credits needed for translating all products, refer to this existing ticket: https://wpml.org/forums/topic/split-how-can-i-estimate-the-number-of-credits-i-need-to-translate-my-entire-website/.
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 further assistance is needed, please open a new support ticket at WPML support forum.
Problem: The client is trying to translate a page using the WPML interface, but encounters issues where the interface shows incomplete translation percentages despite all segments appearing translated. Additionally, after saving translations, they revert to untranslated status, and the English version of the page is not visible on the frontend. Solution: We recommend the following steps to address the translation issues: 1. Ensure that all links within the content are correctly translated and updated. You can find guidance on translating links using the Advanced Translation Editor (ATE) here: Translating Links with Advanced Translation Editor. 2. If the problem persists, try switching to the previous version of ATE: - Open the page in ATE. - Click on the icon in the top right corner. - Select the option to activate the previous version of ATE. - Save the changes and fix the translation. - Save the translation, update it in ATE, and then switch back to the latest version of ATE. - Verify if the issue is resolved.
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 the problem persists, please open a new support ticket.
Problem: The client is experiencing an issue where changes made to content in one language are incorrectly reflecting in another language, despite using Elementor and WPML. This synchronization error prevents maintaining distinct content for different languages. Solution: 1. Ensure that all WPML plugins are updated to the latest version. Instructions for updating can be found here: http://wpml.org/faq/install-wpml/ 2. After updating, apply the workaround described on the WPML errata page: https://wpml.org/errata/wordpress-6-7-mo-files-not-loaded-and-leading-to-missing-translations-on-front-end/ 3. Edit the content in the original language and use the 'WordPress Editor' to ensure changes only apply to the intended language. This can be done by selecting the scope of the changes to apply only to that particular post or page. 4. Make a small change in the original language, save these changes, and then update the translation.
If the solution provided here 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 problems persist, please open a new support ticket at WPML support forum.
Problem: You are using WPML's String Translation to translate a field in the Theme options found in Customizer. While other fields translate correctly and show on the front-end, one specific field does not appear after translation. Solution: First, ensure that your theme supports the translation of this specific field. If the issue persists, follow these steps: 1. When adding a string from the admin text, select to export XML configuration. 2. Add the exported XML to WPML > Settings > Custom XML Configuration. This method helps WPML to manually detect and register the strings for translation, ensuring they display correctly on the front-end.
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 further assistance is needed, please open a new support ticket at WPML support forum.
Problem: You are trying to automatically translate the header into Japanese on your website, but the translation is not successful. It remains in the 'Prepare for Translation' stage, and the header disappears from the Japanese page. Solution: We have reviewed your headers and found that none of them have been translated yet. To address this, we initiated a translation for Dutch as a test, but noticed that the headers were not set to Draft as expected. We recommend watching a video we recorded that explains how this process should work when a new translation is still in the Draft stage. You can view the video here: View the video here.
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: If you're experiencing issues with incorrect canonical URLs for secondary WooCommerce categories in a multilingual setup, you might find that the canonical URL does not point to the intended language version of the category. Solution: We recommend enabling the option
Adjust IDs for multilingual functionality
found under WPML -> Languages -> Make themes work multilingual. This adjustment has proven effective in ensuring that the canonical URLs correctly reflect the language-specific category pages.
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. Should these steps not resolve your issue, please do not hesitate to open a new support ticket at WPML support forum for further assistance.
Problem: You have set up a staging site and are translating the site to Arabic using WPML. You are experiencing an issue where the translation progress is stuck at 93%, and you are unable to save the pages. You are unsure what content remains untranslated. Solution: First, ensure that your WPML String Translation plugin is updated to version 3.2.15. Next, navigate to the Advanced Translation Editor for the page you are working on. Click the gear/settings icon located in the top right section and enable the option for the previous ATE version. After enabling, submit the feedback to load the settings. Check for any empty translation boxes that might not have been translated. If the issue persists, we recommend that you provide us with the URL/User/Pass of your WordPress dashboard. Ensure that you have a backup of your website before providing this information, as it is crucial for restoring your site if necessary. Set your next reply as private when sending sensitive information.
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 this does not resolve your issue, please open a new support ticket.
Problem: The client is using WPML for their website and has questions regarding the costs of translating sentences with variable attributes, the automation of translations for new content, and whether numerical values are excluded from translation costs. Solution: 1. WPML utilizes a translation memory, which means you won't be charged for sentences that are identical to those already translated. For more details, visit how WPML keeps track of your translations. 2. If you use the "Translate everything automatically" option in WPML > Settings, WPML will translate any new content when changes occur. However, this might consume many credits if there's a lot of new or final content. Alternatively, the "Translate what you choose" setting allows more control, letting you select specific content for translation. 3. For sentences with variable attributes like [Scale], each unique sentence is considered new and will be charged unless it matches an existing entry in the translation memory. Sentences need to be 100% identical to be reused from memory without charge. 4. WPML does not translate or charge for numerical values like years or dimensions, as these are recognized as non-translatable and reused from the translation memory.
If this solution does not fully address your issue or seems outdated, we 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. If further assistance is needed, please open a new support ticket at WPML support forum.
Problem: After reinstalling the WPML plugin and translating a site built with Elementor from German to English, all English pages were missing. Attempts to follow forum advice and roll back WordPress versions did not resolve the issue. Solution: We discovered that the issue was not related to WPML but was due to the English pages using a specific Elementor template ("Elementor Single Page #5140") that was set to display no content. We changed the status of this template to DRAFT, so it is no longer applied to the pages, and this resolved the problem.
If this solution does not apply to your case, or if it seems outdated, we 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. If issues persist, please open a new support ticket.
