Rick, how do you do this: “Unzip and upload by FTP, replacing all WordPress 3.2 files”
THANK YOU SO MUCH!!!!
it’s back. Does it work for you?
http://hardwareinsights.com/wp/
One problem, my admin dashboard looks messed up and it says “Database Update Required
WordPress has been updated! Before we send you on your way, we have to update your database to the newest version.
The update process may take a little while, so please be patient.” in all the panes. should i click “Update?”
thanks.
you rename the wp-content folder to wp-content2, then you upload the files from 3.1.2 to your wp directory on the web server.
overwrite the files. then you delete the new wp-content folder and rename the old one back to wp-content
only problem is wp-admin is messed up 🙁
I’m in trouble. None of this makes sense to me. I’m not a computer person.
U want help? Just email me shovenose@hardwareinsights.com I’ll do it for you. I’m happy to help out another WP user 😀
I’m just so relieved my site is back up!
Thank you SN! I am checking with someone I know, but I may take you up on that!
nevermind me previous question. Everything has been restored to proper functionality. Thank you so much everybody, especially Rick 🙂
You’re welcome, happy to know you got it fixed.
Summarizing,
1- Replace all files except for your Theme if it’s custom-made.
2- Same for any plugins you might have created or customized.
3- And do not delete wp-config.php either, because it holds your MySQL password and other details specific to your particular installation. (it does not exist in the package you are uploading, so you won’t be overwriting it. It is created during installation using wp-config-sample.php as a template)
P.S. Also keep the wp-uploads folder, where all your pictures inserted in your posts and pages are.
I updated to 3.2 on http://www.thomdickey.com but I did remember to make a backup of the db before however when the screen refreshed the sidebar where all the controls are located is now missing. I am going to restore the old db and see if that fixes the problem but I am now concerned about doing a update on any of my other domains that really do require that they stay healthy. Any thoughts about this will be greatly appreciated.
Well, 3.2 works fine on two other of my sites. They’re on a different host from the one that had problems. The one that had problems, was using Arras theme, which was known to have 3.2 issues, and also my PHP version was not new enough.
@rick: it’s easier just to keep the entire wp-content folder!
@amplegreen420
Just make sure your host meets the minimum requirements BEFORE you update.
@shovenose
If you keep the entire wp-content folder you are not upgrading its contents, which may or may not have changed.
Also, if you have plugins that are not compatible with the new version you’ll be running into trouble again.
I prefer to reinstall the plugins again one by one after I’ve done the WordPres upgrade. That way I get to review their compatibility rankings, how old since their last update, etc.
I wouldn’t do it for minor upgrades, but for a major one like this one, I would definitely take all possible precautions.
It seems fine.
Thank you so much for the help 😀
I upgraded to WP 3.2 a few days ago and now have lots of problems. At first I thought it was only theme related (Arras Theme), but then switched to Twenty Eleven. Now the dashboard doesn’t work – toggling and rearranging widgets isn’t working. I’ve taken the time to delete all plugins but two, which are inactive at the moment (I can’t do anything with the installed widgets though). I’ve checked my hosting service (GoDaddy) to make sure everything is up to date with MySQL (5.0) and PHP (5.2).
I’m completely stuck now and hope I can get a solution to the problem soon without having to hassle. I’m not into coding much, so if anyone knows of a solution for me that’s simple (though I can follow good directions) I’d greatly appreciate it.
Much thanks. 😉
{UPDATE}: I think my whole problem has to do with Firefox. I’ve been able to work with my WP dashboard in IE, so hopefully this will be the fix I was looking for. Hope this helps others who have been experiencing the same kinds of problems (it sure beats having to mess with reinstalling programs).
Peace. 😉
PHP 5.2 isn’t enough. It’s apparently got to be 5.2.4. My 5.2.14 didn’t work.
