Skip Navigation

Home › Support › English Support › [Waiting for user feedback] Text do not appear in Translator

[Waiting for user feedback] Text do not appear in Translator

This is the technical support forum for WPML - the multilingual WordPress plugin.

Everyone can read, but only WPML clients can post here. WPML team is replying on the forum 6 days per week, 22 hours per day.

Sun Mon Tue Wed Thu Fri Sat
- 9:00 – 13:00 9:00 – 13:00 9:00 – 13:00 9:00 – 13:00 9:00 – 13:00 -
- 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 -

Supporter timezone: America/Los_Angeles (GMT-07:00)

This topic contains 12 replies, has 0 voices.

Last updated by Bobby 10 hours, 40 minutes ago.

Assisted by: Bobby.

Author Posts
May 6, 2025 at 2:20 pm #17002232

sergejsF

Background of the issue:
I am trying to translate the text on the pages of my site hidden link using WPML. However, the translator only shows two strings of text, and I have to use the String Translator to search for text strings one by one, which is time-consuming.
Here is a partial screenshot of the page: hidden link
And here is what the translator shows: hidden link

Additionally, some pages are showing different headers on the translated versions, and adjusting the page settings in the required language no longer resolves this issue. I have studied the support forum and tried recommendations, including those related to Elementor settings, but they did not work.

Symptoms:
The translator only shows two strings of text, and some pages have different headers on translated versions.

If I update to the latest version of plugins I loose translations made via String Translator from frontend (they are still there in the backend)

Questions:
How can I make all text strings appear in the WPML translator?
Why are some pages showing different headers on translated versions, and how can I fix this?
May 7, 2025 at 6:20 am #17004358

Bobby
WPML Supporter since 04/2015

Languages: English (English )

Timezone: America/Los_Angeles (GMT-07:00)

Hi there,

Please edit the page with Elementor and review the Elements used.

Are they native from Elementor or possibly from the theme?

If they are originating from the theme there is a high likelyhood that we will need to create a wpml-config.xml to register them.

Feel free to also share a screenshot with me if you are not sure.

May 7, 2025 at 10:27 am #17005567

sergejsF

Hi, yes, you might be right. These are the template elements. Is that a big problem?

Here are screenshots and screencast:

hidden link
hidden link
hidden link

Screencast: hidden link
May 8, 2025 at 5:41 am #17009739

Bobby
WPML Supporter since 04/2015

Languages: English (English )

Timezone: America/Los_Angeles (GMT-07:00)

Thank you for the screenshots! That helps me identify the elements. (they are originating from the theme and not Elementor)

It shouldn't be an issue, we just need to register them properly with WPML so they can get picked up by the ATE editor as shown in the documentation I shared in my previous reply.

- Please go to the page and edit it in Elementor.

- At the top (next to publish) click on the dropdown arrow and save as a template.

- Click to view your templates and then "export".

- Once the Export is finished share with me the .json file. (google drive, dropbox, we transfer, etc)

This will help me review it and help you create the wpml-config.xml

May 8, 2025 at 11:06 am #17011106

sergejsF

Thank you. Here is the file:
File ---> hidden link
May 8, 2025 at 5:02 pm #17013104

Bobby
WPML Supporter since 04/2015

Languages: English (English )

Timezone: America/Los_Angeles (GMT-07:00)

Thank you for sharing the JSON.

Please go to WPML->Settings->Custom XML Configuration (top of the page)

and add the following

<wpml-config>
  <elementor-widgets>
    <widget name="pxl_heading">
      <fields>
        <field type="LINE" name="title" />
        <field type="LINE" name="sub_title" />
      </fields>
    </widget>
    <widget name="pxl_text_editor">
      <fields>
        <field type="VISUAL" name="text_ed" />
      </fields>
    </widget>
    <widget name="pxl_button">
      <fields>
        <field type="LINE" name="text" />
        <field type="LINK" name="link" />
      </fields>
    </widget>
    <widget name="pxl_icon">
      <fields>
        <field type="LINE" name="circle_text" />
      </fields>
    </widget>
    <widget name="pxl_image_box">
      <fields>
        <field type="LINE" name="circle_text" />
      </fields>
    </widget>
    <widget name="pxl_testimonial_carousel">
      <fields>
        <field type="VISUAL" name="desc" />
        <field type="LINE" name="sub_text" />
      </fields>
      <repeaters>
        <repeater name="testimonial">
          <fields>
            <field type="VISUAL" name="desc" />
            <field type="LINE" name="sub_text" />
          </fields>
        </repeater>
      </repeaters>
    </widget>
    <widget name="pxl_contact_form">
      <fields>
        <field type="LINE" name="form_id" />
      </fields>
    </widget>
  </elementor-widgets>
