Define “patched” (for the DB).
By “patched,” I mean I got the upgrade for 2.0.2 -> 2.0.3, which I installed, instead of redownloading and reinstalling WP.
Obviously something is not OK in your “patched” database. I don’t know about the patch, sorry, so I give up.
What do you mean, you don’t know about the patch? WP, when 2.0.3 first came out, offered an upgrade patch to patch/upgrade 2.0.2 to 2.0.3. I followed the directions. Now, no one has posted on my blog before, so I dunno if 2.0.2 had this issue too, but I guess not since I would’ve found other posts on it. All I can do is speculate that the 2.0.3 upgrade is to blame, and if possible, find a solution to fix it via PHPMyAdmin, or doing other stuff with files/the database.
Thanks for responding though!
No one has a solution to this other than reinstalling WordPress? I really don’t want to lose any posts, etc.
Can you post the url of you blog?
“I’m assuming this is a problem with my database? I’m using 2.0.2 patched to 2.0.3”
It’s just your wording – there are no wordpress “patches” – it’s just an upgrade. The way you said it, it seemed like you got some sort of database patch, which no one here knows about since a wordpress upgrade and a database patch are two completely different things. 🙂
First thing I’d suggest is to backup your database (this is included in your wordpress under “manage”) and then hopefully someone will come along to help you sort this out… it’s probably something with your theme – have you tried switching themes?
Hey guys, sorry, I was away for a day or two.
1.) Blog URL: http://www.thinkinginpixels.com/
2.) Heh, sorry for my wording. Oh well, at least we got that resolved! 🙂
3.) OK…the database seems to be OK! It’s Tarski 1.1.3’s fault. Anyone need to a see a copy of the code for my php files? I’ll copy them into a public directory on my webserver if you need to look at them to suggest corrections.
You guys want to look at Tarski? Let me know.
