Forum Bugs

[sswilson]

Originally Posted by S_G

Firefox 3 right now. You got my PM? Odd, I guess the PM stuff is still partially working. You can get into the message sending page if you go to it directly (ie. by clicking "Send a private message" under your name), but actually trying to get to my inbox or sending the PM resulted in a database error message, so I didn't think it got through. I don't think you'll be able to read the message, though.

Yep, front is down now too.

When you have PMs set to notify you via e-mail you get the text of the PM in it. :)

[lemonlime]

I'm consistently not able to get to my PM inbox or the User CP with a VB database error message. Just an FYI.. I'm sure its being worked on

[S_G]

Originally Posted by sswilson

When you have PMs set to notify you via e-mail you get the text of the PM in it. :)

Sweet, thanks for moving my thread!


As far as the server error is concerned, try clearing out the temp directory manually, but I have a feeling that's just a temporary fix. If you have an antivirus on the system, disable it, or have it exclude the MySQL temporary files path.

[element291]

Zhen was able to send me a PM but i can't access PM at all like most of ya.

[Eagle Eye]

PM issues as with all the rest...

Sheesh this thread just got a lot bigger within the last hour, poor Gav

[Chilly]

Everything around us seems to be failing, every hour it seems I lose access to another part of the site due to database errors. I hope you guys get it sorted out soon!

[Jake_HT]

Yeah I can't check my PM's!

[Chilly]

Another issue just popped up, I can't access alot of user profiles, but some still load fine. For example;

jdrom17's profile loads fine, but
miggs78's profile doesn't, just gives me a database error

[mklym]

Still getting this message when trying to leave iTrader feedback.

"Sorry, but you must wait until January 13, 2009 at 01:09 PM before you can rate this person again."

Has been ongoing since Friday.

[sswilson]

Just got an e-mail from Gav ref. the DB issues. They're aware of the issue and currently working on it (DB got corrupted or something silly like that.... :) ).