Ah this makes sense, the plugin is using the same hook locations as the normal vBulletin WOL, however the database object isn't the same variable/globalised within the CMS. I can resolve this tonight for you, I'll update this thread once the fix is live :)