Known issues from the latest deploy
Published: 2011-11-14 07:42:49 -0500
As most people have noticed, we have had some problems with our latest deploy. We'll address some of the larger concerns in a later post (right now, most of our staff are busy dealing with the immediate issues), but we just wanted to do a quick update to let people know that we're aware of some specific issues and we're working on them:
- Mobile display: We had a big problem when we deployed with mobile displays, because the new mobile skins were not kicking in at all. We've fixed the main part of this issue, so the site is now much more usable on a lot of mobile devices; however, we're still experiencing some bugs with mobile displays, causing button overlays, too much white space, and other oddities. We think that the problem is still related to some parts of the mobile stylesheets not being activated properly: we're looking into it.
- Some problems in Internet Explorer:
- the commas separating tags are not showing up (some versions of IE) or they are showing up too aggressively, giving a comma at the end of every tag even if it's the last tag in the list.
- Some people are reporting problems replying to comments in IE.
- The skins wizard is behaving erratically and inserting code which messes up other things.
If you're experiencing one of the above issues, rest assured we're looking into it. We've already fixed some issues with mobile display, a problem stopping people from bookmarking, the missing OpenID login, and a few other bugs, so if you were seeing something not mentioned on this list, it's worth checking that the problem is still occurring before you get in touch with us.
If you see a problem that's not on this list, do get in touch with Support via our Support and feedback form.
We'd like to say a huge thank you to Support, who have received more tickets in the last 48 hours than they did in the previous 48 days! Despite this massive amount of work they have kept up with replies and right now there are only ten tickets not assigned to someone to be dealt with - GO TEAM! Thanks also to the coders and testers who have worked like crazy to do urgent bugfixes.
Once again, sorry for the problems this deploy threw up: we're working on the immediate issues right now and thinking about future solutions.
ETA: We've received several reports from people who are unable to use the rich text editor. We're having difficulty pinning down this bug since it seems to manifest inconsistently, but we are looking into it. Apologies for the inconvenience.