Yes, there was originally a slightly different issue with the blog back in September. Someone reported this to the vB at that time, meanwhile we implemented a workaround for our 2.2.0 build. Around the same time, vB released a new build of their own, which fixed the issue on their end, but caused our workaround to throw fatal errors.
On February 14, we updated the ZIP to account for both versions of the blog. If you have not upgraded to 2.2.0 (but it sounds like you have), you will need to do so. If you installed it prior to February 14, you need to re-download the ZIP and update your vault/special_plugins_online.php file.