When he says there is no knowledge about the code "laying around" and also when he says it has not been addressed in about a decade. If they haven't corrected it in a decade then I would say that means that portion of the code is not being supported

So you are assuming then, he never came out and said it was not supported. :)

He also stated in that post that all the warnings should be taken care of now, " In 4.2.3 I believe they've all been addressed, and we're working on 5.5 issues now. "

Does that mean that there will not be more in the future, no. It also does not mean that everyone is corrected. :p

You actually do not know what you are talking about, and you've also ignored every single attempt anyone's made to explain it to you.

Please refer back to Joe's earlier post which explains it precisely and answers every point you're trying to make.

Of course, what you're ACTUALLY trying to is bash the company, which is why you aren't taking the slightest bit of notice of the facts being presented to you and instead keep posting the same thing over and over again.

--------------- Added [DATE]1410124101[/DATE] at [TIME]1410124101[/TIME] ---------------

Utter rubbish.

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.

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?

PHP "warnings" are really nothing more than information messages, and are intended to be suppressed in production environments. Go read the set-up instructions for php production values.

Actual php errors cannot be supressed, they will generate a fatal error, and the execution will fail at that point.

Ill informed ranting will not change this, nor will it change how php applications are written.

If certain people cannot comprehend what they have been told several times now, then there is little point in this discussion continuing.

If you have issues with the software and how it is coded, and what may have been or not been told to you prior to purchasing, then you need to address this on vB.com.

This site is not for this type of discussions, it is about modifications and making changes to templates and such.

Yes vBulletin do have the technical skillset to develop and support their products. Hence 4.2.2 and 4.2.3 dealing with the warnings and also adding php compatibility to latest versions. However, feel free to ignore these facts and continue with inaccurate rants, as everyone else can now see the facts.

And yes, I do understand what you're talking about, it's just that you're completely wrong.

Understood