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.
Problema: In homepage, WPML non rileva né traduce alcune sezioni, come la sezione 'benefici'. Questo accade nonostante il contenuto sia parte di un widget del tema utilizzato e non un widget custom di Elementor. Soluzione: Per rendere le sezioni non rilevate da WPML traducibili, è necessario registrare i widget del tema per la traduzione. Segui la procedura dettagliata in questa guida: https://wpml.org/documentation/support/multilingual-tools/registering-custom-elementor-widgets-for-translation/. Se la soluzione proposta non risolve il problema o sembra non essere più attuale, ti consigliamo di verificare la presenza di problemi noti correlati su https://wpml.org/known-issues/, controllare la versione della correzione permanente e assicurarti di avere installato le ultime versioni di temi e plugin. Se il problema persiste, ti invitiamo a aprire un nuovo ticket di supporto.
Problem: You are trying to display different images for different languages on your WordPress site using BeTheme's Be.Story box Elementor widget, but the same image appears in both languages. Solution: We resolved this issue by registering the necessary XML configuration in WPML. Here's how you can do it: 1. Navigate to WPML -> Settings -> Custom XML Configuration. 2. Add the following XML configuration:
3. Save the configuration. 4. Update your page translations, ensuring that the image URLs are correctly translated. For more detailed guidance, refer to the following documentation:
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.
Problem: Sie können Ihren mit Prime Slider von BDThemes in Elementor erstellten Slider nicht übersetzen, da keine Möglichkeit zur Übersetzung über die String Translation vorhanden ist. Solution: 1. Erstellen Sie eine XML-Konfiguration für das benutzerdefinierte Elementor-Widget, um es mit dem WPML-Übersetzungseditor übersetzen zu können. Anleitung zur Registrierung von Page Builder Widgets für die Übersetzung finden Sie hier: https://wpml.org/documentation/support/language-configuration-files/how-to-register-page-builder-widgets-for-translation/ 2. Speichern Sie folgende XML-Konfiguration unter WPML > Einstellungen im Reiter Benutzerdefinierte XML-Konfiguration:
4. Editieren Sie den Slider auf der Originalseite, speichern Sie die Seite erneut ab und übersetzen Sie sie mit dem WPML Übersetzungseditor.
Falls diese Lösung veraltet ist oder nicht auf Ihr Problem zutrifft, empfehlen wir Ihnen, die bekannten Probleme zu überprüfen, die Version des dauerhaften Fixes zu bestätigen und sicherzustellen, dass Sie die neuesten Versionen von Themes und Plugins installiert haben. Sollten weiterhin Probleme bestehen, eröffnen Sie bitte ein neues Support-Ticket im WPML Support-Forum.
Problem: If you're experiencing issues with some text blocks not being translated and not appearing in the translation editor, and you suspect it's due to using a custom Elementor component, we can help. Solution: The widget you're dealing with is a custom one, known as "Dachcom". To enable WPML support for this widget, you need to manually add the necessary configuration. We recommend following the guidelines provided in the WPML documentation on Language Configuration Files.
Additionally, using Elementor, WPML facilitates the generation of the required configuration. You can find detailed, step-by-step instructions on how to register your custom Elementor widgets for translation at Registering Custom Elementor Widgets for Translation.
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. Should you need further assistance, please do not hesitate to open a new support ticket or visit our support forum at WPML Support Forum.
Problem: Sie können im Translation Editor nur den Titel der Startseite übersetzen, aber weitere Abschnitte oder Felder des Kimono Themes von Bravisthemes werden nicht angezeigt. Solution: Es scheint, dass bestimmte XML-Konfigurationen in Ihrem Theme nicht korrekt eingestellt sind. Wir empfehlen Ihnen, die folgenden XML-Einträge zu entfernen:
<fields-in-item items_of="slider2"/>
<fields-in-item items_of="slider3"/>
<fields-in-item items_of="slider4"/>
<fields-in-item items_of="slider6"/>
Nachdem Sie diese Einträge entfernt haben, überprüfen Sie bitte, ob die fehlenden Abschnitte nun im Translation Editor angezeigt werden. Wenn das Problem weiterhin besteht, entfernen Sie schrittweise weitere Teile der Konfiguration, um die genaue Ursache zu identifizieren.
Diese Lösung könnte möglicherweise veraltet sein oder auf Ihren Fall nicht zutreffen. Wir empfehlen Ihnen, die bekannten Probleme 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. Sollten weiterhin Probleme auftreten, zögern Sie nicht, ein neues Support-Ticket zu eröffnen. Besuchen Sie dazu unser Support-Forum.
Problem: You are trying to translate pages from English to German using Elementor and the Hello Plus theme, but certain elements like the CTA element are not translating. Solution: The issue arises because the CTA element from the Hello Plus plugin is not registered as translatable in WPML. To fix this, you need to declare the widget as translatable by adding a custom XML configuration. Follow these steps:
1. Navigate to WPML->Settings->Custom XML Configuration and add the following code:
2. Edit the Homepage with Elementor, make a small change, and update. 3. Access the translation interface, and the content should now be available for translation. 4. Clear your site's cache and check the front end.
If this solution does not resolve your issue or seems outdated, please check for related known issues at https://wpml.org/known-issues/, verify the version of the permanent fix, and ensure you have installed the latest versions of themes and plugins. If the problem persists, we recommend opening a new support ticket at WPML support forum.
Problem: Der Kunde hat Probleme mit der Übersetzung von Links in den Creative Buttons von Essential Addons für Elementor. Die Namen und Ziel-URLs der Buttons werden nicht übersetzt. Solution: Wir haben die Widgets auf einer Testseite überprüft und festgestellt, dass die URLs wie erwartet übersetzt werden, wenn man die Links in den Widgets auf dem originalen Inhalt bearbeitet und den Inhalt erneut speichert. Es ist wichtig, vollständige URLs zu verwenden. Was hier alleine nicht zu funktionieren scheint, ist das interne Links automatisch angepasst werden. Man muss diese in diesem Fall selbst im Übersetzungseditor anpassen.
Falls diese Lösung veraltet ist oder nicht auf Ihr Problem zutrifft, empfehlen wir Ihnen, ein neues Support-Ticket zu erö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.
Problem: The client was unable to translate the 'Sign in' and 'Register' tabs on the login page of their website into different languages using WPML. Solution: We recommended the following steps: 1. Add the following XML configuration in WPML >> Settings > Custom XML Configuration section:
2. Open the default language login page in the Elementor page builder and add the label text in the desired language. 3. Click on the secondary language icon to open the page in Advanced Translation Editor, where the 'Sign in' and 'Register' labels should now be available for translation.
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.
Problème : Si vous rencontrez des difficultés pour traduire l'intégralité du contenu de votre page d'accueil avec l'outil ATE de WPML, et que seuls quelques mots sont disponibles à la traduction, cela peut être dû à l'utilisation de widgets personnalisés Elementor qui n'ont pas été enregistrés pour la traduction. Solution : Nous vous recommandons de vérifier si le contenu manquant provient de widgets Elementor personnalisés ou de modules complémentaires tiers. Si c'est le cas, vous devrez enregistrer ces widgets pour la traduction dans WPML. Vous pouvez trouver un guide utile à ce sujet ici : https://wpml.org/documentation/support/multilingual-tools/registering-custom-elementor-widgets-for-translation/ De plus, nous avons généré et ajouté le code nécessaire à votre fichier XML pour assurer la traduction des widgets personnalisés. Voici le code :
Après avoir ajouté ce code, nous vous conseillons de rafraîchir la page pour que les nouveaux paramètres prennent effet et que le contenu des widgets personnalisés soit chargé sous l'éditeur de traduction. Si cette solution ne résout pas votre problème ou semble dépassée, nous vous recommandons de vérifier les problèmes connus sur https://wpml.org/known-issues/, de vérifier la version du correctif permanent, et de confirmer que vous avez installé les dernières versions des thèmes et plugins. Si le problème persiste, n'hésitez pas à ouvrir un nouveau ticket de support sur notre forum de support.
Problem: The client was unable to translate links in various sections of their multilingual website using Elementor and WPML. These included product images, service box icons, and other elements that did not show up in the translation editor. Solution: We recommended disabling the cache temporarily to ensure changes could be reflected immediately. We provided custom XML configurations to enable the translation of specific Elementor widgets. For example, we added:
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/.
Problem: The client is trying to translate their site to German, including webpage links that should redirect to other German-translated pages. However, the buttons and in-text links still point to the original pages instead of the translated ones. The issue involves Elementor content and a custom widget from Element Pack Pro. Solution: 1. For links appearing in WPML > String Translation but not applying on the live site, ensure to manually translate them using the WPML Translation Editor. Use the search bar in the translation editor to find links by typing "http". 2. For content created with Element Pack Pro, such as Advanced Icon Boxes, a translation of links seems currently not possible, The author would need to adapt the XML configuration for such widgets to make it translatable. If you run into such an issue, please reach out to us and we will assist you on this matter. 3. Generally, if Elementor content does not appear in the WPML Translation Editor, you might need to create a custom XML configuration to ensure that Elementor widgets are properly registered for translation. You can find guidance on this at https://wpml.org/documentation/support/language-configuration-files/how-to-register-page-builder-widgets-for-translation/.
If these steps do not resolve your issue or if the solution seems outdated or irrelevant to your specific case, we recommend opening a new support ticket. We also 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, please visit our support forum at https://wpml.org/forums/forum/english-support/.
