Database Glitches

You all must know by now that we've been having some serious problems with the archive due to both the hacker situation and the sheer size of the archive. Our priority these past few days have been limiting the glitches, but they are beginning to mount to the point where we may need to initiate a temporary queue shutdown. Over the course of the next few days, we will be trying to do a site upgrade, which will hopefully fix the problems we're having. The number and frequency of glitches may escalate over this period, but we ask you to bear with us.

There are several ways you members can help us:

+ Do not submit any new chapters or stories to the queue starting from now. Doing so will add unnecessary strain to our already wobbly system and may threaten the existence of every single story and author stored on the database.
+ Back up your stories and/or reviews just in case the worst happens. We will try not to cause an MNFF apocalypse, but no promises can be made.
+ If you have a fic you've wanted to get rid of or an abandoned fic you aren't going to continue, now is the time: just go in and delete it from the archive yourself.
+ Queue wait time is much, much longer at the moment due to, again, our focus on stabilizing the database. We will try to mod stories as often as we can, but complaining about your wait time will only serve to deter us from our main goal which is to make sure this site continues to exist.

Here are a few glitches that have already been noted and that we will try to correct over the next few weeks.

+ Edit bio information - Reported error is "Method Not Implemented: POST to /user.php not supported."
+ Switch categories and Add stories/chapters - Reported error is "That category is locked. Please select a sub-category."

Several people had reported errors when contacting users via the "Contact" button on user profiles; that error has now been fixed.

Finally, as we are updating behind-the-scenes codes, we will, as humans, make mistakes. Therefore you will see some pages/functions glitching. Please do not report it until 24 hours after first experiencing the particular glitch. That way, you do not waste your time reporting a glitch we know about and will have already fixed; if it is not fixed within 24 hours, most likely we don't know about it and would like you to contact us.

We will keep you updated on glitches and fixes. We will also notify you when you can begin submitting stories in a (nearly) error-free environment.

If you have any questions about this don't hesitate to post them here, but please don't waste our time with off-topic ones that should go elsewhere. As you can see, we have more than enough to do at the moment.

Thank you ever so much for your patience and cooperation.

EDIT: If your story suddenly disappeared from the queue, please don't be afraid. It is not a glitch. Your email provider merely weeds MuggleNet Fan Fiction emails out and refuses to send your rejection letter. Instead of posting in the comments, please post here at the Beta Forums.

UPDATE: We do NOT have an estimated time for when the queue will be "reopened" or when the update will be done because we're running into some difficulties with a third party. Now that that has been answered, please stop asking the same questions in the comments section. Please take the time to at least skim the already existing comments.