Errors in WordPress log

Hi there

it seems that there was a problem during db update process

My suggetion here is to manually trigger update procedure
In order to do so, visit /wp-admin/options.php, locate option yith_wcwl_db_version, change value to 2.0.0 and save your options

This should force plugin to update database again: if everything is fine, option will automatically revert to 3.0.0 value

Let me know if this solves the issue

@apollo13themes If you need to do the same on a large number of sites of a network, I suggest you to proceed using a snippet of code

For example, the following code

function yith_wcwl_force_db_update_on_all_blogs(){
	if( ! isset( $_GET['yith_wcwl_force_db_update_on_all_blogs'] ) ){
		return;
	}

	$blogs = get_sites();

	if( ! empty( $blogs ) ){
		foreach( $blogs as $blog ){
			switch_to_blog( $blog->blog_id );
			echo 'Updating option on blog ' . $blog->blog_id . "... ";
			update_option( 'yith_wcwl_db_version', '2.0.0' );
			echo ' option updated!<br>';
			restore_current_blog();
		}
	}

	die;
}
add_action( 'init', 'yith_wcwl_force_db_update_on_all_blogs' );

will cycle through all defined blogs and update option for each one of them.
Then, on next visit, blog will automatically perform update process

In order to execute the previous code, place it at the end of functions.php, and visit any page of your network, adding ?yith_wcwl_force_db_update_on_all_blogs to the querystring

Don’t forget to remove this code immediately after you’re done, and avoid executing it multiple times

Finally, a note on performance: depending on how many sites your network has, this function could take a lot of time, and even failing due to Max Execution Time reached.
Be warned of the risk

@albertramsbottom if the solution that I suggested do not solve the issue, my best guess is that something is preventing automatic update procedeure do update db structure

Please, check your table structure on db, and dobule check that session_id column was actually created in yith_wcwl_lists table; if it is not, try to manually add it (at least for one blog) defining it as VARCHAR(255) NULL column, and check if this solves the issue (maybe you could ask your hosting provider to help with this task, if you don’t feel confortable checking db structure on your own)

@apollo13themes Glad to hear that you solved the problem, and that you appreciated my code 🙂
Let me know if I can be of further assistance

@albertramsbottom This is the reason why this topic wasn’t set as solved 🙂
Had you the chance to perform the tests that I suggested in my previous answer?