Problem: The client activated WPML on their site, purchased credits, and started automatic translation, but only the menus and not the text itself appeared on the page. Despite the translations showing as 100% complete in the 'Edit translation' section, they were not visible on the website. Solution: We identified that the YooTheme Builder is currently not compatible with WPML. We recommend using the WordPress Editor to translate content created with YooTheme Builder. Unfortunately, this means that the WPML Translation Editors or automatic translation cannot be used for content created with the YooTheme Builder. For more details, please refer to the following documentation:
You can also participate in the community discussion and vote for compatibility at YooTheme support thread. Additionally, due to the exceptional situation of the credits used for non-visible translations, we are considering crediting back the amount used and will update you shortly.
If this solution does not apply to your case, or if it seems outdated, we highly recommend checking related known issues at WPML 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.
Problem: The client noticed a message urging them to activate the WPML String Translation plugin to convert Rank Math Setting values into different languages after running a string scan. They were unsure which strings were relevant for translation and how to proceed with the Rank Math SEO Pro plugin, especially since the file content in their installation did not match the official repository. Solution: We recommended that the client reinstall the Rank Math plugin to ensure that the files match those in the official plugin repository. This step is crucial because the discrepancies in file content can prevent proper functioning. If the issue persists after reinstallation, we advised contacting the plugin authors for further clarification.
Please note that this solution might be outdated or not applicable to your specific case. If the problem persists, 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 needed, do not hesitate to open a new support ticket at WPML support forum for further assistance.
Problem: Wenn Sie globale Elemente in der Divi Bibliothek speichern, die dynamische Inhalte mit "before- und after-Texten" enthalten und diese im Divi Theme Builder verwenden, kann es vorkommen, dass bei der Übersetzung der dynamische Inhalt nicht erkannt wird und der rohe Divi-Code angezeigt wird. Dies führt dazu, dass die Seite nicht korrekt dargestellt wird. Solution: Wir empfehlen Ihnen, die neueste Version von WPML zu installieren, um dieses Problem zu beheben. Bitte gehen Sie zu Plugins > Neu hinzufügen > Kommerziell > Klicken Sie auf „Updates prüfen“ und aktualisieren Sie die WPML-Plugins auf die neuesten Versionen. Stellen Sie sicher, dass Sie vorher ein Backup erstellen. Weitere Informationen finden Sie in der zugehörigen Fehlerbehebung: https://wpml.org/errata/divi-5-dynamic-content-not-fully-supported/
Falls diese Lösung für Sie nicht relevant ist, weil sie veraltet ist oder nicht auf Ihren Fall zutrifft, empfehlen wir Ihnen, ein neues Support-Ticket zu eröffnen. Wir empfehlen Ihnen auch, verwandte bekannte Probleme 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 is using Fluent Forms on their contact page and WPML for site translation. Despite following all recommended steps, including setting up the form for translation and using WPML String Translation for labels, the Fluent Forms block still displays in Dutch on the English version of the contact page. Solution: We recommended checking if the client is using the connector plugin and shared the link to the open errata documentation for a known issue with Fluent Forms and WPML, which might be affecting the translation. The documentation can be found here: https://wpml.org/errata/fluent-forms-error-messages-from-global-settings-are-not-translatable/.
If this solution does not resolve the 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 with us for further assistance.
Problem: Der Kunde erhält eine Meldung zur Aktivierung des WPML String Translation Moduls für Rank Math und hat Probleme mit der Registrierung von Toolset, obwohl WPML vollständig registriert ist.
Solution: Zuerst sollte überprüft werden, ob das WPML String Translation Modul aktiv ist: 1. Gehe zu Plugins → Installierte Plugins. 2. Suche nach WPML String Translation und aktiviere es, falls es noch nicht aktiv ist.
Falls Probleme mit der Toolset-Lizenzierung bestehen, versuche WPML erneut zu registrieren: 1. Gehe zu Plugins → Neu hinzufügen. 2. Klicke auf den Reiter Kommerziell. 3. Klicke auf WPML registrieren und folge den Anweisungen.
Bei einem Fehler durch Rank Math, der auftritt, wenn WPML und String Translation aktiv sind, folge diesen Schritten: 1. Öffne die Datei
3. Deaktiviere und aktiviere Rank Math SEO erneut.
Falls diese Lösungen nicht relevant sind oder veraltet erscheinen, empfehlen wir, die bekannten Probleme zu überprüfen, die Version des dauerhaften Fixes zu bestätigen und sicherzustellen, dass die neuesten Versionen von Themes und Plugins installiert sind. Zögere nicht, ein neues Support-Ticket zu eröffnen, falls weitere Hilfe benötigt wird.
Problem: The client is experiencing an issue where the footer, although correctly translated in WPML, still displays in English on the live website in the French version and other translated pages. This footer is a custom post type created by the theme and selected from the theme options.
Solution: We resolved the issue by identifying the footer block IDs for each language from the footer template pages. In WPML → String Translation, we registered the English footer ID and added the corresponding IDs for the other languages. This configuration ensures that WPML knows which footer template to use for each language in the MedCity theme. After saving these settings, each language now correctly loads the appropriate footer template. Additionally, some footer links are custom menu links, which must be manually translated in WPML → String Translation. It's also necessary to translate the menus themselves to ensure all footer links display correctly in every language.
If this solution does not resolve your issue, or if it seems outdated or irrelevant 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 further assistance is needed, please open a new support ticket at WPML support forum.
Problem: You are using WPML with Advanced Translation Editor and Fluent Forms (v6.1.21) with enabled WPML integration. You are trying to translate the submit button label of a Fluent Form into English and Spanish, but the label remains in German on both /en/ and /es/ pages, despite completed translations. Solution: The plugin "Multilingual Forms for Fluent Forms with WPML" is not an official WPML plugin. We recommend consulting the developer of this addon. You should create one form in each language, ensuring each form has a unique ID. Make sure to use the correct shortcodes manually in each language's content. WPML automatically handles shortcode adjustments for other supported forms like Contact Form 7, Gravity Forms, WP Forms, and Ninja Forms, but not for Fluent Forms.
If this solution does not resolve your issue or seems outdated, please check the related known issues, verify the version of the permanent fix, and confirm that you have installed the latest versions of themes and plugins. We highly recommend opening a new support ticket if the problem persists. You can do so at WPML support forum.
