All issues in which we had to help clients with Elementor Custom Widgets either because they wanted to create one, or (more likely) when related to themes that have Elementor Custom Widgets integrated. Add whether you helped, sent to docs or escalated.
Problem: The client is experiencing issues with translating 'before' and 'after' strings of dynamic components in Elementor using custom XML. The provided XML did not function as expected. Solution: We recommend using the Multilingual Tools plugin to automatically generate the correct XML configuration for Elementor's dynamic tags. Here's a step-by-step guide: 1. Download and Install Multilingual Tools: Visit the OnTheGoSystems GitHub page, download the plugin, and install it on your WordPress site. 2. Prepare Your Elementor Page: Ensure the 'before' and 'after' strings are filled in the Elementor editor and the page is updated. 3. Generate the Custom XML: On the WordPress edit screen, find the 'WPML: Elementor Widgets' section to copy the automatically generated XML. 4. Apply the Generated XML: Paste this XML in the 'Custom XML Configuration' tab under 'WPML → Settings' and save. 5. Update and Translate: Make a minor edit to the page and use the WPML Advanced Translation Editor to translate the newly available strings.
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 problems persist, please open a new support ticket.
Problem: You need to update some text that is not showing in the translation editor. Solution: We recommend downloading and installing the beta version of WPML 4.9, which includes new features for Elementor, such as automatically configuring and making custom widgets translatable when they lack specific WPML configuration. You can download the WPML 4.9 version here. Additionally, please install the beta version for WPML String Translation 3.5, available here. After updating, edit the affected widget on the original page inside Elementor, save the page, and then open the WPML Translation Editor. This should allow you to see all the strings from this widget.
If this does not resolve the issue, or if updating is not an option for you, we 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.
Problem: The client was unable to translate the footer text 'book an innovation tour' from English to German using WPML. Despite trying automatic translation and pay-as-you-go options, the translation did not appear correctly, and accessing the footer translation showed a different text. Solution: We identified that the footer was created as an Elementor template. Here are the steps we took to resolve the issue: 1. Accessed the Elementor footer template in the default language. 2. Made a minor edit to the template and updated it. 3. Removed the edit and updated the template again. 4. Added the translation via the WPML Advanced Translation Editor (ATE). 5. Checked the front end to ensure the translation appeared correctly.
If you're experiencing a similar issue, we recommend following these steps. However, if this solution does not resolve your problem, or if it seems outdated or irrelevant to your case, please check the related known issues and confirm that you have installed the latest versions of themes and plugins. If the issue persists, we highly recommend opening a new support ticket at WPML support forum.
Problem: The client is experiencing an issue where Elementor content does not appear in the WPML Advanced Translation Editor (ATE). Only the Title, Tags, Media titles, and Yoast SEO fields are visible in ATE.
Solution: We found that the issue was due to the Elementor content being added as HTML which was incorrectly formatted. We corrected the issue by editing the content and removing the problematic style part from the HTML. We recommend checking if the Elementor content is added correctly and ensuring that no HTML errors are present. If you want to add styles, please use the CSS tab in Elementor.
Please test this solution on another page to see if it resolves the issue. If the problem persists or if this solution does not apply 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 necessary, please open a new support ticket at WPML support forum for further assistance.
Problem: El cliente tiene problemas al intentar agregar el idioma euskera y traducir páginas en Elementor usando WPML. Elementor muestra una pantalla en blanco o no duplica correctamente el contenido, solo la estructura. Además, la traducción automática con DeepL no detecta todo el texto, solo 65 palabras. Solution: 1. **Actualiza los plugins de WPML**: * **WPML Multilingual CMS**: Actualiza a la versión 4.8.6. * **OTGS Installer**: Actualiza a la versión 3.1.14. Ve a **Plugins → Añadir nuevo → Pestaña Comercial** y haz clic en **Buscar actualizaciones**.
2. **Verifica la configuración del Editor de Traducción Avanzado**: * Ve a **WPML → Ajustes**. * En **Traducción de tipos de entrada**, asegúrate de que **Páginas** esté configurado como **Traducible - usar traducción si está disponible o recurrir al idioma por defecto**. * En **Cómo traducir entradas y páginas**, selecciona **Usar el Editor de Traducción Avanzado de WPML** y guarda los cambios.
3. **Intenta traducir una página de Elementor de nuevo**: * Ve a **Páginas → Todas las páginas**. * Busca una página construida con Elementor que desees traducir. * Haz clic en el **icono de más (+)** bajo el idioma Euskera para esa página. Esto te llevará directamente al Editor de Traducción Avanzado. * Revisa si el contenido de tu página de Elementor aparece completo y listo para ser traducido.
Si después de seguir estos pasos el problema persiste, por favor, abre un nuevo ticket de soporte. Te recomendamos revisar los problemas conocidos, verificar la versión del arreglo permanente y confirmar que tienes instaladas las últimas versiones de los temas y plugins.
Problem: You are using the Real Homes theme and have created a search form with Elementor. Although you have translated the Property Features taxonomies using WPML, the translated features are not displaying in the Elementor search form, except for one feature that remains untranslated and in English. Solution: We tested the issue by setting up a new test site with the Real Homes theme and its plugins. After translating a property and its taxonomies, we added the "RH: Search Form 2" widget on a translated page. The form displayed all features correctly in the translated language. It appears that the "RH: Search Form 2" widget does allow using Real Homes Templates, which are set up in the Customizer's search settings. If you use such a template, you might run into unexpected issues. We were sadly not able to replicate and investigate this issue, as we would require a license key for Real Homes for this purpose. We recommend using the widget without any templates, in case you run into unexpected issues.
If this solution does not resolve your issue or seems outdated, we recommend checking the related 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 was unable to see the content in the text editor box inside the widget in the Advanced Translation Editor (ATE) when using WPML to translate the Filterable Gallery widget from the Essential Addon for Elementor. Solution: We identified an incorrect field definition in the WPML configuration XML. The client initially had
resolved the issue. Additionally, we suggested setting the
editor_type
to "LINE" for fields in the WPML config that are used with the Advanced Translation Editor, as the default is "LINE" and the only field set to "VISUAL" might not display correctly.
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: Sie versuchen, Widgets auf Elementor des Solis-Themes anzuzeigen, aber die Solis Elementor Blöcke werden nur kopiert, und die richtigen Systemfelder können nicht identifiziert werden. Sie fragen sich, warum die Elementor Widgets nicht übersetzt werden und wie Sie alle Blöcke übersetzbar machen können. Solution: Wir unterstützen standardmäßig alle Widgets, die mit Elementor und Elementor Pro ausgeliefert werden. Jedes benutzerdefinierte Elementor-Widget benötigt jedoch eine XML-Konfiguration, um mit dem WPML-Übersetzungseditor übersetzt werden zu können. Es ist die Aufgabe des Theme-Autors, eine solche Konfiguration in einer
wpml-config.xml
-Datei im Stammverzeichnis des Themes oder Plugins zu erstellen. Hier ist eine Anleitung, wie man Page Builder Widgets für die Übersetzung registriert: https://wpml.org/documentation/support/language-configuration-files/how-to-register-page-builder-widgets-for-translation/ Falls der Autor keine solche Konfiguration bereitstellt, können Sie alternativ selbst eine erstellen. Diese Konfiguration kann unter WPML > Einstellungen > Benutzerdefinierte XML-Konfiguration gespeichert werden. Nach dem Anlegen einer solchen Config müssen Sie den originalen Inhalt editieren, erneut speichern und dann den WPML-Übersetzungseditor öffnen. Falls Sie weitere Unterstützung benötigen, empfehlen wir Ihnen, ein neues Support-Ticket zu eröffnen. Überprüfen Sie auch die bekannten Probleme, 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 Hilfe besuchen Sie bitte unser Support-Forum: https://wpml.org/de/forums/forum/deutsch/
Problem: The client installed the WPML plugin and set Croatian as the default language and English as the additional language. However, when opening the manual translation editor, only fields like RankMETA SEO and other meta elements are visible, not the main page content. Solution: There are two potential causes and solutions for this issue: 1) The WordPress memory limit might be too low. We recommend increasing the WordPress memory limit to at least 256 MB, as WPML requires a minimum of 128 MB. To do this: - Connect to your website's server and open the
wp-config.php
file located in the WordPress root directory. - Add the following code just before the comment '// That's all, stop editing! Happy blogging.':
define('WP_MEMORY_LIMIT', '256M');
2) If the content was created using Elementor Custom Widgets from "Qi Addons for Elementor Premium", it might be missing a custom XML configuration to be translatable with the WPML Translation Editor. Check if custom Elementor widgets are used and refer to the guide on registering custom Elementor widgets for translation.
If these solutions do not resolve your issue, or if they seem 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: Se hai attivato la traduzione automatica e acquistato i crediti, ma le pagine non risultano tradotte, potrebbe essere necessario aggiornare la configurazione XML di WPML. Solution: Abbiamo aggiunto il codice XML necessario per garantire che i widget specifici vengano tradotti correttamente. Ecco il codice che abbiamo inserito:
Per applicare le traduzioni alle altre pagine, apri la pagina originale e clicca su 'Aggiorna' per sincronizzare automaticamente le traduzioni con i nuovi campi. Puoi anche andare su WPML --> Impostazioni --> Configurazione personalizzata del codice XML per copiare e incollare il codice nel tuo sito di produzione.
Se questa soluzione non risolve il problema o se sembra non essere più attuale, ti consigliamo di verificare i problemi noti, controllare la versione della correzione permanente e assicurarti di avere installato le ultime versioni di temi e plugin. In caso di ulteriori difficoltà, non esitare a aprire un nuovo ticket di supporto.
Problema: Il cliente ha riscontrato un problema con la traduzione delle pagine e un errore PHP quando visualizza i prodotti in francese. L'errore è causato da template/widget di Ecomus che ricevono dati non validi. Soluzione: Abbiamo richiesto l'accesso temporaneo (wp-admin e FTP) per esaminare meglio il problema. È importante effettuare un backup prima di fornire l'accesso. Inoltre, abbiamo suggerito di aprire il template nella lingua tradotta, cliccare su Modifica e verificare che tutte le impostazioni siano configurate correttamente.
Se la soluzione proposta risulta non pertinente, perché potrebbe essere datata o non applicabile al tuo caso, ti consigliamo di aprire un nuovo ticket di supporto. Ti raccomandiamo inoltre di consultare la pagina dei problemi noti, verificare la versione della correzione permanente e confermare di avere installato le ultime versioni di temi e plugin. Per assistenza ulteriore, visita il forum di supporto WPML.
