How to fix broken upgrade to 3.1

As soon as i saw the message on WPSE about the 3.1 release i immediately went a did a switch on my local installation(SVN switch).

Only issue is the wp-settings.php is trying to include a non-existant file.

Read More

Basically i’m stuck seeing the following two error messages.

Warning: require(MYPATH/wp-includes/classes.php) [function.require]: failed to open stream: No such file or directory in MYPATHwp-settings.php on line 68

Fatal error: require() [function.require]: Failed opening required ‘MYPATH/wp-includes/classes.php’ (include_path=’.;MYPATH/usr/local/php/includes;MYPATH/local/php/pear;MYPATH/home/admin/www/plugins/pear/PEAR’) in MYPATHwp-settings.php on line 68

MYPATH is actually a real path, i’ve removed that from the above quoted errors.

3.1 does not contain any such file, and i’ve checked my trunk installation to confirm(it’s not in trunk). So what’s the deal, why is the settings file still trying to include this file? Maybe an oversight with the release?

I could go grab a copy from 3.0.5, just want to hear what you guys have to say first(had this problem yourself?).

Looks like this is a local issue, i should be getting an updated wp-settings.php file, but for some reason SVN up is giving me an older copy(must be some caching issue somewhere, i assume).

I’ll update the question if i figure out the problem.

UPDATE
No idea why, but seems the switch didn’t quite take, wiping the svn folders and doing the checkout procedure again(like i first did when i set the directory to pull from the SVN) seems to have resolved the problem.

Related posts

Leave a Reply

2 comments

  1. There is no reference to ‘classes.php’ anywhere in the WP codebase, either in the 3.1 branch or in trunk.

    You probably have a modified version. Do a ‘svn stat’ and then a ‘svn diff’.

  2. You failed to update the files in the root of WordPress. I don’t know why, but a lot of people make this simple mistake.

    It is not enough to upgrade only the wp-admin and wp-includes directories. The files in the root directory, such as wp-settings.php and all the other wp-* files there, also must be upgraded.

    WordPress 3.1 no longer contains a wp-include/classes.php file, and the wp-settings.php file from 3.1 doesn’t try to load it.