Sent you a PM but then saw this thread.
This issue has been there since the forum upgrade to version 3.8.5.
We recently upgraded our forums to the latest version of vbulletin. There's a bug in the new release and it is said to be fixed with the next one i.e 3.8.6. There's no patch at the moment as it's not a security related issue.
Have tried manually scripting out this error but it wont work. It will have to wait until vbulletin fixes this in the next build.
Edited by TheTechGuy, 30 March 2010 - 05:47 AM.