@nevir: It's now fixed!
stevebelec
I think I am having the same issue...
(See 2 other replies to this status update)