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:
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.
Problem: If you're experiencing issues with untranslated button texts on your webpages, and these buttons are from the 'Charity Addon for Elementor', it's likely because the widget lacks a necessary XML configuration for WPML to recognize and translate the texts. Solution: We recommend adding the following XML configuration to enable translation for the button texts:
Add this configuration in WPML > Settings > Custom XML Configuration. Then, edit the widget on the original content, save it, and open the translation in the WPML Translation Editor. The button text should now be visible for translation. For translating the link, search for "http" in the text field on the top left of the WPML Translation Editor. It is the responsibility of the theme author to include such configurations in a wpml-config.xml file in the root directory of the Elementor addon plugin. You can refer them to our Go Global Program for assistance.
If this solution does not apply because it's outdated or not suitable for 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 issues persist, please open a new support ticket.