The problem is that overnight my 2007 folder which hosted all my posts this year somehow was deleted
1. WordPress NEVER stores anything in folders. All your content is in the database.
2. Your sidebar is full of errors caused by falbum? Disable it.
3. Fix the database: read the error (errno: 145) – contact your host and/or google for it.
Thanks Moshu.
1. Okay. That’s good to know.
2. That’s a recent thing but it seems to have stuffed up the database so that even when deactivated as a plugin I still get the error.
3. The database now no longer opens far enough to give me the repair option. If the database can’t be repaired I guess that means new posts are not going to post?
However, another thing I thought might affect it is that that I’ve changed my FTP password. I can’t find the option in WordPress to reflect that change.
??
CB
FTP has nothing to do with WP. That’s you and your host.
Ahhh got it… I think. The config file needs to be reset… right?
I’ll let you know how I go.
CB
No. Stop guessing!
Your config file is fine because the blog displays. Better don’t touch it.
If you cannot repair the database – contact your host and don’t mess with everything.
Too late.
You were right. I was wrong.
It has all gone.
Have replaced original file but to no avail.
having consumed an enormous humble pie…
I don’t suppose there is anything I can do at this point is there?
CB
If you reallly have the original wp-config file – it should work (with the above mentioned db errors.
seemingly, your info in the wp-config is NOT correct, regardless what you think…
(and it should be a good lesson no act act on impulsive guesses, LOL)
First, figure out the right info and restore your wp-config file.
Secondly, contact your host to repair the DB.
Okay so what I (stupidly) did…
I impulsively (!!!) changed the password on the config file (after saving the original in another place).
Then I tried to post something.
Then I got the error message.
Then I went (insert loud expletive here) and restored the original.
And then I read your warning. 🙁
But now my front page is just the WordPress Database Error page.
And yes I have contacted the host to repair the DB.
And I take your point about what I think. Plainly not thinking is the problem! LOL or should that be COL!
Again – you did NOT restore the original wp-config. You think you did, but it didn’t happen.
How come you’re so clever? You must be psychic!
You of course were right… again. I had brought it across as a txt file. Twice.
So now I will go to sleep and awake to hopefully an email from my host saying the database has been fixed as per my request. LOL
Thank you for your patience.
CB
You must be psychic!
Nope 🙂 – just been there…
(click on the “moderator” under my name and look at the date!)
On Mousekingdom.. at first when I went to post a comment it went right through. Then I had to enter a security code. Now I get this message
Sorry, but your comment has been flagged by the spam filter running on this blog: this might be an error, in which case all apologies. Your comment will be presented to the blog admin who will be able to restore it immediately.
You may want to contact the blog admin via e-mail to notify him.
I don’t know who to email. Can someone help me
Thanks
So here’s another dumb question.
If the database has corrupted and is, for all intensive purposes, stuffed, how come I can create posts and edit them?
CB
PS re date: impressive!
I don’t see the DB error anymore.
However, I see there is a problem with your permalinks.
Try re-setting them. (if it doesn’t work, set them to default)
