Problem: The client is experiencing unexpected deductions of translation credits when opening a page with the Advanced Translation Editor (ATE), despite the translation memory being up to date and the settings adjusted to prevent automatic translations.
Solution: We reviewed the client's WPML settings and confirmed that the translation mode was set to "Translate What You Choose", which should prevent automatic translations unless initiated by the user. We could not identify any issues with the translation jobs from the reports provided.
Additionally, we suggested switching between translation modes and adjusting the translation settings as already done by the client.
If you continue to experience the issue of WPML credits being deducted when they shouldn’t be, we need to find a way to replicate this problem on your website so we can address it appropriately.
Please note that this solution might be outdated or not applicable to your specific case. If you continue to face issues, 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 unable to duplicate a page in WordPress because the translation already exists. They are also unsure how to reconnect the FAQ to the Advanced Translation Editor (ATE) after it has been disconnected. Solution: If you're experiencing issues with duplicating a page that already has a translation and reconnecting it to the ATE, we recommend the following steps: 1. Understand that the WPML Translation Editor and the WordPress Editor are separate features. Switching between these requires you to recreate the translation, although some parts might be saved in the Translation Memory when using ATE. 2. To switch between the 'WP Editor' and 'WPML Translation Editor', open the WordPress page for the post and toggle between these options in the language box located in the right column. It's important to note that WPML uses Translation Memory, and segments are only charged for automatic translation the first time they are translated.
If this solution does not apply to your case, or if it seems outdated, please check the related known issues and verify the version of the permanent fix. Ensure you have installed the latest versions of themes and plugins. If issues persist, we highly recommend opening a new support ticket for personalized assistance. Visit our support forum for further help.
Problem: You are using WPML to manage translations on your site and want to save different HTML code for each language. However, when you edit the HTML code for the English version, it is perceived as a change that needs to be translated in the Advanced Translation Editor, causing the new HTML code for other languages to get lost. Solution: We recommend manually adding your different HTML code for each language. You can do this by using different translation editors for different pages, as detailed in our documentation: Using Different Translation Editors for Different Pages. Alternatively, consider adding your HTML code outside of the translation-sensitive areas, such as in the
functions.php
file or through Elementor's custom code feature, and then call it on the respective pages. This approach helps avoid the automatic translation adjustments by WPML when you modify the HTML in the default language.
Please note that this solution might be outdated or not applicable to your specific case. If these steps do not resolve your issue, 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 was trying to update the WPML plugin to version 4.6.13 on a live site but encountered issues due to an inactive license and was unsure how to proceed with the update. Solution: We recommended a manual update procedure. First, we advised the client to create a full backup of the website. Then, deactivate and delete the current WPML plugins. The next step is to manually download the latest versions from the WPML account downloads page (https://wpml.org/account/downloads/). After downloading, navigate to the website's backend, go to Plugins > Add New > Upload Plugin, and then upload, install, and activate each plugin one by one. If the WPML plugin was previously registered, it might have been possible to update directly from the Plugins > Add New > Commercial tab by checking for updates.
If this solution does not resolve the issue or seems outdated, or if it does not apply to your case, we highly recommend checking the 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 for further assistance.
