This was supposedly fixed according to Tuesday's maintenance notes. Try clearing the cache.