This thread is resolved. Here is a description of the problem and solution.
Problem:
If you're experiencing a PHP error related to the WPML plugin with a warning like 'unserialize(): Error at offset 69 of 223 bytes in wp-includes/functions.php:650', it might be due to an issue with the WPML_Notices class.
Solution:
We recommend that you first ensure you have a full site backup. Then, update your WooCommerce and WPML String Translation to the latest versions, as these updates include fixes for similar issues. You can read more about the related improvements here: https://make.wordpress.org/core/2024/10/21/i18n-improvements-6-7/. After updating, clear all types of caches on your site to see if the problem resolves.
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. Should you need further assistance, please do not hesitate to open a new support ticket with us 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.
the last 3 errors are:
Caller Componente
Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the health-check 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. (This message was added in version 6.7.0.)
_load_textdomain_just_in_time()
Plugin: health-check
Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the login-customizer 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. (This message was added in version 6.7.0.)
_load_textdomain_just_in_time()
Plugin: login-customizer
Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the viva-wallet-for-woocommerce 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. (This message was added in version 6.7.0.)
_load_textdomain_just_in_time()
Plugin: viva-wallet-for-woocommerce
no other error from wpml
New threads created by Bigul and linked to this one are listed below:
Thank you for the feedback. Please note that I have opened a new ticket for the *function _load_textdomain_just_in_time* issue. As per our support policies, we can address only one issue per ticket. This approach helps us serve you better and avoid discussing multiple problems within a single ticket. I will respond to the new ticket shortly. Thank you for your understanding.
i follow the guide and I updated all plugins the error still there :
Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the health-check 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. (This message was added in version 6.7.0.)
_load_textdomain_just_in_time()
Plugin: health-check
Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the login-customizer 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. (This message was added in version 6.7.0.)
_load_textdomain_just_in_time()
Plugin: login-customizer
Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the viva-wallet-for-woocommerce 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. (This message was added in version 6.7.0.)
Can you help me?
New threads created by Bigul and linked to this one are listed below:
Thank you for the feedback. I have added a new ticket for this warning for easy follow-up and get back to you soon with the latest one. Please wait.
--
Thanks!
Bigul
Manage Cookie Consent
We use cookies to optimize our website and services. Your consent allows us to process data such as browsing behavior. Not consenting may affect some features.
Functional
Always active
Required for our website to operate and communicate correctly.
Preferences
The technical storage or access is necessary for the legitimate purpose of storing preferences that are not requested by the subscriber or user.
Statistics
We use these to analyze the statistics of our site. Collected information is completely anonymous.The technical storage or access that is used exclusively for anonymous statistical purposes. Without a subpoena, voluntary compliance on the part of your Internet Service Provider, or additional records from a third party, information stored or retrieved for this purpose alone cannot usually be used to identify you.
Marketing
These cookies track your browsing to provide ads relevant to you.
