Skip Navigation

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

Problem:
The client's products are not visible on the Korean website. This issue arises because the 'HT Mega – Absolute Addons for Elementor' does not include compatibility code for WPML, affecting the translation of its widgets.
Solution:
To make the Tabs widget translatable, add the following custom XML configuration in WPML > Settings > Custom XML Configuration tab. The config can be found in this comment.

After adding this configuration, edit the Tabs widget on the original content, save the page, and then open the WPML Translation Editor.
For Widgets that are using Elementor Templates, add the following code inside includes\widgets\htmega_tabs.php at line 1050:

$item['template_id'] = apply_filters('wpml_object_id', $item['template_id'], 'elementor_library');

This ensures the correct template loads in each language.

If the theme or plugin author has not provided a wpml-config.xml file, you can create one yourself and store it under WPML > Settings > Custom XML Configuration. For further guidance on registering page builder widgets for translation, visit https://wpml.org/documentation/support/language-configuration-files/how-to-register-page-builder-widgets-for-translation/

Alternatively, consider using the WordPress Editor as the translation method. Instructions can be found here: https://wpml.org/documentation/translating-your-contents/using-different-translation-editors-for-different-pages/

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. If issues persist, please open a new support ticket at https://wpml.org/forums/forum/english-support/.

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.

Tagged: 

This topic contains 4 replies, has 3 voices.

Last updated by michaelD-80 4 weeks, 1 day ago.

Assisted by: Andreas W..

Author Posts
November 14, 2024 at 1:10 am #16400304

michaelD-80

Background of the issue:
I registered the product, and it displays correctly on the English website. All Korean translations have also been registered.

Symptoms:
The product is not visible on the Korean website.

Questions:
How can I make sure that my products are displayed the same way on the Korean homepage?

November 14, 2024 at 8:32 am #16401132

Laura
Supporter

Languages: English (English ) Italian (Italiano )

Timezone: Europe/Rome (GMT+01:00)

Hi,

thanks for contacting us.

Before we continue debugging your issue, please update WPML to version 4.6.14. The version you're currently using is not compatible with WordPress 6.7 and that may be the cause of your problem.

November 18, 2024 at 9:59 am #16413979

michaelD-80

Hello,

I'm already updated to the latest version. Please tell me what to do next.

스크린샷 2024-11-18 오후 6.58.31.png
November 18, 2024 at 9:03 pm #16416532

Andreas W.
Supporter

Languages: English (English ) Spanish (Español ) German (Deutsch )

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

Hello,

Please go to WPML > Settings > Taxonomy Translation and make sure that "Product Categories" are set to "Translatable only show translated items".

Screenshot:
https://wpml.org/documentation/getting-started-guide/translating-post-categories-and-custom-taxonomies/#setting-taxonomy-terms-to-be-translatable

Now, you should be able to translate the product categories at WPML > Taxonomy translation. If the categories are not translated you will not be able to filter the translated products by category.

If this will not solve the issue, please let me know.

Best regards
Andreas

November 19, 2024 at 12:20 am #16417135

michaelD-80

Hello,

The setup is already complete.
I'm attaching a screenshot.

Please help!

스크린샷 2024-11-19 오전 9.16.47.png
November 19, 2024 at 10:16 am #16418694

Andreas W.
Supporter

Languages: English (English ) Spanish (Español ) German (Deutsch )

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

Hi,

I'm happy to offer to take a closer look.

I would like to request temporary access (wp-admin and FTP) to the site to investigate the issue further.

The required fields are below the comment section when you log in to leave the next reply. The information you provide is private, meaning only you and I can see and access it.

IMPORTANT
Please be sure to back up the site and database before granting us access.

If you can't see the "wp-admin / FTP" fields, your post and site login details will be set to "PUBLIC". DO NOT publish the data unless you see the required wp-admin / FTP fields.

The private reply form looks like this:
hidden link

The next time you reply, click on "I still need assistance".

Video:
hidden link

Please note that we are obliged to request this information individually on each ticket. We are not allowed to access any credentials that were not specifically submitted on this ticket in the private response form.

Best regards
Andreas

November 26, 2024 at 8:37 am #16443250

Andreas W.
Supporter

Languages: English (English ) Spanish (Español ) German (Deutsch )

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

There was an issue with the WP MEMORY LIMIT on your site which I have solved now.

I had not issue with completing the translation of the homepage after that. Please update the missing translations now.

