As several people have been locked out of their accounts due to receiving a PM, I have disabled PMs for all non-admin users, to prevent it from happening unwittingly (I myself just had my previous backup get locked because of a PM). Just in case I somehow missed a user group when disabling PMs, DO NOT SEND ANY PMS TO ANYONE AT ALL, PERIOD. I repeat: THE PM SYSTEM IS BROKEN. RECEIVING A PM CAUSES THE BOARD TO GIVE AN SQL ERROR WHEN TRYING TO DO ANYTHING. DO NOT PM ANYONE UNTIL THIS PROBLEM IS RESOLVED.
Random member #1: "lol u suk" Random member #2: "o u bitch. PM'd" Random member #1: "arg my s2b accounts!" Taking the PM system out of the equation was a wise idea. Hopefully this setback will be remedied in due time.
That's alright. I was still able to login to the Admin CP and make another account. I can't really do much for the others until Simon comes back and investigates the problem further.
Would it be possible to get Super a back-up account as well? He asked me, but somthing went wrong when I tried logging in as the account.
OK, try your original account again, it should let you in now. I *think* it might have to do with some "innocent" persistent database connection setting I modified earlier. Still, to be safe, PM will remain disabled until I find out exactly what happened.
From what I could tell, either your PM logs mod screwed something up, or you made another PM mod that calls to ibf_members in the s2b database. Either you got the database wrong, or your table prefix wrong. Check your PHP files.
