Deactivate MP6 on update to 3.8.

If left on, it introduces a lot of weird issues not easily diagnosed. MP6 will be updated before release to prevent itself from functioning 3.8+, but this will cut down on support requests by people who update core but not MP6, which was a fairly popular plugin.

fixes #26334.

Built from https://develop.svn.wordpress.org/trunk@26692


git-svn-id: http://core.svn.wordpress.org/trunk@26582 1a063a9b-81f0-0310-95a4-ce76da25c4cd

wp-admin/includes/upgrade.php

@@ -408,6 +408,9 @@ function upgrade_all() {
 	if ( $wp_current_db_version < 26148 )
 		upgrade_372();
 
+	if ( $wp_current_db_version < 26691 )
+		upgrade_380();
+
 	maybe_disable_link_manager();
 
 	maybe_disable_automattic_widgets();
@@ -1237,6 +1240,17 @@ function upgrade_372() {
 		wp_clear_scheduled_hook( 'wp_maybe_auto_update' );
 }
 
+/**
+ * Execute changes made in WordPress 3.8.0.
+ *
+ * @since 3.8.0
+ */
+function upgrade_380() {
+	global $wp_current_db_version;
+	if ( $wp_current_db_version < 26691 ) {
+		deactivate_plugins( array( 'mp6/mp6.php' ), true );
+	}
+}
 /**
  * Execute network level changes
  *

wp-includes/version.php

@@ -11,7 +11,7 @@ $wp_version = '3.8-RC1';
  *
  * @global int $wp_db_version
  */
-$wp_db_version = 26644;
+$wp_db_version = 26691;
 
 /**
  * Holds the TinyMCE version