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 trying to translate a specific string on their website, which is added using the Elementor page builder, but is unsure how to do so. Solution: 1. Open the default language page in Edit mode. 2. Make a small change, such as adding a space or a + sign in the page title. 3. Save the page. 4. Remove the small change made in step 2. 5. Update the page again. 6. Try to open the translated page in WPML Translation Editor to see if the title is now available for translation. If the title is still not available in WPML Translation Editor, the client may need to register the element by following this documentation: https://wpml.org/documentation/support/multilingual-tools/registering-custom-elementor-widgets-for-translation/
If this solution does not resolve the issue or if it seems outdated or irrelevant, 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 further assistance is needed, please open a new support ticket at WPML support forum.
Problem: The client was unable to see the translated texts of the Apifon form on the front end of their website after using WPML to translate them. Solution: We first verified that the form was correctly translated on the English version of the site. To resolve the issue, we added a custom XML configuration to WPML > Settings > Custom XML Configuration. This configuration ensures that the specific fields of the Apifon Elementor Form Widget are translatable. Here is the XML code we used:
If this solution does not resolve your issue, or if it 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 the problem persists, please open a new support ticket.
Problem: You are trying to translate the BetterDocs search heading on your homepage using WPML, but despite checking all related string translations and the admin side, you haven't been successful. The heading of the BetterDocs search widget cannot be translated, although the search placeholder appears correctly on the page translations. Solution: We recommend checking if the widget has a valid XML configuration, as this is often necessary for translating custom Elementor widgets with WPML. If the strings related to this widget are not available in the WPML Translation Editor when translating the homepage, it indicates that the widget is missing a valid XML configuration. You can learn more about how to register page builder widgets for translation by visiting our guide: https://wpml.org/documentation/support/language-configuration-files/how-to-register-page-builder-widgets-for-translation/
If this solution does not resolve your issue or seems irrelevant due to being outdated or not applicable 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 you still need assistance, please open a new support ticket at our support forum.
Problem: If you're experiencing issues with translating the Accordion Element content in Elementor using WPML, and you need an XML snippet to include in your translations. Solution: We recommend you follow these steps: 1. Add the following XML in WPML >> Settings > Custom XML Configuration section:
2. Open the default language page in Edit mode. 3. Make a small change, such as adding a space or a '+' sign in the page title where you are facing issues. 4. Save the page. 5. Remove the small change made in step 3. 6. Update the page again. 7. Try to translate the page using WPML Translation Editor and check if you can now translate the Accordion Element content. For more details, visit our documentation on registering custom Elementor widgets 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 : Le client ne parvient pas à trouver les titres de la page d'accueil dans les traductions ou dans les traductions de chaînes WPML en utilisant Elementor et le plugin RTMKIT. Solution : 1. Ajoutez le XML suivant dans WPML >> Paramètres > Section de configuration XML personnalisée :
2. Ouvrez la page dans la langue par défaut en mode Édition. 3. Faites un petit changement, par exemple, ajoutez un espace ou un signe + dans le titre de la page où vous rencontrez des problèmes. 4. Sauvegardez la page. 5. Retirez le petit changement effectué à l'étape #3. 6. Mettez à jour la page à nouveau. 7. Essayez maintenant de traduire la page en utilisant l'éditeur de traduction WPML et vérifiez si vous pouvez maintenant traduire le contenu de l'élément de titre avancé. Pour plus de détails, consultez la documentation ici : https://wpml.org/documentation/support/multilingual-tools/registering-custom-elementor-widgets-for-translation/
Si cette solution ne résout pas votre problème ou si elle semble obsolète, nous vous recommandons de vérifier les problèmes connus sur https://wpml.org/known-issues/, de vérifier la version de la correction permanente et de confirmer que vous avez installé les dernières versions des thèmes et des plugins. Si le problème persiste, n'hésitez pas à ouvrir un nouveau ticket de support sur notre forum de support.
Problem: You are unable to translate the content of the Search Placeholder and Generic Text in JetEngine using WPML. Solution: We recommend adding the following XML code to WPML > Settings > Custom XML Code (tab):
After adding the code, please follow these steps: 1. Go to your Dashboard > Pages. 2. Open the edit screen of the original page and make a small change, such as adding an extra blank space at the end of a sentence or paragraph. 3. Save the changes. You should now see a circular arrow beside the second language links, indicating that an update is required. 4. Edit the translation again and ensure it is saved up to 100% translated. You should now be able to see the translated placeholders.
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 the problem persists, please open a new support ticket.
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.
