From what you said it sounds like you only updated the files in the wp-admin folder. You should update all the files and folders.
Whenever I upgrade I follow this basic guide
http://codex.wordpress.org/Upgrading_WordPress
I do as suggested and manually do the wp-content folder, so I don’t accidently mess up my themes or plugins
other than that you overwrite everything else.
Same exact error here. I updated everything (not just wp-admin folder), preserving my theme and plugins, and filling out new wp-config.php file.
Any solution yet, Ben?
Exact same error here when updating to 2.7
Update: make sure your FTP-program uploads all files. I changed to Bullet-FTP, re-uploaded and wp 2.7 is working like a charm now.
My error. I hadn’t uploaded files to the right place after all. Never mind.
Left at default settings some FTP programs would not overwrite existing files. Others would only replace files if they exist, but not add new files…
Usually wp-admin and wp-includes can safely be deleted before starting an upgrade through FTP. That can fix some unusual problems too and reveal files that have permissions problems/cannot be deleted, etc.
I use SmartFTP. It prompts if a file or directory is to be overwritten, so I simply select the option that makes sure all files are updated. I’ve upload the entire contents of wp-admin including subdirectories but I also preserved my theme and plugins, and filled out new wp-config.php file.
When I downloaded the upgrade and unzipped it there was only the wp-admin folder with files and subdirectories. Should there be more?
Uh-oh, there is more isn’t there….
I have a particular site that I upgraded to 2.7 and whilst the site works as before, when I try and login I get this:
Redirection limit for this URL exceeded. Unable to load the requested page. This may be caused by cookies that are blocked.
All the files are there in the wp-admin folder, I updated the site using the WordPress Automatic Upgrade plugin and was able to login ok yesterday. I have not changed anything on the site or the server. I can request a new password ok, but it just gives this Redirect Loop Error.
Anyone got an idea of what I can do to log in?
Thanks
Kev
kejabe – your question deserves its own thread, so please start a new topic.
loveservice – it is possible, if using the built in Windows unzip facility that you didn’t get everything unzipped. Try using 7-zip to unzip the files then revisit Steps 7 and 8 of Upgrading WordPress Extended.
#@#@#@@@#… the same error here…
after wanting to enter the dashboard (yx.com/wp-admin):
Fatal error: Call to undefined function wp_user_settings() in /home/xxxxxxx/public_html/xxxxxx.com/wp-admin/admin-header.php on line 14
Upgraded to WP 2.7 almost 40 blogs yesterday via cpanel, and the question: how can I fix this manually? (I always used cpanel for installing and upgrading)
Help appreciated 🙂
Well, I solved the original problem by unzipping and uploading all the correct files (I had missed some when I first tried).
Now, the errors are as follows. A visitor sees:
Fatal error: Call to undefined function: wp_remote_post() in /var/www/vhosts/xxxxxxx.com/httpdocs/wp-includes/cron.php on line 201
and the admin page shows:
Fatal error: Call to undefined function: wp_remote_post() in /var/www/vhosts/xxxxx.com/httpdocs/wp-includes/cron.php on line 201
So, how is it that wp_remote_post is an undefined function?
How can I fix this?
I use filzilla to upload my files. I deleted the old files, per the detailed instructions here on wp.org and am getting this error:
Fatal error: Call to undefined function wp_remote_request() in /home/provbsco/public_html/wp-includes/update.php on line
I’ve been searching all of these forums trying to find an answer. I’ve deleted the new wp files from my server, reinstalled my old files, deleted them again, down loaded and unzipped an entirely new 2.7 and uploaded per the instructions again.
Same error. Has anyone figured this out yet? If so, please post some step by step instructions. I’m sorta new at this.
Thanks!
PS. I’ve successfully upgraded 2 blogs already today. The only diff. bet. this one and the other two is this is in directly in public_html.
The other two are in public_html/blog1 public_html/blog2.
I couldn’t fix this, so I deleted all the 2.6 files, took a backup of my database, installed 2.7, and inserted my posts into a new database.
I will think very carefully before upgrading again.
