Problem: Der Kunde berichtet über Fehler im neuen Übersetzungseditor (Version 4.8.6), wo deutsche Übersetzungen nicht angezeigt werden und stattdessen das bulgarische Original erscheint. Zudem fehlen die farblichen Markierungen pro Wort, die früher zur Unterscheidung von Formatierungen wie Links, Fett, Kursiv usw. dienten. Solution: Wir arbeiten an einer dauerhaften Lösung für das Problem. In der Zwischenzeit empfehlen wir, alle Beiträge erneut automatisch vom Bulgarischen ins Deutsche zu übersetzen. Wir haben dem Website-Konto des Kunden 15.000 Übersetzungs-Credits gutgeschrieben, um alle Beiträge zu übersetzen und das Problem zu beheben. Dazu sollten Sie zu WPML > Translation Dashboard gehen, Bulgarisch als Quellsprache wählen, alle Beiträge markieren und zur automatischen Übersetzung senden.
Falls diese Lösung veraltet ist oder nicht auf Ihr Problem zutrifft, empfehlen wir Ihnen, ein neues Support-Ticket zu öffnen. Wir empfehlen auch, die Seite mit bekannten Problemen (https://wpml.org/known-issues/) 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 unter https://wpml.org/de/forums/forum/deutsch-support/.
Problem: The client reported an issue where the 'Read more' button on the post page with news articles does not translate when using a filter after switching the website language. Solution: We recommend the following steps to address the issue: 1) Navigate to 'Templates > Saved templates > All > German'. 2) Edit the Loop template in the WP editor and unlink it from the English version by selecting 'This is a translation of = NONE' and save. 3) Independently edit the template in the Elementor editor, ensuring to add the correct 'Read more' text in GERMAN. 4) Return to 'Templates > Saved templates > All > German'. 5) Edit the blog archive template in the Elementor editor. 6) Select the German Loop template in the Loop grid widget and save. Additionally, the issue was resolved in WPML version 4.9. We recommend updating to this version if you haven't already. You can download it from the 'Commercial' tab at 'Plugins > Add Plugin' or directly from https://wpml.org/account/downloads/.
If this solution does not apply to your case, or if it seems outdated, please check related known issues at https://wpml.org/known-issues/, verify the version of the permanent fix, and confirm that you have installed the latest versions of themes and plugins. If issues persist, we highly recommend opening a new support ticket for further assistance.
Problem: You are unable to proceed past Step 4 (AI Translation) in the WPML setup (version 4.8.6) across multiple projects. Despite deactivating all plugins, switching to a default theme, resetting the database, and creating a fresh project with only WPML installed, the setup gets stuck. The console displays an error in the AITranslation component: 'Failed to get parameters to initialize ATE dashboard.' Solution: We recommend trying to install the latest version of WPML. You can download it from here. If this does not resolve the issue, please try updating to version 4.9, which you can also find at here.
Please note that this solution might be irrelevant if it's 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 the problem persists, please open a new support ticket at WPML support forum.
Problem: Se stai riscontrando un errore critico quando clicchi su alcuni post, sia nativi che CPT, e hai attivato il debug, potresti vedere errori legati a WPML che indicano una possibile ricorsione infinita. Solution: Per aiutarci a identificare e risolvere il problema, ti chiediamo di fornirci dettagli specifici sull'azione che stavi eseguendo quando si è verificato l'errore. Ad esempio, se l'errore si verifica durante il salvataggio, l'aggiornamento, la traduzione di una pagina o dopo aver modificato qualche impostazione. Con queste informazioni, possiamo riprodurre il problema nel nostro ambiente e, se necessario, escalare la situazione al nostro team di sviluppatori per un'analisi più approfondita.
La soluzione potrebbe non essere più rilevante a causa di aggiornamenti o modifiche non applicabili al tuo caso. Ti consigliamo di verificare i problemi noti, controllare la versione della correzione permanente e assicurarti di avere installato le ultime versioni dei temi e dei plugin. Se il problema persiste, ti invitiamo a aprire un nuovo ticket di supporto.
Problem: The client is experiencing issues with locked fields in WPML and has concerns about the translation of the footer, which does not display correctly across different language versions of the site. Solution: We clarified that the locked fields can be unlocked simply by clicking on the 'lock' icon. Regarding the footer, it appears that the client had previously attempted to fix the issue by deleting the translated footer template directly from the database. However, this did not resolve the problem as the footer still does not appear correctly. We suggested that the footer's translation issue might be due to the limitations described in the WPML errata for the Pro theme, where layout texts are not translatable via the WPML Translation Editor (https://wpml.org/errata/pro-theme-layout-texts-not-translatable-via-wpml-translation-editor/). The client can either manually translate the template or apply custom code to make it compatible with String Translation. We asked the client to confirm if they intend to use String Translation for the footer in the same way as the “Object (CPT) – Single View” template.
Please note that this solution might be outdated or not applicable to your specific case. We highly recommend checking related known issues (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.
