$ 0 0 Are you ABSOLUTELY sure you're running 4.0.3? Because this was a 4.0.2 bug which we fixed in 4.0.3. Thanks.