Kevin has looked into this and it appears to be a bug in vBulletin, he has reported it to them so hopefully a fix will be included in a update not too long from now. Thanks,