This problem existed only briefly in v1.0 and was fixed last year. 

Reply via email to