ATE

Problema:
Il cliente ha riscontrato un problema con il salvataggio a causa di un errore su alcuni campi di testo normali, accompagnato da un messaggio di errore.
Soluzione:
Abbiamo identificato che il problema era dovuto a un malfunzionamento temporaneo del servizio di traduzione (ATE). Dopo aver verificato che il servizio è tornato operativo, consigliamo al cliente di riprovare a salvare la traduzione. Se il problema persiste o la soluzione proposta risulta non più attuale o non applicabile al tuo caso, ti invitiamo a visitare la pagina dei problemi noti per verificare la versione della correzione permanente e confermare che hai installato le ultime versioni dei temi e dei plugin. In caso di ulteriori difficoltà, ti raccomandiamo di aprire un nuovo ticket di supporto.

Problem:
Wenn Sie versuchen, den Translation Editor aufzurufen, erhalten Sie Fehlermeldungen wie 'kann nicht aufgerufen werden' oder 'This website is under heavy load'. Im Fehlerprotokoll erscheint 'ATE Server Communication - Service Unavailable'.
Solution:
Das Problem wurde durch einen Systemausfall verursacht, der eine kurzfristige Downtime zur Folge hatte. Dieses Problem ist bereits behoben, und das System sollte nun wieder normal funktionieren. Sollten bei Ihnen noch Jobs hängen oder nicht korrekt durchgelaufen sein, empfehlen wir Ihnen, den Job einfach erneut einzusenden.

Falls diese Lösung für Sie nicht relevant sein sollte, weil sie veraltet ist oder nicht auf Ihren Fall zutrifft, empfehlen wir Ihnen, ein neues Support-Ticket zu öffnen. Wir empfehlen Ihnen auch, die Seite mit den bekannten Problemen zu überprüfen, die Version der dauerhaften Lösung zu verifizieren und zu bestätigen, dass Sie die neuesten Versionen von Themes und Plugins installiert haben. Für weitere Unterstützung besuchen Sie bitte unser Support-Forum.

Problem:
The client was unable to use the Advanced Translation Editor (ATE) as it was not loading and displayed an error 503.
Solution:
The issue resolved itself without any intervention from the client. If you're experiencing this issue, we recommend waiting a short period to see if it resolves on its own. However, if the problem persists, please check our related known issues and ensure you have the latest versions of themes and plugins installed. If none of these steps work, we highly recommend opening a new support ticket.

This solution might be irrelevant if it's outdated or not applicable to your case. If you need further assistance, please visit our support forum.

Problem:
After moving the site from staging to live, the client is unable to access the Advanced Translation Editor (ATE). They encounter error messages indicating an inability to retrieve job details and a message about the website being under heavy load, despite server statistics showing otherwise.
Solution:
We have identified a temporary issue on our servers affecting the ATE access. Our technical team is actively working to resolve this. We recommend checking back in a few hours as the issue is expected to be resolved soon.

Please note that this solution might be outdated or not applicable to your 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 needed, please open a new support ticket at WPML support forum for further assistance.

Problem:
The client is trying to return some translation credits to their main account but receives an error message indicating that credits cannot be withdrawn to wpml.org.
Solution:
We explained that when a site key is created, we provide 2,000 free credits per site. These credits are assigned specifically to that site and are not transferable between sites or back to the main account. Therefore, it is not possible to move them back to the main account.

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. If further assistance is needed, please open a new support ticket at WPML support forum.

Problem:
The client reported issues with their multilingual website where the homepage and other pages were not translating properly. Despite updates in the backend, the frontend displayed outdated layouts, structures, and media across different languages. The WPML Menu Sync settings were advised to remain off due to conflicts with a custom mega menu.
Solution:
1. We instructed the client to resave the English versions of the affected pages.
2. We guided them through checking WPML → Settings to ensure proper translation settings for post types and custom fields.
3. We advised using WPML → Media Translation to synchronize or update images and media for each language.
4. We directed the client to resend affected pages via WPML → Translation Dashboard and complete translations again in the WPML Translation Editor.
5. We emphasized the importance of clearing all site, server, and browser caches after updates.
6. We avoided suggestions involving WP Menu Sync as per the client's prior instructions.
7. If issues persisted, we recommended manually inspecting Elementor templates for affected pages in each language, ensuring template assignments and media selections matched the current English layout.

If this solution does not resolve your issue or 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 problems persist, please open a new support ticket at WPML support forum.