Elementor Custom Widgets

Problem:
The client reported that despite translations being marked as complete, the 'Login / Register' strings in an Elementor custom widget were not reflecting on the front end.
Solution:
We resolved the issue by modifying the WPML settings to register the strings for translation. Here are the steps we followed:
1. Navigate to WPML -> Settings -> Custom XML tab.
2. Add the following code to register the strings for translation:

<wpml-config>
  <elementor-widgets>    
    <widget name="apus_element_user_info2">
      <fields>
        <field>login_register_text</field>
        <field>login_text</field>
        <field>register_text</field>
        <field>login_title</field>
        <field>register_title</field>              
      </fields>
    </widget>
  </elementor-widgets>
</wpml-config>

3. Edit the original header and add an empty space to prompt WPML to recognize that the translation needs an update.
4. Edit the translation of the header where the texts will now be available for translation.

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 the problem persists, please open a new support ticket.

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 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:

<wpml-config>
  <elementor-widgets>
    <widget name="be-timeline">
      <fields-in-item items_of="list">
        <field>list_title</field>
        <field>list_content</field>
      </fields-in-item>
    </widget>
  </elementor-widgets>
</wpml-config>

2. To allow the translation of numbers in the timeline title field using WPML Translation Editor, add the following code to the functions.php file:

add_filter( 'wpml_tm_job_field_is_translatable', '__return_true' );

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.