Big error on Dashboard after update

It may be related to the known plugin issue. Please follow the guidelines provided. If the issue still persists, please let us know.

I’ve done everything asked in the manual update, and am now getting these messages:

Warning: require(/home/rt66news/public_html/wp-includes/load.php) [function.require]: failed to open stream: No such file or directory in /home/rt66news/public_html/wp-settings.php on line 21

Fatal error: require() [function.require]: Failed opening required ‘/home/rt66news/public_html/wp-includes/load.php’ (include_path=’.:/usr/lib/php:/usr/local/lib/php’) in /home/rt66news/public_html/wp-settings.php on line 21

OK … I saw that WP-includes and WP-admin were in the wrong place. I moved them to the proper public_html, and now I’m getting the old message:

Fatal error: Call to undefined method dbrc_wpdb::delete() in /home/rt66news/public_html/wp-includes/option.php on line 370

Tracked down the code on line 370 at option.php:

$result = $wpdb->delete( $wpdb->options, array( ‘option_name’ => $option ) );

Full context from lines 363 to 379:

wp_protect_special_option( $option );

// Get the ID, if no ID then return
$row = $wpdb->get_row( $wpdb->prepare( “SELECT autoload FROM $wpdb->options WHERE option_name = %s”, $option ) );
if ( is_null( $row ) )
return false;
do_action( ‘delete_option’, $option );
$result = $wpdb->delete( $wpdb->options, array( ‘option_name’ => $option ) );
if ( ! defined( ‘WP_INSTALLING’ ) ) {
if ( ‘yes’ == $row->autoload ) {
$alloptions = wp_load_alloptions();
if ( is_array( $alloptions ) && isset( $alloptions[$option] ) ) {
unset( $alloptions[$option] );
wp_cache_set( ‘alloptions’, $alloptions, ‘options’ );
}
} else {
wp_cache_delete( $option, ‘options’ );

Deleting the db.php file did the trick. Lord, that thing really was messing it up.

Glad to know, that fixed the issue.

I had the same and it shocked me, i found the fix here : [Solved] Fatal Error While Updating Database WordPress 3.4 Update

The plugin causing this issue, DB Cache Reloaded Fix, has been updated to support 3.4. You can re-enable it after updating if you disabled it in the meanwhile.