To tbworld, thanks for assuming I don't know what I'm talking about, it really reflects on your character.
You said if more would have been involved in beta/alpha testing then this wouldn't have been an issue. As ozzy has said, this has been present for 10 years, I wasn't around to beta test 3.x but I was around for 4 and 5 and I know for a fact that the testers reported tons of errors and it went on deaf ears. If you're in the alpha team for 4 or 5 you would have seen that as well. I don't know if this "bug" was reported but I do know we gave great feedback and it was ignored for the most part.
The lesson is that vbulletin doesn't care about quality anymore, not just in this issue but in general. What the customers get is 50% rubbish and half of the rest works as it should.
My point was that my client pointed this thread out to me thinking it would fix the errors they're seeing on their forum which they paid for. This was a stock setup with only one new style added which the client was working on to make it match their brand. I had to tell them to just ignore the errors because that's what vbulletin told us to do.. Very professional indeed
Why is it up to the customers to suggest how to fix a broken product? Also this was the
latest stable release in the members area, so not sure what "latest release" you're talking about.