Skip Navigation

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.

WordPress 6.7 has introduced a new issue that impact translations, please update WooCommerce and WPML to the latest versions before you report issues. More about this here - https://wpml.org/errata/php-error-wp-6-7-notice-function-_load_textdomain_just_in_time-was-called/
Sun Mon Tue Wed Thu Fri Sat
- 8:00 – 13:00 9:00 – 13:00 9:00 – 13:00 8:00 – 12:00 8:00 – 12:00 -
- 14:00 – 17:00 14:00 – 18:00 14:00 – 18:00 13:00 – 17:00 13:00 – 17:00 -

Supporter timezone: Europe/Zagreb (GMT+01:00)

Tagged: 

This topic contains 0 replies, has 0 voices.

Last updated by Bruno Kos 5 days, 16 hours ago.

Assisted by: Bruno Kos.

Author Posts
November 22, 2024 at 8:20 am

olgaS-13

Background of the issue:
I have translated the global header using the DonDivi DiviMenu module on my site hidden link. I have also translated the corresponding Divi layouts for the submenus, including Welding, Surface Technology, and Contact.

Symptoms:
The translation is not displayed, and the original German text is shown instead.

Questions:
Why is the translated text not displaying for the submenus?
Is there a specific setting in WPML that I need to adjust for the DiviMenu translations?

November 22, 2024 at 9:37 am
November 22, 2024 at 9:38 am #16432924

Bruno Kos
Supporter

Languages: English (English ) German (Deutsch ) French (Français )

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

Let me know if DonDivi support is aware of this issue or if they need help from our https://wpml.org/documentation/support/go-global-program/ team.

November 28, 2024 at 9:02 am #16453668

olgaS-13

I got the following reply from DonDivi:

"""
Hello Werner,
We have included a WPML config XML file in the root of the plugin folder to tell WPML which fields need translation.
Reference: https://wpml.org/documentation/support/language-configuration-files/
We were asked to do that in order for DiviMenus to be compatible with the WPML plugin.
Since you have translated the Menu Item texts, the XML file seems to work as expected to translate our plugin output.
However, it looks like that the Divi Layout field has to be added so you can change the layout ID for the translated language layout ID.
I’m not sure about this since we are following the WPML documentation and we don’t know well that plugin, but we can try it.
In order to change the layout ID, I have added support for the Divi Layout field (popup layouts and sub layouts) to the XML file.
Please paste and replace the wpml-config.xml file located in the DiviMenus folder. Download link:
hidden link
We have included this line:
<attribute>sub_layout</attribute>
According to the WPML documentation, you can manually update the XML file via the plugin options (see link above), so you can do that in case that you can’t copy the updated file in the server.
And I’m afraid that’s all that we can do for now. Please, let us now if this solution works for you in order to keep this changes in the XML file. Otherwise, we’ll check out the WPML Compatibility Program and will try to find out what’s happening with the layouts.
Hope the updated XML file helps you. Thank you!
"""

It seems to me, that the layout ID should be automatically translated.

Do you think the suggested edit of the config file will help?

Thanks an best regards

November 28, 2024 at 1:22 pm #16455293

Bruno Kos
Supporter

Languages: English (English ) German (Deutsch ) French (Français )

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

I am not sure where that ID would be stored and where would we translate it. I added it and resaved hidden link, but there are no new fields within.

The thing is that values for the menu are translated, so the issue is elsewhere I believe.

We can either go through our Compatibility team by testing this in sandbox, or you can ask their developers to apply here https://wpml.org/documentation/support/go-global-program/ so our Compatibility and their developers can find a more permanent solution.