Sorry guys, charset screwup.
I fixed everything I could find, but I didn't do all the profile fields so it's possible something still slipped through. Let me know if you find any more.
jp wrote:This happened the last time there was a server hiccup, too. Even webteases were hit by the "bug". Don't remember if there was a resolution or if things had to be manually fixed.
I think there were a couple of these. MySQL defaults to Latin1 for god knows what reason, but our database is in UTF8. So it's pretty easy to forget to set the correct charset when importing stuff. I think I always fix it once it gets reported.
Especially if it affects webteases and/or forum posts, manually fixing is pretty much out of the question, at that point we're talking about many tens of thousands of pages/posts.
janmb wrote:I've been working with this board system and had a database act up on me a few times myself and getting that back together is certainly not easy short of a flat out restore like I suspect seraph did...
A full restore would have undone all changes that happened between the 21st when the error occurred and the 26th when I had a chance to fix it, so that wasn't an option. (If I rolled back the database one day I'd get complaints. Three days - I'd get serious unrest. Five days - I'd be straight up lynched.
)
Fortunately the corruption was limited to a single table - the users table - and there was no incorrect data, only missing rows. So what I did was edit the backup for that table replacing the INSERT statements with INSERT IGNORE. That way, no changes were overwritten - only the missing rows were restored. Voila good as new. Except I picked the wrong charset - oh well.
janmb wrote:Anyone else but me get redirected to some "default website from the hosting company" a few minutes ago?
That would be pretty odd - we use co-located servers only, no webspace. The only page that I can think of that you might get if something goes wrong is our "bad virtualhost" page (
example). Maybe a URL typo?