View Single Post
We fixed a bug like this in 1.0.2.
Please double-check that you've got that update.