</wpml-config>

NOTE: If the config.xml gives any errors please share them with me as I have not been able to test it on your environment, but it should work OK.

Once you add it go to the page in question, make a small edit and update, then check the translation again.
May 8, 2025 at 7:35 pm #17013628

sergejsF

Hi, thank you. But there are still problems. The interface does not let me save Custom XML. And there are errors on all lines. Maybe it is something to do with server permissions. Here is the screenshot: hidden link

And here is the full text of the error log:
Error
Line: 5, Column: 0
Element 'field', attribute 'name': The attribute 'name' is not allowed.
Line: 5, Column: 0
Element 'field': [facet 'minLength'] The value has a length of '0'; this underruns the allowed minimum length of '1'.
Line: 5, Column: 0
Element 'field': '' is not a valid value of the atomic type 'wpml-non-empty-string'.
Line: 6, Column: 0
Element 'field', attribute 'name': The attribute 'name' is not allowed.
Line: 6, Column: 0
Element 'field': [facet 'minLength'] The value has a length of '0'; this underruns the allowed minimum length of '1'.
Line: 6, Column: 0
Element 'field': '' is not a valid value of the atomic type 'wpml-non-empty-string'.
Line: 11, Column: 0
Element 'field', attribute 'name': The attribute 'name' is not allowed.
Line: 11, Column: 0
Element 'field': [facet 'minLength'] The value has a length of '0'; this underruns the allowed minimum length of '1'.
Line: 11, Column: 0
Element 'field': '' is not a valid value of the atomic type 'wpml-non-empty-string'.
Line: 16, Column: 0
Element 'field', attribute 'name': The attribute 'name' is not allowed.
Line: 16, Column: 0
Element 'field': [facet 'minLength'] The value has a length of '0'; this underruns the allowed minimum length of '1'.
Line: 16, Column: 0
Element 'field': '' is not a valid value of the atomic type 'wpml-non-empty-string'.
Line: 17, Column: 0
Element 'field', attribute 'name': The attribute 'name' is not allowed.
Line: 17, Column: 0
Element 'field': [facet 'minLength'] The value has a length of '0'; this underruns the allowed minimum length of '1'.
Line: 17, Column: 0
Element 'field': '' is not a valid value of the atomic type 'wpml-non-empty-string'.
Line: 22, Column: 0
Element 'field', attribute 'name': The attribute 'name' is not allowed.
Line: 22, Column: 0
Element 'field': [facet 'minLength'] The value has a length of '0'; this underruns the allowed minimum length of '1'.
Line: 22, Column: 0
Element 'field': '' is not a valid value of the atomic type 'wpml-non-empty-string'.
Line: 27, Column: 0
Element 'field', attribute 'name': The attribute 'name' is not allowed.
Line: 27, Column: 0
Element 'field': [facet 'minLength'] The value has a length of '0'; this underruns the allowed minimum length of '1'.
Line: 27, Column: 0
Element 'field': '' is not a valid value of the atomic type 'wpml-non-empty-string'.
Line: 32, Column: 0
Element 'field', attribute 'name': The attribute 'name' is not allowed.
Line: 32, Column: 0
Element 'field': [facet 'minLength'] The value has a length of '0'; this underruns the allowed minimum length of '1'.
Line: 32, Column: 0
Element 'field': '' is not a valid value of the atomic type 'wpml-non-empty-string'.
Line: 33, Column: 0
Element 'field', attribute 'name': The attribute 'name' is not allowed.
Line: 33, Column: 0
Element 'field': [facet 'minLength'] The value has a length of '0'; this underruns the allowed minimum length of '1'.
Line: 33, Column: 0
Element 'field': '' is not a valid value of the atomic type 'wpml-non-empty-string'.
Line: 35, Column: 0
Element 'repeaters': This element is not expected.
Line: 46, Column: 0
Element 'field', attribute 'name': The attribute 'name' is not allowed.
Line: 46, Column: 0
Element 'field': [facet 'minLength'] The value has a length of '0'; this underruns the allowed minimum length of '1'.
Line: 46, Column: 0
Element 'field': '' is not a valid value of the atomic type 'wpml-non-empty-string'.
May 9, 2025 at 5:41 pm #17017585

Bobby
WPML Supporter since 04/2015

Languages: English (English )

Timezone: America/Los_Angeles (GMT-07:00)

No it's an issue with my config.xml, I will adjust it for you.

I would like to request temporary access (wp-admin and FTP) to your site to test the issue.
(preferably to a test site where the problem has been replicated if possible)

