If this is the same issue we think it is, this is fixed in the 0.20.2b build going live in the next few minutes :)
