Elementor Custom Widgets

Problem:
Der Kunde hat Schwierigkeiten mit der Übersetzung von Custom Fields in einem WooCommerce-Shop, der mit Elementor und JetEngine erstellt wurde. Beim Duplizieren eines Produktes in Deutsch (D) wurde die englische (EN) Übersetzung überschrieben. Die Felder (Field format, Suffices, Prefixes in Dynamic Field and Terms) wurden im Advanced Translation Editor (ATE) von WPML nicht angezeigt, obwohl sie als übersetzbar markiert waren.
Solution:
Wir empfehlen die Installation der neuesten Beta-Versionen von WPML, um von neuen Features zu profitieren, die die Strings aller Elementor-Plugins automatisch erkennen. Nach der Installation soll der Kunde den originalen Inhalt editieren und speichern, dann die Übersetzung erneut durchführen. Hier ist eine Anleitung zur Installation der Beta-Versionen: https://wpml.org/faq/how-to-install-beta-and-development-versions-of-wpml/
Bitte installiere die Beta-Versionen von:

• WPML Multilingual CMS
• WPML String Translation
• WPML Multilingual & Multicurrency for WooCommerce

Sollte das Problem weiterhin bestehen, bitten wir dich, ein neues Support-Ticket zu eröffnen. Wir empfehlen 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 du die neuesten Versionen von Themes und Plugins installiert hast.

Problem:
You need to update some text that is not showing in the translation editor.
Solution:
We recommend downloading and installing the beta version of WPML 4.9, which includes new features for Elementor, such as automatically configuring and making custom widgets translatable when they lack specific WPML configuration. You can download the WPML 4.9 version here.
Additionally, please install the beta version for WPML String Translation 3.5, available here.
After updating, edit the affected widget on the original page inside Elementor, save the page, and then open the WPML Translation Editor. This should allow you to see all the strings from this widget.

If this does not resolve the issue, or if updating is not an option for you, 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 the problem persists, please open a new support ticket.

Problem:
The client is experiencing an issue where Elementor content does not appear in the WPML Advanced Translation Editor (ATE). Only the Title, Tags, Media titles, and Yoast SEO fields are visible in ATE.

Solution:
We found that the issue was due to the Elementor content being added as HTML which was incorrectly formatted. We corrected the issue by editing the content and removing the problematic style part from the HTML. We recommend checking if the Elementor content is added correctly and ensuring that no HTML errors are present. If you want to add styles, please use the CSS tab in Elementor.

Please test this solution on another page to see if it resolves the issue. If the problem persists or if this solution does not apply 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 necessary, please open a new support ticket at WPML support forum for further assistance.

Problem:
The client was unable to see the content in the text editor box inside the widget in the Advanced Translation Editor (ATE) when using WPML to translate the Filterable Gallery widget from the Essential Addon for Elementor.
Solution:
We identified an incorrect field definition in the WPML configuration XML. The client initially had

<field>link>url</field>

, which was incorrect. Changing this to

<field type="Heading Link" editor_type="LINK">link>url</field>

resolved the issue. Additionally, we suggested setting the

editor_type

to "LINE" for fields in the WPML config that are used with the Advanced Translation Editor, as the default is "LINE" and the only field set to "VISUAL" might not display correctly.

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.

Problem:
The client installed the WPML plugin and set Croatian as the default language and English as the additional language. However, when opening the manual translation editor, only fields like RankMETA SEO and other meta elements are visible, not the main page content.
Solution:
There are two potential causes and solutions for this issue:
1) The WordPress memory limit might be too low. We recommend increasing the WordPress memory limit to at least 256 MB, as WPML requires a minimum of 128 MB. To do this:
- Connect to your website's server and open the

wp-config.php

file located in the WordPress root directory.
- Add the following code just before the comment '// That's all, stop editing! Happy blogging.':

define('WP_MEMORY_LIMIT', '256M');

2) If the content was created using Elementor Custom Widgets from "Qi Addons for Elementor Premium", it might be missing a custom XML configuration to be translatable with the WPML Translation Editor. Check if custom Elementor widgets are used and refer to the guide on registering custom Elementor widgets for translation.

If these solutions do not resolve your issue, or if they seem 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.