Aaron Daniel wrote: > We had the bug on 1.2.2, but when I rolled back to 1.2.1 to fix the > problem, everything started working. Doesn't seem like it's a bug in > 1.2.1 :) It is not. The bug was introduced during the 1.2.1->1.2.2 transition.