Problem: The client copied their domain to a new one and changed the default language from German to English. They inquired whether deleting the German language, which was once the main/default language, could cause issues with graphics or other elements and how to ensure it does not appear in Google listings. Solution: We recommend not deleting a language that was once set as default due to potential content defaults in that language. Instead, you can hide this language from the frontend. To do this, navigate to the WPML → Languages page, go to the Hide languages section, select the languages you want to hide, and click the Save button. For more detailed instructions, visit hiding languages on the front-end.
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 further assistance is needed, please open a new support ticket at WPML support forum.
Problem: The client wants to copy the default media graphics to all other languages on their site. Solution: We recommend using the Media Translation options available in WPML -> Settings. Specifically, you can use: - Translate existing media in all languages - Duplicate existing media for translated content However, please note that this may not automatically fill in image data such as descriptions, alt texts, or custom fields for images that lack this data but are already present in other language media libraries.
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 further assistance is needed, please open a new support ticket at WPML support forum.
Problem: Der Kunde versucht, einige Strings aus der
functions.php
zu übersetzen. Es funktioniert für die Sprachen nl und de, aber nicht für en, fr, da, it. Die Strings sind korrekt hinterlegt, und die Einstellungen in Elementor für das Formular sind zwischen den Sprachen ES und EN identisch. Solution: 1) Die Strings direkt in ein Template (z.B. header.php) als
getText()
Aufruf mit
echo
einfügen und prüfen, ob diese bei einem Sprachwechsel im Frontend korrekt ausgegeben werden. Dies hilft festzustellen, ob die String-Ausgabe generell funktioniert. 2) Das Problem isolieren, indem der Code zuerst in ein neues Hello Elementor Child Theme eingefügt wird. Funktioniert es damit? 3) Das Problem weiter isolieren, indem ein Standard-Theme verwendet wird, alle nicht benötigten Plugins deaktiviert werden und der Versand eines übersetzten Formulars ohne Elementor getestet wird. 4) Überprüfen, ob zusätzliche externe Logik (Workflows) von Brevo geladen wird, die möglicherweise nicht für alle Sprachen identisch ist.
Bitte beachten Sie, dass die Lösung möglicherweise irrelevant ist, entweder weil sie veraltet ist oder nicht auf Ihren Fall zutrifft. Wir empfehlen Ihnen, ein neues Support-Ticket zu öffnen, wenn dies der Fall ist. Überprüfen Sie außerdem verwandte bekannte Probleme unter https://wpml.org/known-issues/, bestätigen Sie die Version der dauerhaften Lösung und stellen Sie sicher, dass Sie die neuesten Versionen von Themes und Plugins installiert haben. Für weitere Unterstützung empfehlen wir Ihnen, unser Support-Forum zu besuchen: WPML Support-Forum.
Problem: The client is experiencing an issue where strings in the functions.php file are not displaying in the correct language despite using the correct WPML string setup. The issue occurs when using a shortcode that includes translated strings. Solution: If you're experiencing this issue, ensure you are using the gettext
__()
function correctly. First, scan your theme for new strings in WPML under Theme and plugins localization. You can find this option at Theme and plugins localization. After scanning, translate the strings accordingly. If the gettext call is set up correctly and you still face issues, you might want to use the
wpml_translate_single_string
hook to retrieve string translations directly. More details on this hook can be found here: wpml_translate_single_string. For additional guidance on enabling text translation for themes not compatible with WPML, refer to this documentation.
If this solution does not resolve your issue or seems irrelevant due to being outdated or not applicable to your case, we recommend opening a new support ticket. We also highly suggest checking related known issues at 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, please visit our support forum at WPML support forum.
Problem:
The client wants to retrieve the translated string from WPML >> String Translation page using the wpml_translate_single_string hook but it was returning the default language string instead of the translation.
Solution:
First, registering the string using the wpml_register_single_string hook solved the issue.
