evalhyn

Hello,
Thanks for your help. I've tested a lot of things over the past few days:
I've disabled almost all extensions except for security, WooCommerce, and newsletter.
I've also disabled Smash Balloon. Cleared caches, CSS, and JS
The WooCommerce errors are still there.
I deactivated the Salient theme and switched to the native theme.
Cleared caches, CSS, and JS
The WooCommerce errors are still there.
I activated the Salient theme.
I deactivated the Brevo (newsletter) plugin.
Cleared caches, CSS, and JS
I deactivated the Regenerate and Redirection plugins.
Cleared caches, CSS, and JS

What I notice is that the store pages are accessible on my site during all these tests (on another browser as well), except for the payment page.

But the bug still occurs as soon as I return to "Woocommerce > Home," and the WooPayment settings don't remain active.
Then I deleted all the WooCommerce extensions and removed the database components in WPoptimize.
I reinstalled WooCommerce, but not everything installed.

I tried to reinstall a backup via Updraftplus, but I couldn't complete it because it searched for the various modules for an hour. I couldn't start the reinstallation, so I canceled it.

So I reinstalled last week's FTP and database backup (OVH) to recover everything I had at that time, including WooCommerce, WooPayment, and everything else I had installed.
All the extensions are activated and the updates are complete.

There are two recurring messages:
WooCommerce > Home: "An error occurred while retrieving your inbox. Please try again."
If I try again, it takes me back to the beginning of the WooCommerce installation.

WooPayment > Settings:
"Error retrieving settings."
The settings are empty/deleted.

I also have this message in the header of the WooCommerce settings pages:
"An important update is required for WooCommerce" and "An important security update for WooCommerce has been released. It is recommended that you update as quickly as possible."
But everything is up to date (plugins, theme, WordPress).

Thank you for your help.

Hello,

Thank you for your reply.
Reading is open. Je partage le rapport.?https://pastebin.com/ni1VTbnF

I’m also sharing the latest fatal error report:

2025-03-14T15:09:24+00:00Critique Uncaught TypeError: json_decode(): Argument #1 ($json) must be of type string, array given in /home/evalhynfar/www/wp-content/plugins/instagram-feed/inc/Helpers/SB_Instagram_Tracking.php:175 Contexte supplémentaire{ “error”: { “type”: 1, “file”: “/home/evalhynfar/www/wp-content/plugins/instagram-feed/inc/Helpers/SB_Instagram_Tracking.php”, “line”: 175 }, “remote-logging”: true, “backtrace”: [ “”, “#0 /home/evalhynfar/www/wp-content/plugins/instagram-feed/inc/Helpers/SB_Instagram_Tracking.php(175): json_decode(Array, true)”, “#1 [internal function]: InstagramFeed\Helpers\SB_Instagram_Tracking::{closure:InstagramFeed\Helpers\SB_Instagram_Tracking::get_data():174}(Array)”, “#2 /home/evalhynfar/www/wp-content/plugins/instagram-feed/inc/Helpers/SB_Instagram_Tracking.php(174): array_map(Object(Closure), Array)”, “#3 /home/evalhynfar/www/wp-content/plugins/instagram-feed/inc/Helpers/SB_Instagram_Tracking.php(289): InstagramFeed\Helpers\SB_Instagram_Tracking->get_data()”, “#4 /home/evalhynfar/www/wp-includes/class-wp-hook.php(324): InstagramFeed\Helpers\SB_Instagram_Tracking->send_checkin()”, “#5 /home/evalhynfar/www/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters(”, Array)”, “#6 /home/evalhynfar/www/wp-includes/plugin.php(565): WP_Hook->do_action(Array)”, “#7 /home/evalhynfar/www/wp-cron.php(191): do_action_ref_array(‘sbi_usage_track…’, Array)”, “#8 {main}”, “thrown” ] }

Thank you for your help.
Valérie