Início›Suporte›Tag do Tópico: Elementor Custom Widgets
Elementor Custom Widgets
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 was unable to save certain strings in the string translation. Solution: We recommended that the client first install the multilingual-tools plugin from https://github.com/OnTheGoSystems/multilingual-tools. After installation, we advised following the steps outlined in our documentation for registering custom Elementor widgets for translation. The client can find the guide here: Getting Started and Using WPML Config Generator for Elementor. We also offered to check the XML generated by the WPML Config Generator if the problem persisted.
Please note that the solution provided might be irrelevant due to being outdated or not applicable to your case. If the issue persists, we highly 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 necessary, please open a new support ticket in the WPML support forum.
Problem: The client was unable to translate the Contact Form 7 widget on their Contact page, which was created by the Elementor widget "reycore-cf7" from the Rey theme. Additionally, the client could not find where to translate the tab names on their product pages, such as "détails du produit", "livraison", and "conseils de lavage". Solution: We instructed the client to register the "reycore-cf7" widget for translation by adding the following code to WPML > Settings > Custom XML Configuration:
If the solution provided does not apply to your case, or if it seems outdated, we recommend checking the 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.
Problem: The client was unable to find where to translate text on a WooCommerce shop page, which was added through the Title widget from the Themerex addons. Solution: We suggested that since Themerex addons are not included in our list of compatible plugins, the widget might not support translation, which could be why the content is not available for translation. We recommended following the steps provided in a previous support ticket that addressed a similar issue:
If you're experiencing this issue, we recommend trying the steps mentioned in the provided link. However, please note that the solution might be irrelevant due to being outdated or not applicable to your 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 you still need assistance, please do not hesitate to open a new support ticket with us.
Problem: The client needed to translate a button in the menu area of the Finnish version of their website, which was created with Elementor and associated with the "Themerex Addon" plugin. Solution: We informed the client that the "Themerex Addon" plugin is not listed in our directory of compatible plugins, which may result in the lack of integrated translation support for its widgets. We suggested that the client ensures translation support is integrated for these widgets. We provided documentation on how to register page builder widgets for translation: https://wpml.org/documentation/support/language-configuration-files/how-to-register-page-builder-widgets-for-translation/ We also recommended that the client could ask the plugin developer to join WPML's Go Global program: https://wpml.org/documentation/support/go-global-program/ Furthermore, we provided a solution to add translation support for Elementor widgets using our tool, which simplifies the process of registering custom widgets. We directed the client to our documentation for registering custom Elementor widgets for translation: https://wpml.org/documentation/related-projects/wpml-compatibility-test-tools-plugin/registering-custom-elementor-widgets-for-translation/ We encouraged the client to reach out if they needed further assistance.
Please note that this solution might be irrelevant if it's outdated or not applicable to your case. If you're still experiencing issues, 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 for personalized assistance: https://wpml.org/forums/forum/english-support/
Problema: Está intentando traducir la página de inicio de su sitio web y espera ver la opción para traducir todos los elementos en Elementor, pero algunos elementos no muestran la opción de traducción. Solución: Si está experimentando este problema, le recomendamos seguir los pasos de nuestra guía sobre cómo agregar soporte de WPML a widgets personalizados de Elementor, que puede encontrar aquí: https://wpml.org/documentation/plugins-compatibility/elementor/how-to-add-wpml-support-to-custom-elementor-widgets/.
Tenga en cuenta que la solución proporcionada podría no ser relevante si ya está desactualizada o si no se aplica a su caso. Si después de seguir los pasos aún tiene problemas, le sugerimos abrir un nuevo ticket de soporte. También recomendamos revisar los problemas conocidos en https://wpml.org/known-issues/, verificar la versión de la solución permanente y confirmar que ha instalado las últimas versiones de temas y plugins. Si necesita asistencia adicional, no dude en contactarnos en el foro de soporte de WPML.
Problem: The client is using the Divi Contact Form Helper plugin and has identified certain fields that are not available for translation in the WPML Advanced Translation Editor. These fields include Description, Placeholder text, HTML field, and various fields within the Confirmation Email settings.
Solution: We provided a Custom XML Configuration to make the missing fields translatable. The client should add the following code to WPML > Settings > Custom XML Configuration:
After adding the code, the client should re-translate the page. Additionally, we reminded the client not to forget to translate URLs, providing a link to our documentation on this topic:
If the provided solution does not apply due to being outdated or not relevant to the client's specific case, we recommend opening a new support ticket. We also highly suggest checking related known issues at https://wpml.org/known-issues/, verifying the version of the permanent fix, and confirming that the latest versions of themes and plugins are installed.
