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: You are trying to translate content created with Elementor and the CharityWP theme, which includes custom Elementor elements from the Thim Core Plugin. These elements are not translatable using the usual methods such as the Advanced Translation Editor. Solution: We recommend ensuring that every custom Elementor widget has an XML configuration so it can be translated using the WPML Translation Editor. This configuration should ideally be provided by the theme author and included in a
If these solutions do not apply or become outdated, or if you encounter further 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 needed, please open a new support ticket at https://wpml.org/forums/forum/english-support/ for further assistance.
Problem: The client created translations in NL and EN from the French language for their website using the usual method by clicking on the '+'. However, in the translator, the fields of the Price List widget do not appear. After making a correction in French, all translations in NL and EN reverted back to French. Solution: The issue was due to the Price List widget originating from a third-party theme or plugin that was not compatible with WPML. If these are widgets implemented in Elementor, they need to be registered as explained here: https://wpml.org/documentation/support/multilingual-tools/registering-custom-elementor-widgets-for-translation/ To prevent translations in NL and EN from reverting to French after a correction, avoid modifying the English and Dutch content directly from these pages. Do not alter the translation using the site editor.
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.
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 open a new support ticket at WPML support forum.
Problema: Stai utilizzando il tema TrekOn Child con Elementor e hai notato che attivando la traduzione automatica con WPML, alcune sezioni della pagina vengono tradotte mentre altre no. Inoltre, la traduzione manuale non funziona. Soluzione: Se stai riscontrando questo problema, è probabile che ci siano widget custom di Elementor creati dal tema che necessitano di essere resi compatibili con WPML. Ti consigliamo di seguire questa procedura per registrare i widget custom per la traduzione.
Se la soluzione proposta non risolve il problema o sembra non essere più attuale, ti invitiamo a verificare le problematiche note, a controllare la versione della correzione permanente e a confermare che hai installato le ultime versioni dei temi e dei plugin. Se il problema persiste, ti consigliamo di aprire un nuovo ticket di supporto. Per assistenza ulteriore, visita il forum di supporto WPML.
Problem: Клиент столкнулся с проблемой, что при добавлении перевода к странице через WPML не отображаются все поля для перевода. Также, несмотря на завершенный статус перевода, переводы фактически не отображаются. Solution: 1. Возможно, используются нестандартные виджеты Elementor, для которых WPML не имеет конфигурации. Рекомендуем заменить виджет на стандартный или поддерживаемый WPML виджет и проверить результат. 2. Отключите редактор переводов WPML для страницы и выполните перевод непосредственно в Elementor. Подробная инструкция доступна здесь: https://wpml.org/ru/документация/перевод-контента/как-использовать-разные-дизайны-для-р/ 3. Обновите плагины WPML до последней версии, чтобы исключить проблемы совместимости, особенно с последними версиями Elementor. Проверьте наличие обновлений в разделе «Моя учетная запись -> Загрузки» на сайте WPML. Инструкции по обновлению доступны здесь: https://wpml.org/ru/faq/как-установить-wpml/
Если предложенные решения не помогут, рекомендуем проверить известные проблемы, убедиться в актуальности версии исправлений и установить последние версии тем и плагинов. В случае, если проблема сохраняется, пожалуйста, откройте новый тикет поддержки.
Problema: Stai cercando di tradurre elementi di Elementor Pro sulla pagina dei Prodotti del tuo sito, ma alcuni elementi non vengono proposti per la traduzione. Soluzione: Per poter tradurre gli elementi di Elementor Pro che non vengono automaticamente proposti per la traduzione, devi registrare questi elementi. Segui questa procedura per registrare i widget personalizzati di Elementor per la traduzione.
Se la soluzione proposta non risolve il problema o sembra non essere più aggiornata, ti consigliamo di verificare i problemi noti correlati, controllare la versione della correzione permanente e confermare che hai installato le ultime versioni dei temi e dei plugin. Se il problema persiste, ti invitiamo a aprire un nuovo ticket di supporto.
Problem: The client was unable to translate the 'eael_fg_control' field in the Filterable Gallery addon from Essential Addons using WPML. The XML code added for translation did not work, and the field was not listed under WPML > Settings > Custom fields translations.
Solution: We confirmed that the XML provided by Essential Addons was complete and included all necessary fields, so no additional custom XML was required. The issue was unique to the client's site configuration. We suggested removing all custom XML code added by the client and verified that the fields were registered correctly in the plugin's XML configuration file. If the issue persisted, we recommended switching from the Classic Translation Editor (CTE) to the Advanced Translation Editor (ATE) for better handling of the content. Additionally, we provided a custom XML code to ensure all relevant fields were included and suggested a template refresh to update the fields in the translation editor.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your case, please visit our known issues page, verify the version of the permanent fix, and ensure you have installed the latest versions of themes and plugins. If further assistance is needed, we highly recommend opening a new support ticket here.
Problem: The client was using the Premium Addons for Elementor widget for their blog, along with WPML for translation. They encountered an issue where the category filter worked correctly in Estonian, the main language, but displayed Estonian posts when filtering in English. Solution: We recommended reviewing an errata our team published, which addresses issues with the Premium Addons for Elementor Widget not displaying posts in secondary languages when including or excluding post categories. You can find the errata here: https://wpml.org/errata/premium-addons-for-elementor-blog-widget-not-showing-posts-in-the-secondary-language/ We also suggested updating the Hello Elementor theme, Premium Addons for Elementor, and Elementor itself. After updates, it was necessary to re-add the snippet from the errata to the functions.php file.
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 at WPML support forum.
