Problem: Der Kunde konnte eine Übersetzung auf seiner Website nicht öffnen und erhielt Fehlermeldungen. Zudem gab es Probleme mit der Übersetzung von Inhalten, die mit dem Bricks Builder und ACF erstellt wurden. Solution: Wir empfehlen, den originalen Inhalt im Bricks Builder zu bearbeiten und erneut zu speichern, dann die Übersetzung nochmals durchzuführen.
Falls diese Lösungen nicht relevant sind oder das Problem weiterhin besteht, empfehlen wir, ein neues Support-Ticket zu eröffnen. Überprüfen Sie auch die bekannten Probleme, bestätigen Sie die Version des dauerhaften Fixes und stellen Sie sicher, dass Sie die neuesten Versionen von Themes und Plugins installiert haben.
The client was experiencing issues with automatic translations getting stuck in the queue after moving their webshop to a new host. Despite trying several troubleshooting steps such as deregistering and registering the site with a new key, and enabling auto translation, the problem persisted.
Solution:
We discovered that the issue was due to a conflict between the IDs of translation jobs and the site ID on our ATE server. Our developers resolved this conflict, ensuring that the automatic translation functioned correctly.
If you're experiencing similar issues, we recommend checking for potential ID conflicts or reaching out for support.
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 at WPML support forum.
Problem: The client is trying to use WPML's AI translation feature but finds the available language options limited. Additionally, they are experiencing an issue with an unwanted globe icon appearing next to the menu language switcher in the Buddyboss platform. Solution: For the AI translation feature, WPML AI is currently available in a limited number of languages, and more are being added over time. Clients can check the list of available languages here. If the current languages do not meet the client's needs, it is recommended to use other translation engines like DeepL. Instructions for changing translation engines can be found here. For the issue with the Buddyboss platform, the client should try the workaround provided in the WPML errata here. If that does not resolve the issue, a CSS solution is available here.
If these solutions do not resolve your issues or if they seem outdated, we recommend opening a new support ticket. We also highly recommend checking related known issues here, 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 here.
Problem: You are trying to add new translations to the header, footer, and contact form using WPML > Translations, but the page does not stop loading, and you encounter error messages stating 'Something went wrong, please try again' and 'Unable to retrieve job details'. Solution: We recommend canceling the problematic translation job in WPML under Translation Management → Translation Jobs. After canceling, resend the job from the Translation Management. Once done, you should be able to access and complete the translation from WPML → Translations.
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 the problem persists, please open a new support ticket at WPML support forum for further assistance.
