Feature request

Problem:
The client is using the Advanced Translation Editor (ATE) in WPML and has content that does not require translation. Despite setting the translation priority to 'Not needed' for specific pages, these pages still appear as 'not translated' in the translation management dashboard. The client is seeking ways to automatically exclude such items from translation processes, especially when using the 'Translate Everything Automatically' feature.
Solution:
Currently, WPML does not support the automatic exclusion of items marked as 'Not needed' from the translation process when using the 'Translate Everything Automatically' feature. Our team has reviewed the request to deselect some content from the translation editor, but as of now, this is not a popular request, and there are no plans to implement it in the near future. We recommend manually managing items that do not need translation and not including them in the 'Translate Everything Automatically' setup.

If this solution does not fully address your issue or if it becomes 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. Should you need further assistance, please do not hesitate to open a new support ticket at WPML support forum.

Problem:
Der Kunde kann nach einem Update auf ein Block-Theme das Menü auf der Subseite nicht mehr auswählen und die Flagge neben dem Menü nicht mehr anzeigen. Zuvor konnte er spezifische Sprachen im Menü ausblenden, was nun nicht mehr möglich ist.
Solution:
Wir haben erklärt, dass die Menüsprachwechsler-Option für klassische Menüs unter 'Design > Menüs' gedacht ist und bei modernen Block-Themes nicht verfügbar ist. Für Block-Themes sollte die Übersetzung der Menüs unter 'WPML > Translation Management > Dashboard' erfolgen und der Sprachwechsler über den 'WPML Sprachwechsler Block' im Site Editor hinzugefügt werden. Um komplette Sprachen auszublenden, kann man die Einstellungen unter https://wpml.org/de/documentation-3/ratgeber-zum-loslegen/einstellung-der-sprachen/sprachen-auf-dem-frontend-ausblenden/ anpassen. Da die Option zum Ausblenden der aktuellen Sprache im neuen WPML Language Switcher Block fehlt, haben wir einen Feature-Request dafür erstellt.

Falls diese Lösung für Ihr Problem irrelevant erscheint, weil sie veraltet ist oder nicht auf Ihren Fall zutrifft, empfehlen wir Ihnen, ein neues Support-Ticket zu eröffnen. Wir empfehlen auch, die Seite mit bekannten Problemen unter 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.

Problem:
The client encountered an issue where square brackets in text were being misinterpreted as shortcodes by the WPML translation editor. Additionally, the client inquired about features in the Advanced Translation Editor (ATE) that were available in the old editor, specifically the ability to show only fields that need translation and to copy the original text for all untranslated fields.
Solution:
For the square brackets issue, we recommended escaping the brackets using their Unicode equivalents ([ with [ and ] with ]) or trying double brackets, although the latter did not resolve the display issue as desired. Another suggested workaround involved using HTML and CSS to visually represent the brackets without them being interpreted as shortcodes:

<span class="square_braces">The hotel</span>

and the accompanying CSS:

.square_braces::before { content: "["; }<br />.square_braces::after { content: "]"; }<br />html[lang="en-US"] .square_braces::after, html[lang="en-US"] .square_braces::before { display: none; }

Regarding the ATE features, the client's requests were escalated as feature requests to our developers. An update was provided that the newest ATE Gen3 includes a new UI and shortcuts, such as Ctrl + Enter, which allows navigating to the next untranslated field without scrolling.

Please note that the solutions provided might be outdated or not applicable to your specific case. If these solutions do not resolve your issue, 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 do not hesitate to open a new support ticket at WPML support forum.