Amalthia's recs and fan works

I accidently deleted the database for the Angst Archive so for now the site is down.

I have the sql file but am getting an error message #1044 - Access denied for user 'amothea'@'localhost' to database 'amothea_archive'

I have no clue how to fix this.

None of the files are gone or damaged the stories are all there but I think I lost the tables or I backed up the wrong file.

going off to my room to cry. Like seriously I'm trying very hard not to panic. Next time I swear I'll experiment with upgrades on my personal fiction site first.



EDIT: database is restored, but the site is still screwed up because I was in the middle of upgrading to 331 efiction in order to combat the spam attacks the archive was getting. Though at this point I've come to the conclusion that I was not prepared to upgrade the site after all. This is just one big mess and I don't have time to fix it because I have work in the morning. I should be able to get the archive restored by this weekend or during the weekend. (I hope)

Well I got the database restored, the one I backed up last week. Which means some stuff was lost, like 2 chapters I uploaded for one author which I'll re-add as soon as everything starts working properly again.

At the moment people can access stories but not categories. I can't update the welcome message and well there may be a few more bugs that I don't know about.

I've already wrote in a request for help at the efiction forums and I'm really hoping someone there understands what the error messages mean so I they can tell me what I need to do to repair the problem.

At this point I'm just happy the database backup worked. I can still access the story. Worst case senario I do a fresh install of the newest efiction archive software and manually transfer everything over to the newer version of the archive. (best case the problems i'm seeing are easy to fix for those that know how)

Also on another note, I got a stomach bug. So not a good day.

edit: it looks like I solved most of the error messages I was getting. so the archive is up and running again.