Upgraded to 4.2.2 problem with stylevar

[Disco_Stu]

Originally Posted by ForceHSS

I totally agree with what you have said this is why I put a link in my sig so any can find the fixes for the problems in 4.2.2

Thanks. Between the constant security issues for each release and things like the suppression of warning/error messages I have to say I'm very disappointing in the quality of this software.

Why is it that no sooner is a new version released then hackers find security holes? Don't the developers test their work? Why don't they see these holes before the release? You would think that after the first few times it happened the folks writing this stuff would get a clue and start doing more rigorous testing.

My clients would NEVER put up with this lack of quality control. My software is used in very large scale environments and the slightest errors can balloon into major problems in no time at all.

It's my understanding that vBulletin is used on over 100K sites which makes me wonder why more effort is not put into QA. Perhaps a rush to release a new (and expense) release to drive sales is the reason.

I've beaten this dead horse enough

[Zachery]

Again, you do understand that these error messages have been suppressed since 2004?

[ForceHSS]

I have never been hacked because I make my forum secure its not hard to do

[Disco_Stu]

Originally Posted by Zachery

Again, you do understand that these error messages have been suppressed since 2004?

So you're saying that with all the releases in the last 10 years no one bothered to find and address the source of the problem???

[ozzy47]

Why would you want to address the warnings if they are just depreciated PHP warnings. They are addressed if they become errors AFAIK.

[Zachery]

Originally Posted by Disco_Stu

So you're saying that with all the releases in the last 10 years no one bothered to find and address the source of the problem???

For a long time, no one actually had touched the code that did all of this, and the code base goes back to 2002~ or so when vBulletin 3 development started. Every developer from that time period is gone. We don't have that knowledge laying around anymore.

So, to fix them, in 4.2.2 we DISABLED it, and then found a large chunk of them and actually fixed the code.

A few of them escaped, and went unfixed in the final 4.2.2 release. But we patched it with the skip errors lines if customers were running into it.

We urged them to log bugs where they were occurring.

In 4.2.3 I believe they've all been addressed, and we're working on 5.5 issues now.

[Disco_Stu]

Originally Posted by Zachery

For a long time, no one actually had touched the code that did all of this, and the code base goes back to 2002~ or so when vBulletin 3 development started. Every developer from that time period is gone. We don't have that knowledge laying around anymore. .

Let me get this straight. You're saying that you're selling a large software package containing code that no one on the current staff has any knowledge about?? What????? Are you kidding me??? You're joking right??? You must be!!

[ForceHSS]

Originally Posted by Disco_Stu

Let me get this straight. You're saying that you're selling a large software package containing code that no one on the current staff has any knowledge about?? What????? Are you kidding me??? You're joking, right??? You must be!!

I don't think he is, it is a surprise to me that no coder can fix the coding after all any coder should know how to code even if another coder first done the coding

[Disco_Stu]

Originally Posted by ForceHSS

I don't think he is, it is a surprise to me that no coder can fix the coding after all any coder should know how to code even if another coder first done the coding

If what he''s saying is true then I am shocked ! How in the world could a company actually sell software containing code that they have no knowledge about? How can you possibly test a new release when it contains code that you have no knowledge about? How do you support it? How do you know how it will interact with the new code for the new release? How do you know that some angry developer didn't plant something nasty in it?

But you are correct in that any good coder can figure out another programmers code. That brings into question the capabilities of the current staff. Why can't they understand the code?

As I said - I am shocked!

[ForceHSS]

I have lost some trust with the devs after finding this out if they went in and fixed all that needs doing I am sure things would run a lot better. But going by what has been said they don't seem to have a clue