Skip Navigation

This thread is resolved. Here is a description of the problem and solution.

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:

<wpml-config>
  <elementor-widgets>
    <widget name="nacharity_basic_button">
      <fields>
        <field>btn_text</field>
        <field>btn_link>url</field>
      </fields>
    </widget>
  </elementor-widgets>
</wpml-config>

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.

Alternatively, you can use the WordPress Editor for translation. Instructions can be found here: Using different translation editors for different pages.

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.

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.

No supporters are available to work today on this forum. Feel free to create tickets and we will handle it as soon as we are online. Thank you for your understanding.

This topic contains 1 reply, has 2 voices.

Last updated by Andreas W. 4 months, 1 week ago.

Assisted by: Andreas W..

Author Posts
May 18, 2024 at 10:33 am #15641687

moeschamara-tjitskeB

Hi, on several of my webpages there are buttons with a call for action on it, however the texts on those buttons did not translate on automatic translation and I also can't find the button texts in the editor to translate them myself. See for example on hidden link .

Of course it is necessary that the text on the buttons is also translated, so how can this be done? Either automatically or manually afterwards, both is fine just let me know how.

Thank you

Screenshot 2024-05-18 at 12.29.52.png
May 18, 2024 at 12:19 pm #15641786

Andreas W.
Supporter

Languages: English (English ) German (Deutsch )

Timezone: America/Lima (GMT-05:00)

Hello,

It looks like this button is coming from the plugin "Charity Addon for Elementor".

WPML by default supports all widgets that are shipped with Elementor and Elementor Pro.

Every Custom Elementor Widget must have an XML configuration so that it can be translated using the WPML Translation Editor.

In this case the config for the button must look like this:

<wpml-config>
  <elementor-widgets>
    <widget name="nacharity_basic_button">
      <fields>
        <field>btn_text</field>
        <field>btn_link>url</field>
      </fields>
    </widget>
  </elementor-widgets>
</wpml-config>

Add the config to WPML > Settings > Custom XML Configuration, then edit the widget on the original content, save the content, and open the translation.

On the WPML Translation Editor the button text should now be visible right away. To translate the link please type "http" inside the text field on the top left to find the URL.

It is the theme author's responsibility to create such a configuration for all the widgets in a wpml-config.xml file which needs to be placed in the root directory of the Elementor addon plugin.

Guide:
https://wpml.org/documentation/support/language-configuration-files/how-to-register-page-builder-widgets-for-translation/

We also provide the following plugin, which makes creating such a config easier, but we do not recommend using it in a production environment:
https://wpml.org/documentation/related-projects/wpml-compatibility-test-tools-plugin/

We can further offer a WPML test site on which we can recreate the issue and I assist you with a basic configuration for a couple of widgets, but if there are many affected widgets it would be better to reach the author of those widgets.

We offer a program for theme and plugin authors to support them on this matter which you could name as a reference to the author:
https://wpml.org/documentation/support/go-global-program/

---

Alternative: Use the WordPress Editor as the translation method instead.

Instructions for translating with the WordPress editor:
https://wpml.org/documentation/translating-your-contents/using-different-translation-editors-for-different-pages/

It would also be very helpful if you could send us the WPML information for troubleshooting.
More information about this here:
https://wpml.org/de/faq/provide-debug-information-faster-support/

If you are thinking about using a different Elementor Addons, take note that the following ones all include a wpml-config.xml file and are compatible with WPML:

Essential Addons for Elementor
JetElements for Elementor
Ultimate Addons for Elementor
Premium Addons for Elementor
ElementsKit
Happy Addons
Dynamic Content for Elementor
AnyWhere Elementor

Best regards
Andreas

May 18, 2024 at 2:14 pm #15641950

moeschamara-tjitskeB

Hi, thank you for your elaborate answer! I tried editing the page in Elementor and that turned out to work perfectly, so the issue is resolved, thank you. I will keep in mind your answer which I think is to have the automatic translation in the future, instead of manually like I did in this case?

moeschamara-tjitskeB confirmed that the issue was resolved on 2024-05-18 14:14:57.
This ticket is now closed. If you're a WPML client and need related help, please open a new support ticket.