Problem: If you're experiencing issues with markers being erased when pasting text into the new Advanced Translation Editor (ATE), or if copying the original text does not apply the markers in the new ATE, here's what we've found: Solution: Our developers have identified that in the new ATE, any pasted text is stripped of markers, although existing markers within the editor are preserved unless they are completely overwritten. This behavior was consistent with our previous editor version. We are planning to address this in a future release after further evaluation.
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: When accessing the Advanced Translation Editor (ATE) to translate pages, it automatically translates them even though it was set not to. Additionally, the version of ATE that opens is random, sometimes the old version and other times the new one. Solution: First, we recommend creating a short screencast to illustrate the issue as it helps in diagnosing the problem more accurately. Next, please temporarily deactivate all plugins except WPML on your dashboard. This step is crucial to ensure that no other plugin is affecting this behavior. We have also recently updated ATE, which might have resolved the issue if it was related to the version updates.
If the problem persists, it might be due to reasons that are no longer relevant or because the situation described doesn't apply 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 none of these solutions work, please open a new support ticket.
Problem: The client noted that in the new version of the software, the labels that were helpful for translators to identify elements they might not need to translate were missing. Solution: We have reinstated these labels in the ATE editor. This update has been implemented and successfully pushed to production. To see these changes, you should reactivate ATE Gen3, which operates independently of the WPML plugin updates.
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. 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: The client is experiencing an issue where the Advanced Translation Editor (ATE) does not load in any browser, including Mozilla Firefox and Chrome, on two different sites. Solution: We recommend clearing the cache on both the server and the browser to resolve the issue.
Please note that the solution provided might be outdated or not applicable to your case. If the issue continues, 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. If you still need assistance, do not hesitate to open a new support ticket in the WPML support forum.
Problem: The client is experiencing an issue where the Advanced Translation Editor (ATE) jumps to the end of the page after saving a block of text during translation. This issue occurs randomly and not for all text blocks. Refreshing the page seems to prevent the issue from reoccurring for that specific page. Solution: 1. We first suggested that the issue might be temporary and asked the client to attempt to replicate it, providing clear steps if possible. 2. We noticed that the REST API appeared to be disabled on the client's site, which is essential for some of WPML's functionality. We recommended checking the REST API dependencies here: https://wpml.org/documentation/support/rest-api-dependencies/ 3. Upon further investigation, we confirmed that the REST API was working on the client's site. 4. We asked the client if the issue persists with the latest WPML version (at the time, 4.6.10) and advised checking for the latest versions in the "My Account -> Downloads" section. We also provided a link to update instructions: http://wpml.org/faq/install-wpml/ and reminded the client to back up their database before updating.
If the solution provided here is not relevant to your case, either because it's outdated or it doesn't apply to your situation, 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 the issue persists, please do not hesitate to open a new support ticket with us.
Problem: The client reported that a string at the bottom of BetterDocs pages was not showing the translation, despite the translation being in place and having worked previously.
Solution: We recommended that the client should first update the WPML plugin and add-ons to the latest version to ensure they have all the latest bug fixes and improvements. We provided instructions for updating and emphasized the importance of backing up the database before proceeding.
If the issue persisted after updating, we suggested the following steps: 1. Go to WPML → String Translation. 2. Enable the option "Look for strings while pages are rendered". 3. Navigate to the page where untranslated strings are displayed. 4. Return to WPML → String Translation and check if the string has been registered. 5. If found, translate the string.
We also provided a link to the documentation for finding and translating strings that do not appear on the String Translation page:
I would like to know if there is an option for translators to add notes for other translators on the ATE directly. This feature would be very useful to improve communication.
Our developers considered it and decided not to implement this feature.:
