Try:
– switching to the Twenty Eleven theme by renaming your current theme’s folder in wp-content/themes and adding “-old” to the end of the folder name using FTP or whatever file management application your host provides.
– resetting the plugins folder by FTP or phpMyAdmin.
– re-uploading all files & folders – except the wp-content folder – from a fresh download of WordPress.
– re-running the upgrade via wp-admin/upgrade.php
Do I upload all of the new files (with the exception of the wp-content folder)to my existing directories, or do as the install says and upload them to a new directory and run it from there? I have made the changes to the plug-ins folder, and have re-named the twentyten folder to twentyten-old.
Upload all the new files over your existing directories 🙂
Or delete wp-includes and wp-admin ONLY (JUST those two folders) and re-upload from a fresh install (you can get that from http://wordpress.org/download/ ) if you want force things.
You won’t hurt your themes or plugins as long as you leave wp-content alone 🙂
Well, the blog is back, although I got an internal server error after the update ran. And now I”m getting the message that:
An automated WordPress update has failed to complete – please attempt the update again now.
And now I can’t get the plug-ins to re-activate. What happens if I do a new install and save my content folder, then move it to the new install?
Did you try the suggestions I posted above?
Yep! Renamed the twentyten folder, reset the plug-ins in PHPMyAdmin, uploaded the new files, with the exception of the wp-content folder and its files, and then ran upgrade.php.
The blog itself seems to be up, but everything is dog-slow, and when I try to re-activate any plug-in, I get an internal server error. And the only thing I can equate this with is my editing of the plug-ins table entry.
I’m ready to do a clean install, but I hate to lose everything. But if the database is corrupted… What happens if I do a fresh install, connect it to a new d/b, and keep the contents folder?
Try checking your server’s error logs.
Well, I’ve been round & round with GoDaddy about this. Everything seems to be okay yesterday, and then this morning 500 Internal Server Error pops up again. This time I went to a different tech support guy who was a bit more helpful – the last kept telling me it was WordPress that was hosed and all of their stuff was fine.
Anyhow, this guy looked at everything and had me rename the .htaccess file and try again. Everything is working, so he thinks it’s this file doing the damage. This is the file:
addhandler x-httpd-php-cgi .php4
addhandler x-httpd-php5-cgi .php
addhandler x-httpd-php5-cgi .php5
The site is http://www.theampat.com. The .htaccess file is still .htaccess.bak2, and all seems to be working fine. Any input?
