Problem: If you're experiencing issues where superscripts in your original pages are not being added to translations in WPML, and instead, a space appears, we have a solution that might help. Solution: We recommend following these steps to address the superscript issue: 1. Navigate to your Dashboard > Pages. 2. Open the edit screen of the original page. Look for a pencil/circle/gear icon in the sidebar options under the "Languages" section. 3. Make a minor change, such as adding an extra blank space at the end of a sentence or paragraph. 4. Save your changes. 5. A circular arrow should appear beside the links for the second languages, indicating that an update is required. 6. Edit the translation again and ensure it is saved up to 100% translated.
Please note that this solution might become irrelevant due to updates or may not apply to your specific case. If the issue 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 necessary, do not hesitate to open a new support ticket at WPML support forum for further assistance.
Problem: You are experiencing an issue where random pages on your WordPress site open with the WordPress editor instead of the Advanced Translation Editor (ATE) despite correct settings. Solution: 1. Open the page (in the default language) in your WordPress editor. 2. In the right-hand sidebar, find the Language section. 3. Check which translation editor is selected. If it says 'WordPress Editor', click to change it to WPML editor. 4. When prompted, choose whether to use the WPML (Advanced) Translation Editor for just this page or for all pages of this type. Pick the option that fits your workflow. 5. Save or update the page. After updating, go back to WPML → Pages (or the relevant translation dashboard) and click the plus icon for translation. The ATE should now open as expected. To prevent this from happening on other pages, you can set your preferred editor for all content types in WPML → Settings → Translation Editor. This ensures ATE is used by default for future translations. If you still see some pages opening the WordPress editor after these steps, double-check each affected page's Language settings as above.
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: 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.