**Before we proceed It is necessary to take FULL BACKUP of your database and your website. Providing us with access, you agree that a backup has been taken **

I often use the Duplicator plugin for this purpose: http://wordpress.org/plugins/duplicator/
You will find the needed fields for this below the comment area when you log in to leave your next reply.
The information you enter is private which means only you and I have access to it.

NOTE: If access to the live site is not possible and the staging site does not exist please provide me with a duplicator package created with the duplicator plugin.

Thank you,
Bobby
May 10, 2025 at 3:41 pm #17019223

Bobby
WPML Supporter since 04/2015

Languages: English (English )

Timezone: America/Los_Angeles (GMT-07:00)

Thank you for the access details!

I have updated the wpml-config.xml and it is working as expected now.

If you go to Services I can now see the rest of the content, please review and let me know your results.

<wpml-config>
  <elementor-widgets>
    <widget name="pxl_heading">
      <fields>
        <field type="LINE">title</field>
        <field type="LINE">sub_title</field>
      </fields>
    </widget>

    <widget name="pxl_text_editor">
      <fields>
        <field type="VISUAL">text_ed</field>
      </fields>
    </widget>

    <widget name="pxl_button">
      <fields>
        <field type="LINE">text</field>
        <field type="LINK">link</field>
      </fields>
    </widget>

    <widget name="pxl_icon">
      <fields>
        <field type="LINE">circle_text</field>
      </fields>
    </widget>

    <widget name="pxl_image_box">
      <fields>
        <field type="LINE">circle_text</field>
      </fields>
    </widget>

    <widget name="pxl_testimonial_carousel">
      <fields>
        <field type="VISUAL">desc</field>
        <field type="LINE">sub_text</field>
      </fields>
    </widget>

    <widget name="pxl_contact_form">
      <fields>
        <field type="LINE">form_id</field>
      </fields>
    </widget>
  </elementor-widgets>
</wpml-config>

P.S Regarding the other issue you mentioned with the latest version of WPML, this is something that I would encourage you to create a staging version or possibly letting our team create one and and testing the update there to review if the issue happens again and what might be causing it.

Please let me know if you would like me to open a split ticket about this for you or if you want to explore at a later time.

May 12, 2025 at 12:12 pm #17022831

sergejsF

Hi, thank you for the help. Can you please advise on how should we continue with those XML records? So we could complete the website ourselves.

Are those widgets registered only once per widget or per page?

Do you have any advice on the second issue we encountered with different headers on translated versions?

I am trying to get some explanations from the theme developer. But they seem not to understand how WPML works. When we purchased their theme stated that it supports WPML. Still trying to get more information from them.

May 12, 2025 at 9:41 pm #17024707

Bobby
WPML Supporter since 04/2015

Languages: English (English )

Timezone: America/Los_Angeles (GMT-07:00)

The wpml-config.xml that I have added seems to work well now, it is not needed to be adjusted you can use it as is.

Can you confirm that now when you open the editor the items are available for translation. (it worked for me when I tested)

If yes, then there is nothing more to do, you can continuue tranlsation as expected, and it's only needed to do this once and takes effect sitewide.

Nothing is needed from the developers unless of course they want to become compatible with WPML they can reach out to our team directly via this link:
https://wpml.org/documentation/support/go-global-program/

How are the headers created? Are they coming from the theme?

May 13, 2025 at 12:26 pm #17027401

sergejsF

Hi, yes the edits that you have made are working perfectly. But those were only records from one page: Services.
But how do we add the rest of the widgets from other existing and future pages?

I can see the logic behind what you did. And I guess we could do the rest ourselves. I just need to understand where we get those records for other widgets and do we add them via backend or via FTP?

The headers are coming from the theme, yes. In my experience, usually you would need to go to page settings in each langueage and adjust them. But in this case it does not show on the frontend. even though we have changed the settings for those pages in each language separately.

May 13, 2025 at 5:06 pm #17029263

Bobby
WPML Supporter since 04/2015

Languages: English (English )

Timezone: America/Los_Angeles (GMT-07:00)

Hi there,

The config.xml does not need to be created for each page it's created based on the elements used, elementor elements are compatible, therefore we just need it for the theme created ones.

there is a chance some elements are possibly missing from the one I added (I tried to add as many as I could 🙂 )

You can see the breakdown of how to do this here, also we have an add-on tool that can help you do this.
https://wpml.org/documentation/support/language-configuration-files/

Another option is to let our team know in the case that you run into specific elements that are not added and we can further help.

----------_

Regarding the headings:

Go to WPML->Translation management->dropdown templates and My Templates, are you able to send them for translation and are those the correct templates?

once finished with the translation set within the theme settings the template for the default language and let me know your results, please.