Your posts are in a database which is completely separate from the files, so replacing all the files makes no difference. The only thing is if you’re reinstalling with a newer version of WordPress, in which case treat it as an upgrade and run upgrade.php in your admin directory after uploading the new installation. (Newer versions may have to reconfigure the database.)
Basically, upgrading *is* reinstalling.
Oh, and back up the database before you do anything!
WordPress_Backups has some info on db backups.
I’m currently using the newest version of WordPress, 2.2.2.
But I’m having a couple problems with it. Is it possible to downgrade or possibly even re-upgrade?
Assuming you made a database backup BEFORE the upgrade, you could restore it along with the previous WP version.
Or, you could start some new topics about the problems you’re having and see if folks could help.
I actually have already posted a new topic about my problems, but nobody replied. I am having the same problem a lot of people are having, but it doesn’t seem to have been solved yet. It’s this same problem:
http://wordpress.org/support/topic/101693
Heres my post:
http://wordpress.org/support/topic/131630#post-607497
It seems to be a very serious problem. Is it being looked into? Is there a fix for it somewhere? Or did WordPress give up on working on a fix? Or was it completely looked over?
It’s making me so upset because I don’t wanna lose all of my hard work! 🙁
Sorry you didn’t get a reply. Sometimes these things are mysterious and no one knows what’s going on. I’m just a WordPress dabbler and I’ve really no idea. I’d imagine someone will be looking into it.
One of the other people in that thread said that upgrading WordPress Gallery solved the problem. Have you tried disabling plugins to see if that makes a difference?
I tried deactivating every plugin that I have installed:
- Akismet
- CoolPlayer
- Flickr Photo Gallery
- Now Reading
- Progress bar Widget
- Run For Cover
- Scrobbles Widget
- WordPress Video Plugin
- wunderground.com weather sticker
But it still didnt work.
I’m sorry. That’s a really crappy experience. If I were you (and you may have done these things already). I’d reinstall and run the upgrade script, but heaven knows if any of that will help…
Hmm, it worked when I tried it on my new MacBook. 🙂
So maybe it’s a browser incompatibility thing?
Anyway, that’s good news (both the new MacBook — wonderful, aren’t they? — and the site functioning properly).
It could be, but it still rather strange how it just randomly started having that problem. Hopefully I never have the same problem come back some how. The problem had occurred in Mozilla, Mozilla Firefox, and IE. (now I’m using Safari)
Yes, the MacBook is wonderful. I’ve only had it for two days now and I’m already in love with it. It makes me never want to use my crappy Gateway desktop ever again.
Gateways are good. Standard hardware is all linux friendly. 🙂
