[Plugin: WordPress SEO by Yoast] Another 3.4 MultiSite ERROR

Hi!

I get the same on a multisite install I just updated. Blog 1 and network admin pages are ok but blog 2 displays the error.

Same issue here, everything seems to be working OK but the error persists.

Warning: Invalid argument supplied for foreach() in /home/-site-/development/staging.-site-.com/wp-content/plugins/wordpress-seo/inc/wpseo-functions.php on line 407

I’m on latest version of WP and WPSEO, this is on my staging server which I run updates on before going live. As the other guys said, it only shows on sub-sites (blogs) not the main site (ID1).

This needs a fix soon. You can’t to like any actions. You get headers already sent out by trying to approve a comment, Update a post, Insert a Thumbnail. Please fix soon Joost. Thanks

Same here. Come on, Joost, give us a quick fix, man (although, quite frankly, this is mainly an annoyance, not a real problem).

Oh, while you’re at it, the plugin is also ignoring when I tell it to stop bugging me about my new site not being visible to search engines. A fix for that little gem would be great too.

I’m getting the same error message but the error is also preventing me from installing other plugins on my site.

I was getting the same error.

if ( version_compare( $current_version, '1.2.3', '<' ) ) {
		$opt = get_option('wpseo');

		foreach ( $opt as $key => $val ) {
			if ( !in_array( $key, array('ignore_blog_public_warning', 'ignore_tour', 'ignore_page_comments', 'ignore_permalink', 'ms_defaults_set', 'version', 'disableadvanced_meta', 'googleverify', 'msverify', 'alexaverify') ) ) {
				unset( $opt[$key] );
			}
		}

		update_option('wpseo', $opt);
	}

It seems that the one that’s causing the error are the options. The $opt variable above is trowing a string when it’s supposed to be an array. The only fast way that I’ve seen is by updating the settings on the Yoast WordPress SEO dashboard.

Wow, that actually worked, although when I updated the option on the SEO dashboard page, I got an even scarier error. I went back, refreshed and all was well.

Thank you, @lucentx!