after a quick bit of research, it appears this is a very widespread issue that's been popping up all over the place since the 3.0.7 version of vb was released. the vb admin dudes suggest re-uploading all original non-image vb files (minus install.php of course) as a quick/temporary fix. other than that, it's something they're working on.
i imagine it's one of those super elusive bugs floating around in some obscure chunk of code.
i imagine it's one of those super elusive bugs floating around in some obscure chunk of code.
Comment