iDope

Yes

I mean, the problem seems to be that the programmer expects $option to still have the same value while in reality it has been overridden in the foreach statement.

That is correct but you need to get the latest value of ‘wpseo’ before updating it. That’s why this line is needed
$option = get_option( 'wpseo' );

Alternatively, you could set $option['ms_defaults_set'] = true; within the foreach loop when the option key is ‘wpseo’;

@james Olney: I think your issue is different. Mine is the Fatal error in class-admin.php on line 440 which some people have been getting.

See this thread for a proper fix to this. Hopefully the author includes this in an update.

One more thing, you will need to delete the bad ‘wpseo’ setting that has been saved to the db. Using phpMyAdmin or something similar logon to your db and open the wp_{blogid}_options table (where {blogid} is the blog id of the blog which is giving the error). Look for a ‘wpseo’ option (it should have the value ‘1pseo_social’) and delete it.

See this thread for a proper fix to this.

Please see this for a fix

This is how it should look like after the fix:

function multisite_defaults() {
		$option = get_option( 'wpseo' );
		if ( function_exists( 'is_multisite' ) && is_multisite() && !is_array( $option ) ) {
			$options = get_site_option( 'wpseo_ms' );
			if ( is_array( $options ) && isset( $options['defaultblog'] ) && !empty( $options['defaultblog'] ) && $options['defaultblog'] != 0 ) {
				foreach ( get_wpseo_options_arr() as $option ) {
					update_option( $option, get_blog_option( $options['defaultblog'], $option ) );
				}
			}
			$option = get_option( 'wpseo' );
			$option['ms_defaults_set'] = true;
			update_option( 'wpseo', $option );
		}
	}

Agreed. I have no issues with plugin developers charging for premium versions with new features. Charging for bug fixes is plain wrong.

Thanks… haven’t worked on my plugins for a while though.

This has been fixed.

Can you update to the latest version and try again?

I left a block of test code it it by mistake that would explain the code in the header (fixed in the latest version). But there should not be any 404 errors.

Details?

Please try the latest 0.9 version.

Its back up now.