Skip Navigation

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

Problem:
After updating to WordPress 6.7, certain language translations, specifically Estonian and Russian, were not displaying correctly on the client's live e-commerce site. Despite being correctly configured in the String Translation module, some sections like the footer showed English instead of the intended languages.
Solution:
We initially suggested checking and re-saving the translations for the affected strings in WPML->String Translation. When this did not resolve the issue, we requested access to the site to investigate further. Our investigation revealed that the issue was related to a known problem introduced in WordPress 6.7, affecting string translations. We escalated this to our compatibility team for further analysis. Meanwhile, we advised the client to update to the latest version of WordPress as soon as it was available, which resolved the issue. We also recommended enabling the option 'Automatically load the theme's .mo file using

load_textdomain

' in WPML->Theme and Plugins Localization, which corrected the translation display.

Please note that this solution might be irrelevant if it's outdated or not applicable 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 issue persists, please open a new support ticket at WPML support forum.

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.

This topic contains 20 replies, has 2 voices.

Last updated by Bobby 7 months, 2 weeks ago.

Assisted by: Bobby.

Author Posts
November 21, 2024 at 1:55 am #16427030

Bobby
WPML Supporter since 04/2015

Languages: English (English )

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

Hello,

Yes, I am doing a double check on your specific situation to exclude a possible compatibility issue, however at the moment i am 99% confident this is caused by the WP 6.7 introduced issues discussed here.

https://wpml.org/errata/missing-translations-on-front-end/

WP 6.7 has introduced many issues related to such cases but as this is a woodmart theme site i want to be 100% sure. I will have results in the next 30 minutes most likely and will update you

November 21, 2024 at 6:45 pm #16430812

Bobby
WPML Supporter since 04/2015

Languages: English (English )

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

Hello,

Please update to the latest version of WP and let me know your results, they team just released it today and on my testing, it looks like it resolves the issue.

November 21, 2024 at 9:50 pm #16431175

faridi-3

Hello,
The problem has been solved on the home page, only when you switch to the store page it goes back to English

November 21, 2024 at 11:37 pm #16431329

Bobby
WPML Supporter since 04/2015

Languages: English (English )

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

Thank you for updating me! I have another similar case that we are looking into with our compatibility team that might be related to what you are experiencing.

I will take a look and update you as soon as I have some updates.

In the meantime please make sure to clear your cache as well as any server related caching or drop in cache and let me know your results.

November 22, 2024 at 4:27 pm #16434719

faridi-3

Hi, I did everything you said but nothing changed.

November 22, 2024 at 9:36 pm #16435351

Bobby
WPML Supporter since 04/2015

Languages: English (English )

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

Hi there,

I just got some feedback based on the issue I mentioned and it does seem like the 2 are correlated.

Please review now and let me know your results.

When I view it I can now see the translation in the shop as well.

To resolve I did the following:

Go to WPML-> Theme and Plugins localization and check the box for Automatically load the theme's .mo file using 'load_textdomain' , once that was enabled the translation was showing as expected.