Inicio›Soporte›Etiqueta del tema: 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 translate certain texts into Arabic, including the word 'SHOP' and phrases in the top bar of their website. Additionally, Arabic characters in the Slider Revolution were displaying backwards and separated. Solution: For the Slider Revolution issue, we recommended accessing WP Admin -> Slider Revolution and editing the 'Demo-rtl 1' slider used for Arabic. The client should remove the text layers and add them again without applying animation effects that break the words into individual letters. For the text in the top bar, which is managed by the 'Thim Elementor Kit' plugin (not WPML-compatible), we attempted standard methods to find the text through string translation but were unsuccessful. We offered to download a clone/snapshot of the website to further investigate how the plugin manages this text. For the image accordion issue, we made the fields translatable by adding custom XML configuration to the WPML settings. The client should open the page in the default language, make a minor edit to refresh the elements detected by WPML, and then proceed with the translation.
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 further assistance is needed, please open a new support ticket at WPML support forum.
Problem: The client has translated all identified strings using the Translation Editor on an Elementor page, but only a few words are displayed as translated, with about 90% not reflecting the changes. Solution: We suggested checking if there are global templates in Elementor that might not be visible in the Translation Editor and need translating separately. Additionally, we identified that the theme used ('Tastyc') is not officially compatible with WPML. We recommended contacting the theme developers to encourage them to join our Go Global program. As a workaround, we advised the client to: 1. Edit the page in the default language. 2. Switch to the secondary language using the language switcher. 3. Edit with Elementor and manually adjust translations directly in Elementor.
If this solution does not resolve the issue or seems outdated, please check our related known issues and ensure you have the latest versions of themes and plugins. If problems persist, we highly recommend opening a new support ticket here.
Problem:
An Elementor Custom Widget "Content Switcher" from "HappyAddons" is used to display different product collections in the form of sections for which an Elementor template is used.
The Elementor content is translated with the WPML Translation Editor.
On the translated content the translations do not show up as the Content Switcher Widget is not applying the correct template.
Solution:
Take note, that this is a compatibility issue between "HappyAddons" and WPML. The user was asked here to recreate the issue on a test so that we can escalate the problem internally and work on a solution.
Saldy the user did close the ticket before we were able to take any further steps.
If you have a similar issue, please open a ticket.
Workaround:
Make sure that you translated your Elementor Templates, then open Elementor on the translated content and make sure that the Content Switcher Widget is using the correct template.
Take note, that the settings of the widgets might get reverted, if you translate the content again with the WPML Translation Editor.
This means you should use the WordPress Editor as a translation method for affected content until we are able to find a solution for making the "Content Switcher Widget" translatable with the WPML Translation Editor.
Problem: You are trying to translate content using a plugin compatible with WPML, but the theme support has indicated no actions are needed on their part. You are seeking assistance for the correct configuration of the plugin. Solution: The content you referred to is within an 'About' widget created by the theme. All theme widgets (as shown in your screenshot) need to be made compatible with WPML by following this procedure. If the theme authors claim everything is in order, they might have made a mistake or they might believe that the only way to translate with WPML is manually, in which case you cannot use the translation editor.
If this solution does not resolve your issue, or if it seems 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 further assistance is needed, please open a new support ticket.
Problem: The client was having difficulty writing the correct XML code to register an Elementor widget ('be-timeline') for translation using WPML, despite following the documentation. Solution: We recommended the following steps: 1. Insert the following XML in the WPML >> Settings > Custom XML Configuration section:
For more details, refer to the documentation on translating custom shortcodes with WPML. 3. Make a small change in the default language page to reload the translation and attempt translating it again.
If this solution does not resolve your issue, or if it seems outdated or irrelevant 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 needed, please open a new support ticket.