This thread is resolved. Here is a description of the problem and solution.
Problem:
After updating to WordPress 6.7, you are seeing multiple PHP errors on your staging website when using the first language. The errors do not appear when switching to the second language. The errors mention that the function
_load_textdomain_just_in_time
was called incorrectly, indicating that translation loading for the cookie-law-info domain was triggered too early.
Solution:
We are aware of these notifications but could not determine if they are directly related to the WPML plugin. We recommend waiting for each plugin to address this notification. In the meantime, you can set the debug mode to false to prevent these notifications from being bothersome.
If this solution does not resolve your issue or seems irrelevant due to being 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 problem persists, please open a new support ticket at WPML support forum for further assistance.
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 4 replies, has 0 voices.
Last updated by 2 weeks, 3 days ago.
Assisted by: Andrey.
 |
Contesto del problema: after the WordPress 6.7, I see many, many errors PHP on my staging website, all the same. If I switch to the second language, everything is ok. All plug-in are updated to the last version: WPML Media Translation: 2.7.5 Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the cookie-law-info domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/customer/www/xxx.com/public_html/wp-includes/functions.php on line 6114 I don't know if these errors are related to WPML or to single plug-in. For example, WooCommerce and Yoast teams are already working to the fix. https://wordpress.org/support/topic/bug-with-the-latest-version-of-wp-6-7/ What should we do? Sintomi: Domande:  |
 Supporter Languages: English (English ) Russian (Русский ) Timezone: Europe/Kyiv (GMT+02:00) |
|
|
|
|
|
Supporter Languages: English (English ) Russian (Русский ) Timezone: Europe/Kyiv (GMT+02:00) |
|
 |