Problem: If you're experiencing issues where your Translation Dashboard continuously reloads after enabling the WPML Advanced Editor, it might be due to a Content Security Policy (CSP) blocking a necessary WPML script. This blockage prevents the dashboard from loading properly. Solution: We recommend checking where your CSP is configured, which could be in Cloudflare, a security plugin, or your server settings. You need to allow
https://ams.wpml.org
under script-src and, ideally, also under connect-src in your CSP settings. This adjustment should resolve the issue with the dashboard.
If this solution does not apply to your case, or if it 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 with us for further assistance. You can do so at WPML support forum.
Problem: The client reported an issue where deleted glossary terms were still being "cached" and applied in translations, despite being removed from the glossary. Solution: We advised the client to ensure that the content was not coming from a template but directly from the product content itself. After confirming that the section was indeed added via a template, the client was able to edit the relevant file and retranslate the string. This resolved the issue, and the glossary terms were applied correctly after retranslation. If you're experiencing similar issues, we recommend checking if the content is coming from a template and ensuring that all strings are sent for translation through the Translation Dashboard.
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 do not hesitate to open a new support ticket at WPML support forum.
Problem: The client reported multiple PHP warnings and a WordPress database error related to the WPML String Translation plugin and database operations. Solution: We identified that the issues are associated with a known bug in WPML version 4.9. We recommend reverting to the previous stable versions of WPML and WPML String Translation until the issue is resolved in the upcoming 4.9.1 release. We have implemented this solution on the staging site, and it appears to resolve the errors. Please verify on your end and contact us if the problem persists or if new issues arise.
Please note that this solution might become outdated or may not apply to your specific situation. 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 the issue persists, please open a new support ticket.
Problem: The client was unable to use the Advanced Translation Editor for a page that was originally translated using the Classic Translation Editor. Solution: We reviewed the client's settings and enabled the option in WPML → Settings:
"Use also for old translations created with the classic editor"
. This allowed the page to open correctly in the Advanced Translation Editor and the translation to load properly. We asked the client to clarify any specific issues they were still facing.
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 problems persist, please open a new support ticket.
Problem: If you're experiencing issues with Elementor translations where links are not displayed correctly in some language versions, despite being set up correctly in the ATE editor, you're not alone. Solution: We recommend re-sending the content to automatic translation. This should resolve the issue with the incorrect display of links in translations. Here's an example of how you might add the problematic paragraph text in English before translation to German using PTC engine:
<p>As soon as your supply starts to dwindle, you can start a new cultivation project. For example, make new <span style="text-decoration: underline;"><strong><a href="https://acidshroomz.com/how-to-make-rye-grain-spawn/">mushroom spawn</a></strong></span>, or directly grow a new batch of mushrooms in a <span style="text-decoration: underline;"><strong><a href="https://acidshroomz.com/grow-magic-mushrooms-monotub/">monotub</a></strong></span> if you already have spawn available. This way, you are always well-stocked.</p>
Please note that this solution might be irrelevant if it's 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: How to disable automatic translations inside WPML? Solution: To disable automatic translation: 1) Turn off "Translate Everything automatically" in WPML > Translation Dashboard. 2) In the Advanced Translation Editor's settings, disable "Translate all content automatically when the editor is opened". 3) Disable all automatic translation engines in WPML > Translation Tools. 4) Ensure no admin or translator is enabled for automatic translation in WPML > Translation Tools. If this solution does not apply to your case, or if it seems outdated, we highly recommend checking related 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.
Problem: The client translated over 20 pages automatically with a review process, but seven of these pages could not be reviewed or published. When attempting to preview the translations by clicking the eye icon, the client was redirected to the Advanced Translation Editor instead of the frontend. Additionally, the translation queue page was loading but then displayed nothing, and the main translation management page showed no review buttons. Solution: We resolved a recent incident that caused downtime in the Advanced Translation Editor (ATE), which has now recovered. For the specific case of the product '550 Schokoladenmasse 55/45/30' and similar issues, we recommend the following steps: 1. Open the product in edit mode in the original language. 2. Use the language switcher to open the English version. 3. Choose to edit with ATE. 4. After updating and saving the content via the translation workflow, use the preview link to preview the translation and then publish it.
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.
Problema: Le pagine non vengono visualizzate come tradotte nonostante lo stato di traduzione sia 'Completato'. Potrebbe esserci un conflitto con un plugin o un tema. Soluzione: Se stai riscontrando questo problema, ti consigliamo di seguire questi passaggi: 1. Vai su WPML → Supporto → Risoluzione dei problemi e esegui le seguenti operazioni: - Remove ghost entries from the translation tables - Fix element_type collation - Set language information - Fix WPML tables collation - Assign translation status to duplicated content - Fix terms count - Fix post type assignment - Cleanup and optimize string tables 2. Invia nuovamente la pagina in traduzione. Questo processo non consumerà ulteriori crediti per le pagine già tradotte.
Se la soluzione proposta non risolve il problema o se sembra non essere più attuale, ti invitiamo a visitare la pagina dei problemi noti e a verificare che tu abbia installato le versioni più recenti dei temi e dei plugin. Se il problema persiste, ti consigliamo di aprire un nuovo ticket di supporto sul forum di supporto WPML.
