[Disco_Stu]

Originally Posted by Mark.B

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.

You need to get a clue. I am complaining about the following (so it is crystal clear to you):

1) I was not informed prior to purchasing this software that warning messages were being suppressed. The sellers should have informed potential customers of this

2) I was told by a support staff member that these warning messages have been around for a decade without being addressed. That is unacceptable coding practice in my book

3) I was told by the same support staff member that they did not have the knowledge "laying around" about the code that was generating the messages. This means that they are selling software that they have no knowledge about. If you know nothing about the code then how do you support it? How do you properly test each new release? How do you even know what it contains? And why can't you understand it? Do you not have the technical skill set to understand it?


Are you clear now? Do you now understand what I am talking about?