In case you need further assistance, please provide an example about a section or page that is causing issues with its translation.

memory.jpg
November 27, 2024 at 1:34 am #16447195

michaelD-80

I've already completed the Korean translation, but it's not showing up.
Please help!

스크린샷 2024-11-27 오전 10.32.46.png
November 27, 2024 at 10:05 am #16448483

Andreas W.
Supporter

Languages: English (English ) Spanish (Español ) German (Deutsch )

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

I am not sure what you are exactly expecting to see. I see the same Korean content on the WPML Translation Editor, as I do on Frontend.

See screenshots.

Could you please provide an exact example?

The only difference is that the layout is not respected, which seems to be an issue with the Classic Translation Editor's WYSIWYG field.

translation editor.jpg
frontend.jpg
November 28, 2024 at 5:12 am #16452254

michaelD-80

I have attached a screenshot.

On the English page, the product list appears in the tab menu,
but on the Korean page, the product list does not appear.

스크린샷 2024-11-28 오후 2.07.21.png
스크린샷 2024-11-28 오후 2.07.04.png
November 28, 2024 at 11:12 am #16454535

Andreas W.
Supporter

Languages: English (English ) Spanish (Español ) German (Deutsch )

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

The "Parts" page only seems not to work for Korean.

If I try to edit one of the "Parts" posts in any language different than English I get this message:

"You attempted to edit an item that doesn't exist. Perhaps it was deleted?"

I see the same issue for the Custom Posts in other languages, just with the difference that those are actually showing up on the archive templates.

I can confirm that the issue disappears once I disable WPML but at this point I am not sure why the issue occurs.

I took a copy of the site using "All In One WP Migration" to investigate this issue further.

---

Please also take note of the following:

We suggest to translate custom posts created with PODS only by using the WordPress-Editor as translation method.

This means, when editing one of the English "Parts" you need to set the "WordPress-Editor" as translation method inside the right sidebar of the WordPress Editor.

A dialog will show up. Select here to set this translation method for all posts of the same type.

More details about PODS:
https://wpml.org/plugin/pods-custom-content-types-and-fields/

How to translate with the WordPress-Editor:
https://wpml.org/documentation/translating-your-contents/using-different-translation-editors-for-different-pages/

November 28, 2024 at 1:15 pm #16455254

Andreas W.
Supporter

Languages: English (English ) Spanish (Español ) German (Deutsch )

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

1) The issue with the filters on the "Parts" page seems to be a compatilbity issue with "HT Mega – Absolute Addons for Elementor". I will try to recreate this issue on a new test site so that we can take further steps.

2) I can not confirm the second issue on my test site. Here I have no issue with editing translated CPTs on the WordPress Editor.

November 28, 2024 at 10:40 pm #16457145

Andreas W.
Supporter

Languages: English (English ) Spanish (Español ) German (Deutsch )

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

Hello,

The issue here is, that "HT Mega – Absolute Addons for Elementor" is not including any compatibilty code for WPML and this is why you will have issues translating its widgets with the WPML Translation Editor.

WORKAROUND:

Example for Tabs Widget:

Added this config at WPML > Settings > Custom XML Configuration (tab) to make the Tabs widget translatable.

<wpml-config>
  <elementor-widgets>
    <widget name="htmega-tab-addons">
      <fields>
        <field>htmega_tabs_list</field>
      </fields>
      <fields-in-item items_of="htmega_tabs_list">
        <field>tab_title</field>
       <field>custom_content</field>       
      </fields-in-item>
    </widget>
  </elementor-widgets>
</wpml-config>

After that you will still need to edit the Tabs widget on the original content, save the page and then open the WPML Translation Editor.

For the issue with the Elementor Templates:

Inside includes\widgets\htmega_tabs.php in line 1050 add:

$item['template_id'] = apply_filters( 'wpml_object_id', $item['template_id'], 'elementor_library' );

This will make sure that the correct template will get loaded in each language, as each template in each language has a different post_id.

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

It is the theme author's responsibility to create such a configuration in a wpml-config.xml file in the root directory of the theme or plugin. Further it is the responsibiity to apply WPML hooks when needed, to make the plugin work with WPML.

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/

If the author does not provide such a config, you can alternatively create one yourself. This config can be stored under WPML > Settings > Custom XML Configuration.

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/

Best regards
Andreas

November 29, 2024 at 4:24 am #16457499

michaelD-80

Thank you for your support so far.