I tried it again and now the error is:
Fatal error: Call to undefined function wp_remote_request() in /home/briayers/public_html/wp-includes/update.php on line 58
There is a quite short list of the files which are actually changed to go from 2.6 to 2.7.
If you have it backed up at 2.6 and can locate that list (I threw my printed copy away a month ago when I did the update manually) then it’s no big deal to go to 2.7 without hassles. I’ll have a bopeep and see if I can relocate where the cheat sheet was!
Note from some other source I found:
AND – WAU Says:
“= What files do you upgrade =
This plugin only upgrades the files that are essential which includes the files in wp-includes, wp-admin and the root directory
= I made some modification in the themes, will that be affected? =
No, we do not touch those files at all. We only upgrade files in the root directory and wp-includes and wp-admin directory.”
plus this instruction:
§ delete all the files in the main /blog directory except for:
§ config.php
§ robots.txt
§ favicon.ico
§ .htaccess
§ php.ini
§ phpinfo.php
Again, I do not delete any of the above files mentioned. I also do not delete my custom theme, only the ones that come with WordPress.
Note from wenu: “These instructions become obsolete with 2.7 because after that the WPAU plugin became redundant.”
AND
The list of changes from 2.7 to 2.7.1 are at :
http://core.trac.wordpress.org/changeset?old_path/ etc. check that out but it’s a long process to find the exact page I located.
The page description of the page I located is: Diff from tags/2.7@10539 to tags/2.7.1@10539 – WordPress Trac
OR
Changes from tags/2.7 at r10539 to tags/2.7.1 at r10539
That one actually comprises 64 files to swap from 2.7 to 2.7.1 but works anyway so long as you are ABSOLUTELY careful in replacing the indicated files, in their proper directories.
Hope you are not more confused than before. Note that the above is instructions for changes from 2.6 to 2.7 and THEN from 2.7 to 2.7.1 – all done manually.
Wouldn’t replacing all the files except the wp-config.php file work? (if you basically are taking an unused 2.3x install and immediately manually upgrading it to 2.7.1? The hosting company is really lame and only offers a 2.3x WordPress installer…
I’m getting a lot of errors about missing files, yet I’ve completely deleted everything except the wp-config.php file (at the root level) that contains all the relevant database references,etc.
To me, some of those six (6) files listed above seem to be just ‘look and feel’ but I’m prepared to go with whatever others suggest.
The point about going from 2.3 up is that I think you need first to get from 2.3 to 2.5 – but don’t take my word for that. I just updated whenever suggested during the last 14 months or so. Updating with cPanel was a lot easier than with my present DirectAdmin – but in the old Blog I had Joomla instead of WordPress – is it “different horses for different courses”? heh
As I read it, the Downloaded WordPress zip is a standalone and complete unit. The only reason for keeping some files is to save having to do a new Config etc., so I agree with you in theory. (plus the Database)
But I think there was a step at about 2.5 that was critical??
