Which version are you using? If it's 2.0.1 or 2.0.2, then this bug was fixed in 2.0.3. If it's 2.0.3, then I must have missed something....