Known issue

Problem:
You are experiencing an issue where WPML is overriding the Yoast meta title and meta description for categories after saving a new category.
Solution:
This is a known issue, detailed here: https://wpml.org/errata/wordpress-seo-issues-translating-yoast-seo-term-meta/.
Previously, SEO titles and meta descriptions had to be manually added in the category editing screen. However, starting from WPML SEO 2.2.0, these can be translated via WPML → Translation Dashboard as String Packages, which also supports automatic translation. Since WPML SEO 2.2.5, manually added translations may not appear on the frontend because WPML now handles these translations through the Translation Dashboard.
Options to resolve this include:
1. Rolling back to WPML SEO 2.1.1 to continue using manual translations.
2. Using the WPML → Translation Dashboard (String Packages) for translations, which is the recommended method moving forward.

If this solution does not apply to your case, or if it 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 issues persist, please open a new support ticket at WPML support forum.

Problem:
Die CSS-Styles von Greenshift-Elementen werden auf der englischen (übersetzten) Seite Ihrer Website nicht beachtet, was zu einer falschen Formatierung führt. Dieses Problem tritt auf, wenn Seiten manuell über WPML verbunden und nicht automatisch übersetzt werden. Das Problem verschwindet, wenn die Verknüpfung der Übersetzung in WPML gelöst wird.
Solution:
Das Problem mit der Synchronisation von Greenshift-CSS ist bekannt. Wir arbeiten mit dem Hersteller zusammen, um eine Lösung zu finden. Eine vorübergehende Lösung besteht darin, das CSS manuell im WordPress-Editor für die Übersetzung festzulegen. Alternativ kann das CSS korrekt kopiert werden, wenn Sie die Vorlage zuerst duplizieren und dann übersetzen. Weitere Informationen finden Sie unter https://wpml.org/pt-br/errata/greenshift-css-synchronization-issues/.
Falls diese Lösung für Sie nicht relevant ist oder veraltet erscheint, empfehlen wir, einen neuen 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/support-in-german/.

Problem:
The client is experiencing an issue where the meta title for a category page in French appears in English, despite being correctly entered in the SEO title settings for that product category page.
Solution:
1. In the latest versions of our plugins, you can translate Yoast SEO Term Meta at WPML > Translation Dashboard > Yoast SEO.
2. Create a job for Term Meta, assign it to yourself, and access the job at WPML > Translations. These translations will be automatically saved at WPML > String Translation inside the domain yoast-seo-term-meta.
3. This issue is a known limitation within WPML SEO. Please review the following errata: https://wpml.org/errata/wordpress-seo-issues-translating-yoast-seo-term-meta/
4. Alternatively, you can roll back to WPML SEO 2.1.1 to continue using manual translations until the issue is resolved in a future update.

If this solution does not apply to your case, or if it 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 issue persists, please open a new support ticket at WPML support forum.

Problem:
The client reported critical issues with WPML Multilingual CMS and WPML String Translation plugins. They were installed and active, but the client encountered errors indicating missing database tables ('wp_icl_strings' doesn't exist) and restricted access to WPML settings and support pages, leading to 404 errors on the site.
Solution:
We recommended resetting WPML and configuring it again from scratch. Here are the steps we advised the client to follow:
1. Navigate to WPML → Support and click the Troubleshooting link.
2. In the Reset section, select the checkbox “I am about to reset all translation and language data”.
3. Click Reset and deactivate WPML.
It is crucial to back up the database before making any changes. For more details, visit this documentation.

If this solution does not resolve your issue, or if it seems outdated or irrelevant to your case, please open a new support ticket. 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. For further assistance, visit our support forum at https://wpml.org/forums/forum/english-support/.

Problem:
When attempting to send a page for translation, the message indicates that some content includes fields that are encoded and thus removed from the translation job. Additionally, the menu for this section does not appear at the top.
Solution:
If you're experiencing this issue, we recommend following the workaround provided by the WPML support team. Please visit the following link for detailed instructions: WPML cannot send base64 encoded content to translation.

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 for further assistance.