Originally posted by sunder B
Best thing for support to do since it seems to be a sitewide problem and not just an isolated bug, is to urgently get in touch with Bort and to post an update or announcement with an ETA of it being fixed.
To ignore the userbase and tell us to "contact support" is not very supportive.To be clear, I was saying that the best way to get any issue resolved is to contact Support. I was mostly trying to respond to the suggestion from earlier that we'd committed a grievous customer service error by not replying to a forum thread. The point was that threads are great for discussing things, but if it's something an admin has to fix it's better to talk to an admin to get it fixed, not put it out there and hope we stumble onto the thread.
In this case, support has been contacted and Bort has been contacted. I'm afraid I'm not the one who talked to Bort, so I can't give you an estimate on when it will be fixed (other than that, as with anything, he'll fix it when he fixes it, and not before

).