Alright, apparently I diagnosed my problem incorrect, it seems to be a conflict with vBadvacned. The issue I posted about the unknonw location showing in whosonline has nothing to do with someone viewing a thread with images in it, rather... whenever anyone is looking at my vBa index or a vBa page, I see the;

Unknown Location
/clientscript/ncode_imageresizer.js?v=3

In whosonline. Any idea why this might be the case, I would assume it shouldnt interact with or intefere with vBa in anyway?

In past versions I relied on the per version installation code functionality of vBulletin. Either I misunderstood this functionality or something else went wrong, but I now just use one installation code. The SQL error you give is related to an old version. Please uninstall everything and reinstall the latest version to get rid of everything. Perhaps you can give me the version number of the version you had before so I can test how upgrading between these two versions goes and I can try to improve this.

vBAdvanced compatibility is something I will look into in the near future. I will take this report into account then.

If you use the RC1 database schema you will get problems, because is has changed in the meantime. As I said, I will look into the upgrade problems. I will not go back to the old method, that's for sure.

The first post (and readme) also mention another way to thank Spleasure. :) A few bucks via PayPal is how I showed my thanks, for the best hack to come along in a while... along with great support and responsiveness! Thanks again, Spleasure!

I have tried all kinds of upgrade scenario's and I can't reproduce the errors. Mike-D: can you tell me which versions you had installed? In which order did you upgrade?

Why is it working for my members with FireFox but not with IE? *sighs* Why can't anything ever be foolproof?

Great Mod,

Improve the board look alot ;)

I visited that URL in Internet Explorer 6 and it works for me. Please contact me by IM so we can fix this bug.

does this work with 3.6.4? if so, why not mention it in the original post?

Yes, it works with 3.6.4. It actually works with 3.6.0 and up, it's a little unclear. But if you keep in mind that there isn't much difference between 3.6.x and 3.6.y (x != y), just bugfixes, then this is clear automatically.