Upgraded to 4.2.2 problem with stylevar

[Brandon Sheley]

Originally Posted by Disco_Stu

Suppressing errors (hiding, covering up problems) is about the worst thing you can do as a developer. If customers find out you're doing that then they will never trust you again. This type of approach shows a complete lack of desire or ability to fix the underlying problems.

This is the way vbulletin works these days... Just hiding the errors is not the answer. :up:

[ozzy47]

Originally Posted by Brandon Sheley

This is the way vbulletin works these days... Just hiding the errors is not the answer. :up:

So you are saying, there is no other software out in the world that does not suppress warning messages?

[Brandon Sheley]

Originally Posted by ozzy47

So you are saying, there is no other software out in the world that does not suppress warning messages?

I'm saying vbulletin is doing a sh*ty job here and now I have clients asking me why all these errors are on their pages while they configure the style as they want.

It's making vbulletin look bad for me to say.. Oh, vbulletin knows about these warning and their fix is to just HIDE them.

The professional vBulletin we all knew 5+ years ago is long gone, it's ran by lazy management now that only cares about selling more products and sock puppets that seems to believe their still supporting a superior product.

I wish them the best but I'm moving clients away from vbulletin as fast as I can, it's nowhere worth the headaches it's causing.

For example... I have a client moving from ipb 3.4.6 to vb 4.2 and impex itself has 3 errors in the code which where all reported over 4 years ago and would take a few mins to fix the release package.. Do you think it'll be fixed anytime soon, I'd be impressed if these simple fixes where in place in the next 4 years.

Example #2.. I reported a bug in that godforsaken bug tracker called jiri several years ago.. I'm JUST NOW getting email updates that someone is looking at it. It's always up to the consumer to "post in jiri" yet nothing ever happens, even if the customer goes out of their way to figure out exactly what the problem is and how to fix it... which is wrong on so many levels..

It's time vBulletin acted like the million dollar company it is, not like a few high school kids working on a script on the weekends..

</rant>

[ozzy47]

You do realize that these error messages have been suppressed since 2004?

So it has nothing to do with the past 5 years, it has been 10 years like this.

[Brandon Sheley]

Originally Posted by ozzy47

You do realize that these error messages have been suppressed since 2004?

So it has nothing to do with the past 5 years, it has been 10 years like this.

Yes I read that several times but does that make it right?
Also if they've been hidden for 10 years, why are they popping up now?

[ozzy47]

Originally Posted by Brandon Sheley

Yes I read that several times but does that make it right?

Well it may not be right or wrong, but it makes the below a mute point.

Originally Posted by Brandon Sheley

I'm saying vbulletin is doing a sh*ty job here and now I have clients asking me why all these errors are on their pages while they configure the style as they want.

It's making vbulletin look bad for me to say.. Oh, vbulletin knows about these warning and their fix is to just HIDE them.

The professional vBulletin we all knew 5+ years ago is long gone, it's ran by lazy management now that only cares about selling more products and sock puppets that seems to believe their still supporting a superior product.

Originally Posted by Brandon Sheley

Also if they've been hidden for 10 years, why are they popping up now?

They are showing up now because the suppressing of the errors was removed, in order to fix them, AFAIK they are all fixed in the latest beta of vB4/vB3

[Brandon Sheley]

It doesn't really make it a mute point to me or my client but there is nothing anyone is going to do about it.

[tbworld]

There is a reason why error suppression is a built-in language construct. @Brandon Sheley you are arguing something you really do not understand. I doubt that you will find any advance programmer or program written for multiple platforms that does not contain error suppression or error response altering. In fact I do not want to work with a language that lacks this type of mechanism.

If more users would have been involved with alpha testing the releases (I am at fault here), then the error suppression would have not been an issue by the time it went to beta. The lesson here is that vBulletin needs to leave their releases longer in alpha, as I have written about before. From what I can see vBulletin has done exactly that.

I am not sure what your point is for even bringing this up anymore. All I read was a complaint with no suggestions, when I have employees like this I get rid of them due to them wasting everyone's time. Install the latest release and spend your time here on a real issue -- there are many to choose from.

[Brandon Sheley]

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.

[ozzy47]

Originally Posted by Brandon Sheley

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.

Define anymore, as this has been around for 10 years. Some very popular developers that are no longer with the company, that are on their own now, activly developed the software knowing they were suppressing errors, and did noting about it either.

As it has been stated many times over, there in sot one software out there that does not do this in some way, at some point in the script.

Originally Posted by Brandon Sheley

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

Well either ignore the error, or add the suppression of the warnings to the includes/config.php file. Since it was this way for ten years, and no one said or did anything about it, including the former developers.