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
- - 9:00 – 18:00 9:00 – 18:00 9:00 – 18:00 9:00 – 18:00 9:00 – 18:00
- - - - - - -

Supporter timezone: America/Lima (GMT-05:00)

This topic contains 12 replies, has 2 voices.

Last updated by Andreas W. 6 hours, 11 minutes ago.

Assisted by: Andreas W..

Author Posts
November 14, 2024 at 2:25 pm #16403393

georgiT-5

Background of the issue:
We are currently using WPML to translate our website at hidden link but have encountered issues with missing translations in certain sections, despite having translated these strings through WPML's string translation tool. When we enable the 'Look for strings while pages are rendered' option, the translations appear correctly. However, if we disable this option, the translations revert to their original untranslated state. We have already tried clearing the WPML cache from the troubleshooting menu and have also synced all links.

Symptoms:
Not loading all the translations.

Questions:
Could you please advise on any further steps or configurations to ensure our translations display correctly without having to keep the 'Look for strings' option active?

November 15, 2024 at 9:52 am #16406903

georgiT-5

Could you please advise on any further steps or configurations to ensure our translations display correctly without having to keep the 'Look for strings' option active?

November 15, 2024 at 2:13 pm #16408776

georgiT-5

And we have the same problem with the new WP 6.7. After the update alot of translations are not working. Woocommerce emails are not translated.

November 15, 2024 at 11:23 pm #16410020

Andreas W.
Supporter

Languages: English (English ) German (Deutsch )

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

Hello,

This might not be a WPML issue, as WordPress 6.7 changed how language files and translations are handled and there is a known issue in reagrds to WooCommerce.

Please read this:
hidden link

Possible workaround:
Rollback WordPress to the earlier version (Not tested)

If you think that this issue is not related, please let me know.

Best regards
Andreas

November 18, 2024 at 7:22 am #16413001

georgiT-5

Hello we dont know what the issue is. We have a secound client hotfarm.eu and we see a separate problem.

We translate the Menu button in Woocommerce using WPML.

The original translation translatest Menu to Навигация, but we want to change it to Меню and the moment we do that all the translations brake. If we return the original translations all is fine and well.

November 18, 2024 at 10:16 am #16414063

georgiT-5

Hello again,
About the Developer advisory. We dont get any errors in the admin panel but the translations dont initialize on the front end

November 18, 2024 at 2:17 pm #16415220

Andreas W.
Supporter

Languages: English (English ) German (Deutsch )

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

Do I understand right, that the site default language is Russian and you are trying to change a original string on WooCommerce?

If so, please take note that this is very likely not a WPML issue. You can confirm this by disabling WPML and our addons. If the issue persists, then it is not a WPML issue.

(Take note that you might need to change the WordPress default language to Russian once you disable WPML)

Also, please take note again of the following known issue that will be solved the upcoming WooCommerce update:
hidden link

November 18, 2024 at 5:47 pm #16416252

Andreas W.
Supporter

Languages: English (English ) German (Deutsch )

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

Take kindly note that we investigate this issue further and published the following errata:
https://wpml.org/errata/php-error-wp-6-7-notice-function-_load_textdomain_just_in_time-was-called/

Updating WPML and WooCommerce should solve the issue, unless another third plugin is casuing issues.

the upcoming WordPress Update should solve the issue after all.

November 19, 2024 at 6:43 pm #16421095

georgiT-5

Hello, No both of the website main language is Bulgarian.

We made a copy of quanta.keyweb.bg and did a wp rollback.
All the translations work fine. We cant do the same with Hotfarm.eu.

If you want we can provide an account to acces quanta stage website for testing.

About "Updating WPML and WooCommerce should solve the issue, unless another third plugin is casuing issues"
Each month at 15-th we do updates. After updating the WP Core and plugins we don't see improvement.

November 19, 2024 at 6:52 pm #16421118

georgiT-5

We tried some of the fixes but no luck :
https://core.trac.wordpress.org/ticket/62337

We use Woodmart and we have alot of websites with that theme. We still dont know if the problems is with WPML or WP. The only thing we know is if we roll back to 6.6.2 version of WP all of the translations work.

November 19, 2024 at 7:30 pm #16421287

Andreas W.
Supporter

Languages: English (English ) German (Deutsch )

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

As mentioned, this is not really a WPML issue.

Each theme and plugin will need to make sure to adapt their code, as WordPress 6.7 changes the way about how textdomains are loaded.

This would be a topic for the Woodmart Support maybe.

Did you try this workaround?
https://core.trac.wordpress.org/ticket/62337#comment:19

November 22, 2024 at 8:48 am #16432467

georgiT-5

We will try to contact Woodmart too. After the update of WP 7.6.1 some of your website with woodmart got fixed. But some of them didnt. And yes we did tested the manualf fix with no luck

November 22, 2024 at 5:05 pm #16434825

Andreas W.
Supporter

Languages: English (English ) German (Deutsch )

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

Yes, the latest WordPress update 7.6.1. should usually solve the issue.

If you are still experiencing issue, this might be a topic for the Woodmart support team. I am sure they must be already aware of this problem and might be able to provide you with a quick workaround.