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.
Background of the issue:
I am experiencing a PHP error on my site hidden link. I received a warning on all pages related to the WPML plugin. The warning is: unserialize(): Error at offset 69 of 223 bytes in wp-includes/functions.php:650. The error seems to be related to the WPML_Notices class in the WPML plugin.
Symptoms:
Warning unserialize(): Error at offset 69 of 223 bytes in wp-includes/functions.php:650.
Questions:
How can I resolve the unserialize() error in WPML?
Is there a way to prevent this warning from appearing on all pages?
To enable the WordPress Debug log, open your wp-config.php file of site root and look for define('WP_DEBUG', false);. Change it to:
// Enable WP_DEBUG mode
define( 'WP_DEBUG', true );
// Enable Debug logging to the /wp-content/debug.log file
define( 'WP_DEBUG_LOG', true );
// Disable display of errors and warnings
define( 'WP_DEBUG_DISPLAY', false );
@ini_set( 'display_errors', 0 );
The errors will be saved to a debug.log log file inside the */wp-content/* directory. Please do the steps to reproduce the bug and check if you are getting any errors or warnings related to WPML in the log file.
If you can paste your debug.log to http://pastebin.com/index.php and provide me that link it would be great! (This is the cleanest way because sometimes the logs are long and create a complete mess of discussion).
Thank you for the Debug.log details. This looks like a compatibility issue. So if you have a staging/dev site (a clone copy of the live), please try the following steps to track this bug.
a) Backup your site first[Mandatory]
b) Switch for a moment to a WordPress default theme like 2024 or Avada Parent theme
c) Deactivate all the plugins that are not related to WPML
d) Then check whether the issue exists or not
e) If the issue is gone, activate the plugins as a group of three or four to find which one has an interaction issue
f) Switch back to the original theme of the site
Thank you for the updates. Please fill in the private details fields after a full site backup. I would like to access the admin area of your site for further checking. Refer to the following links for more details about our private information sharing policies.
Thank you for the details and login information. Please upgrade to the latest version of WooCommerce and WPML String Translation after a full site backup {mandatory}, It has included the fix for the issues related to - https://make.wordpress.org/core/2024/10/21/i18n-improvements-6-7/
Then clear all types of caches and check whether any difference in the result.
If the problem remains, please allow me to make a duplicator copy of your site using the Duplicator plugin (https://wordpress.org/plugins/duplicator/) for debugging the issue on my local server. So we can troubleshoot the issue without affecting your live site.
Thank you for the updates. Can you create a staging site (a clone copy of the live site) for our testing? So we can troubleshoot the bug without affecting the live site.
how i wrote before : I cant do site copy with users data for the GDPR (EU users data rules) , Is there a way to copy site without users data? let me know.
Thank you for the updates. Have you made any changes to the site now?
Please note that there are chances for conflicts while making a copy of the site without the wp_users & wp_usersmeta database tables. It is inter related to the wp_posts table. Refer to this image for more details - https://codex.wordpress.org/File:WP4.4.2-ERD.png
absolutely nothing, just cleaned htaccess file but i dont think is related. Im looking log files and i sow that when wpml error is gone is appear another strange server error. Im investigate about. keep u update. thanks
