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: Estás utilizando un tema con elementos personalizados en tu sitio web y al intentar traducir la página de inicio con WPML, no puedes encontrar las cadenas dentro de estos elementos personalizados. Además, una sección dentro de la página de Elementor no se detecta para traducción. Solución: Si estás enfrentando este problema, es probable que los widgets de Elementor que no se traducen provengan del tema Winwood. Para solucionar esto, necesitas generar un código XML que te permitirá traducir esos widgets. Hemos preparado un video que muestra cómo hacerlo, que puedes ver aquí: https://komododecks.com/recordings/JABhmu0orF9kAzep6UsC Además, te recomendamos seguir esta documentación para registrar los widgets personalizados de Elementor para su traducción: https://wpml.org/documentation/support/multilingual-tools/registering-custom-elementor-widgets-for-translation/
Si la solución proporcionada no resuelve tu problema o parece no ser relevante debido a actualizaciones o diferencias en tu caso, te recomendamos abrir un nuevo ticket de soporte. También es altamente recomendable que revises los problemas conocidos en https://wpml.org/known-issues/, verifiques la versión de la solución permanente y confirmes que tienes instaladas las últimas versiones de los temas y plugins.
Problem: Wenn Sie versuchen, Änderungen an der primären Sprache Ihrer Website vorzunehmen, die automatisch auf die übersetzten Sprachen übertragen werden sollen, und feststellen, dass diese Änderungen nicht übernommen werden, obwohl die automatische Übersetzungsfunktion aktiviert ist, könnte dies an der Kompatibilität Ihres Themes liegen. Solution: Das Houzez Theme ist derzeit als nicht kompatibel mit WPML gelistet. Sie können die bekannten Probleme und Lösungsvorschläge hier einsehen:
Wir empfehlen, den Theme-Autor zu informieren, dass das Houzez Theme von unserem Compatibility Team als nicht kompatibel eingestuft wurde. Der Theme-Autor sollte sich mit unserem Compatibility-Team in Verbindung setzen, möglicherweise über unser Go Global Programm.
Falls diese Lösung für Ihr Problem irrelevant erscheint, weil sie veraltet ist oder nicht auf Ihren Fall zutrifft, empfehlen wir Ihnen, ein neues Support-Ticket zu eröffnen. Wir empfehlen Ihnen 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. Für weitere Unterstützung besuchen Sie bitte unser Support-Forum: WPML Support-Forum.
Problem: You are unable to find some text in the WPML editor while trying to translate your website. Solution: If the custom XML you added did not resolve the issue, we recommend using the Multilingual Tools plugin to find the correct custom XML. Follow the steps in our documentation on registering custom Elementor widgets for translation. After locating and applying the correct XML, you can remove the Multilingual Tools plugin.
Please note that this solution might be outdated or not applicable to your specific 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 the issue persists, please open a new support ticket.
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.
