Glad it's a bug (ie: fixable) and not something in my configuration.
Quick question: does this follow the conventions of vb's secondary usergroup handling? That is, if I have it enabled for one primary group, but a member also belongs to a secondary group with this disabled, will it then be disabled for that user? I hope so, as I currently block ads for paying users via a secondary usergroup, so I'd like those same paying members to have this plugin disabled for them.
|