[Mark.B]

Originally Posted by Disco_Stu

I don't appreciate you accusing me of trying to bash the company. I therefore accuse YOU of trying to justify bad coding and support.

Please tell me when it is considered good coding practice to ignore warning messages instead of identifying and correcting the root cause? If that's the way you design systems then I suggest you take a few business and systems design courses at your local college. It sounds like you could benefit from them.

Again, please read Joe's post where he explains in detail that these matters have been fixed....

4.2.2 behaves the way it does by default because vBulletin were FIXING the warnings.
Yet here you are, complaining about warnings not being fixed, despite you being told several times now that they are being fixed.

Really don't know how to spell it out any better than Joe did in his earlier post.