Upgraded to 4.2.2 problem with stylevar

[lsti]

Hey, i upgraded my board to 4.2.2 but i am not able to edit variables in style var.

Also i get this error.

Warning: Declaration of vB_DataManager_StyleVarDefn::delete() should be compatible with that of vB_DataManager::delete() in ..../includes/class_dm_stylevar.php on line 233

Warning: Declaration of vB_DataManager_StyleVar::save() should be compatible with that of vB_DataManager::save() in ..../includes/functions_log_error.php on line 615

Fatal error: Call to undefined method vB_DataManager_StyleVarSize::() in
/includes/class_dm.php on line 495

[ozzy47]

Read this ;

http://www.vbulletin.com/forum/forum...66#post4000466 (http://www.vbulletin.com/forum/forum/vbulletin-announcements/vbulletin-announcements_aa/4000121-vbulletin-4-2-2-full-has-been-released?p=4000466#post4000466)

[Paul M]

The first two are warnings that flash up, but wont do any harm. Please log them in Jira though.

The fatal error is a mystery.
I cannot replicate that, and that class does exist - it is defined in class_dm_stylevar.php

[sp1der]

Hi there,

I have the same 2 warning and realized my download (exported) style even default style the <stylevar> </stylevar> is completely empty.

am i the only facing this?

[SiFor]

Hi there,

I have the same 2 warning and realized my download (exported) style even default style the <stylevar> </stylevar> is completely empty.

am i the only facing this?

Yes I have to exact same issue, did you find a fix?

[Slayerz]

Add define('SKIP_ALL_ERRORS', true); to your config.php file

[deathtrancer]

I got the same problem, so If I skip these errors, and after changing my settings will follow?

because on my case even if I change my doc_width and doc_margin to my set up these errors will flash and no effect at all on my desired width

https://vborg.vbsupport.ru/external/2013/12/14.jpg

thanks

[fatherofspeed]

This cured my issue as well. Thank you all very much.

[ozzy47]

Glad you got it sorted. :)

[Brandon Sheley]

I just upgraded a clients site to vb 4 and we're upgrading the vb3 style with vbulletin's built in upgrade tool. I went to go change out the logo and I get the Declaration errors mentioned a year ago in the OP... The advice is to hide PHP errors?

It seems it would be better for the company to fix the problem, not hide it.. :down:


actually it seems when I edit any stylevar.. well this will be an annoying job.. I'm sure the client will be asking me what the hell is wrong with vb4 when they see them too.. Thanks vBulletin :mad:

[ozzy47]

Those are not errors, but warnings. They have always been suppressed it was just recently with PHP newer versions, they started showing again.

[Paul M]

I just upgraded a clients site to vb 4 and we're upgrading the vb3 style with vbulletin's built in upgrade tool. I went to go change out the logo and I get the Declaration errors mentioned a year ago in the OP... The advice is to hide PHP errors?

It seems it would be better for the company to fix the problem, not hide it.. :down:


actually it seems when I edit any stylevar.. well this will be an annoying job.. I'm sure the client will be asking me what the hell is wrong with vb4 when they see them too.. Thanks vBulletin :mad:
Regardless of your predictable rant, if you want to fix it, use the advice given.
You should however use SKIP_DS_ERRORS rather than SKIP_ALL_ERRORS, that restores the warning reporting to the same as used by vb2, vb3 and vb4 versions other than 4.2.2.

[Disco_Stu]

I have to throw my two cents in here:

I run my own software business and have over 30 years experience developing software. I develop systems for telecoms, railroads and manufacturers and I can tell you that if I started suppressing errors instead of addressing and correcting them I would be out of business tomorrow.

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.

Would you want your plumber or auto mechanic to hide problems from you? Of courses not.

Ask yourself this: When you were first thinking about purchasing vBulletin and you found out that error messages were being suppressed would you still be willing to purchase it?

[doctorsexy]

Ask yourself this: When you were first thinking about purchasing vBulletin and you found out that error messages were being suppressed would you still be willing to purchase it?
Reply With Quote

The answer to that is, no.....

[ozzy47]

Well then there is not much web based software you would purchase then, as it has been a common practice for ever. If it was so bad, then the blame should fall on the people who created PHP, as they made it so the warnings could be suppressed. :)

[Disco_Stu]

Well then there is not much web based software you would purchase then, as it has been a common practice for ever. If it was so bad, then the blame should fall on the people who created PHP, as they made it so the warnings could be suppressed. :)

Most software development environments have the ability to suppress error messages. They also provide the ability to write completely illogical spaghetti code too but that doesn't mean it's good practice to use either option.

[ozzy47]

Leave my spaghetti code out of this. :p :)

[tbworld]

I have to throw my two cents in here:

I run my own software business and have over 30 years experience developing software. I develop systems for telecoms, railroads and manufacturers and I can tell you that if I started suppressing errors instead of addressing and correcting them I would be out of business tomorrow.

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.

Would you want your plumber or auto mechanic to hide problems from you? Of courses not.

Ask yourself this: When you were first thinking about purchasing vBulletin and you found out that error messages were being suppressed would you still be willing to purchase it?

I do not believe that anyone was promoting masking constructional errors. The discussion (as I interpreted) was about interpretive/compiler warnings. Maybe I just misread. :)

[Mark.B]

I have to throw my two cents in here:

I run my own software business and have over 30 years experience developing software. I develop systems for telecoms, railroads and manufacturers and I can tell you that if I started suppressing errors instead of addressing and correcting them I would be out of business tomorrow.

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.

Would you want your plumber or auto mechanic to hide problems from you? Of courses not.

Ask yourself this: When you were first thinking about purchasing vBulletin and you found out that error messages were being suppressed would you still be willing to purchase it?
Well it was common knowledge when vBulletin 3 was released. Nobody seemed to mind then.

[ForceHSS]

I have to throw my two cents in here:

I run my own software business and have over 30 years experience developing software. I develop systems for telecoms, railroads and manufacturers and I can tell you that if I started suppressing errors instead of addressing and correcting them I would be out of business tomorrow.

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.

Would you want your plumber or auto mechanic to hide problems from you? Of courses not.

Ask yourself this: When you were first thinking about purchasing vBulletin and you found out that error messages were being suppressed would you still be willing to purchase it?
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

[Disco_Stu]

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]

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]

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]

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]

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]

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

[Spinball]

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

When did you *start* trusting them? I stopped trusting the vb development team when most of them left in 2009, and nothing released since has gained it back.

[BirdOPrey5]

First- no matter what- even when staff accidentally say we have been suppressing errors since 2002, they mean warnings. PHP warnings. We have been suppressing warnings only. Warnings don't stop execution of the code, warnings don't hurt anything. Most are in fact deprecation warnings that just say "Hey, this code still works but one day you will need to change it."

All forums used in production environments should be setup to suppress warnings and errors to begin with for security reasons- that is good practice. Only development environments should be showing warnings and errors.

Our competitors also suppress warnings in their software in normal modes. It is common practice is all PHP software.

4.2.2 was the first time in a long time many of the long-standing issues were addressed. Everyone who is saying "how come you didn't fix it instead of hide it" well 4.2.2 (and 4.2.3 now in beta) are the result of actually fixing the issues rather than hiding them.

[Alfa1]

I have been running vb3 on my big board since 2005 and have not suppressed error reporting. So stating that errors were hidden since 2002 is complete nonsense.

You can spin it however you like, but warnings are intended so that the developers pick up on it and do something about it. It is not good practice at all to hide warnings.

Deprecated errors are a big sign on the wall that the software you run is getting outdated and should be either fixed or replaced by modern software. Because sooner or later your server software like php version will be EOL and you risk all. PHP 5.3 is already EOL. PHP 5.4 will be.
Just like YUI2 has been EOL since 2009 and YUI is abandoned now (http://yahooeng.tumblr.com/post/96098168666/important-announcement-regarding-yui). But we see no rewrite going on replacing YUI with jquery. Its just waiting for the hammer to fall.
Hiding the warnings is like fixing the security vulnerability by completely removing the install folder. It sort of works, but it evidently shows that quick hacks are provided instead of quality development.

In the case of vb4 you can wait until it stops working, hope that Internet Brands actually fixes up vb4, releases a quality vb6 or draw your conclusions based upon the current situation.

[ozzy47]

So you are saying, you went in the core files, and removed the suppressed warning code that was in there?

Note, we are talking warnings, not errors, they are two totally different things. :)

[Disco_Stu]

You people have got to be kidding me. What software company would actually tell it's customers that they are actually suppressing error and/or warning messages? Clearly you need to learn how to run a business.

Under no circumstances is it justifiable in my book to suppress these warnings and errors. The whole purpose of a warning message is to alert you that a condition exists that is not correct. Why then would you want to ignore it and not correct the condition that caused the message to be displayed?

Can you provide any reasonable explanation as to why these conditions are not addressed ? As a customer who paid a lot of money for this software package I expect it to work WITHOUT errors and warnings.

[ozzy47]

If warnings were not suppressed, every time your server had a php update, it would probably throw up a bunch of warnings, due to the new php coding. Then everyone would be crying that there is warnings all over their sites.

Sure the vB code should try and accommodate for all of this, but sometimes it is not feasible.

When I write my mods, I try to make sure everything is correct, but sometimes I even overlook stuff. :)

[Disco_Stu]

If warnings were not suppressed, every time your server had a php update, it would probably throw up a bunch of warnings, due to the new php coding. Then everyone would be crying that there is warnings all over their sites.

Sure the vB code should try and accommodate for all of this, but sometimes it is not feasible.

When I write my mods, I try to make sure everything is correct, but sometimes I even overlook stuff. :)

Mods are not what I am talking about. Mods are free and when you accept free software you accept it as is for FREE with no expectation of bug free software.

When you PURCHASE software then you should be at the very least be told BEFORE THE PURCHASE that warnings and/or errors exist and are being hidden. Not telling a potential buyer that these conditions exist is tantamount to deceptive selling practices.

Also, how do you explain the comments from Zachery a vBulletin Support Staff member that, and I quote:

"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. "

He is actually saying that they are selling software containing code that they know nothing about. Unbelievable!!! Not only is he saying they are marketing a product they do not fully understand but that they apparently do not have the skills necessary to understand it.

How do you rationalize that?

[ozzy47]

I don't comment on what he has said, as it is something he said, I will leave it to him to to explain that one. :)

[Alfa1]

When I write my mods, I try to make sure everything is correct, but sometimes I even overlook stuff. :)
Which is exactly why its great to have error reporting turned on. If I upgrade one of the 110 addons that I run and it causes a warning or error, then its good to have that clearly in sight. Because if I do not encounter the warning then one of my 3.5 million readers will instantly notify me. This allows me to quickly report the bug to the developer and have it fixed.

[DemOnstar]

Getting it fixed is what the error reporting thingy is (or should) be all about.

Or is it more about getting the error report and ignoring it?

What is the point of including the error report mechanism if nothing is going to be done about it?

I mean, from the nobs that included the error report, I am guessing that there was a reason for it to be included.

[ozzy47]

Everyone still is referring to errors, which is wrong and completely different from warnings, which is what has been suppressed. :)

[DemOnstar]

Everyone still is referring to errors, which is wrong and completely different from warnings, which is what has been suppressed. :)

And a warning means?

As far as I understand, a warning is something that people, generally should pay attention to.

Allow me to illustrate. . . .

http://b4thethrone.webng.com/Graphics-C/BridgeOut.jpg

[ozzy47]

Most of them are warnings telling you something might be depreciated, but that does not necessarily mean that it is going to stop working. I am trying to defend anything, just trying to make sure everyone understands it's not errors that is being discussed. :)

[Disco_Stu]

Most of them are warnings telling you something might be depreciated, but that does not necessarily mean that it is going to stop working. I am trying to defend anything, just trying to make sure everyone understands it's not errors that is being discussed. :)


OK....let me ask you something. If vBulletin said in it's advertisements that some warning messages are intentionally being suppressed would you still be willing to purchase the software not knowing what those warning conditions were?

[ozzy47]

Yes, as I knew this was being done in the early stages of vB3 when I was a admin on various sites. I then proceeded to purchase my own vB license, and have since then purchased 2 more, one of which was vB5, and TBH I wish I would have waited on that till it was stable. :)

[DemOnstar]

vB 5. TBH I wish I would have waited on that till it was stable. :)

Really don't want to be pedantic here but we are talking about a platform that is a hell of a lot more popular/used/viable/functional than the example quoted above.

[Disco_Stu]

Yes, as I knew this was being done in the early stages of vB3 when I was a admin on various sites. I then proceeded to purchase my own vB license, and have since then purchased 2 more, one of which was vB5, and TBH I wish I would have waited on that till it was stable. :)

Well, would you still be willing to purchase it if you knew that the current staff has no knowledge of some of the code included and apparently cannot support it - according to a current staff member?

[ozzy47]

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.

Well, would you still be willing to purchase it if you knew that the current staff has no knowledge of some of the code included and apparently cannot support it - according to a current staff member?

Where does Zachary say it can not be supported? From what I read he says the suppressing of the warnings was turned off, and sure some went unnoticed. This is bound to happen as code acts different on various servers due to different configurations. :)

And yes I would still but another license if I needed to, but I don't. ;)

[doctorsexy]

Then everyone would be crying that there is warnings all over their sites.


Well better late than never....:D

When does an error become a warning ?

[ozzy47]

True, but hopefully with the latest release of vB4 they are all fixed. :)

[Disco_Stu]

Where does Zachary say it can not be supported? From what I read he says the suppressing of the warnings was turned off, and sure some went unnoticed. This is bound to happen as code acts different on various servers due to different configurations. :)

And yes I would still but another license if I needed to, but I don't. ;)

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

[ozzy47]

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

[Mark.B]

OK....let me ask you something. If vBulletin said in it's advertisements that some warning messages are intentionally being suppressed would you still be willing to purchase the software not knowing what those warning conditions were?

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 1410124101 at 1410124101 ---------------

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

Utter rubbish.

[Disco_Stu]

Where does Zachary say it can not be supported? From what I read he says the suppressing of the warnings was turned off, and sure some went unnoticed. This is bound to happen as code acts different on various servers due to different configurations. :)

And yes I would still but another license if I needed to, but I don't. ;)

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 1410124101 at 1410124101 ---------------



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.

[Mark.B]

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.

[Disco_Stu]

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?

[Paul M]

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.

[ozzy47]

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?

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.

[Mark.B]

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?
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.

[Disco_Stu]

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.

Understood

[Brandon Sheley]

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]

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]

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]

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]

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.

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.


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]

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.



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.

[Brandon Sheley]

carry on.. everything is fine :rolleyes:

[ozzy47]

We did carry on, you were the one that replied to a thread that was last replied to over two months ago. :p

[Brandon Sheley]

We did carry on, you were the one that replied to a thread that was last replied to over two months ago. :p

haha.. that just makes it that much sadder.. :rolleyes:

We'll just give it 2 more months and maybe the warning will vanish again..LMAO

[ozzy47]

Good grief, you just don't get it.

[Brandon Sheley]

See that's where you're dead wrong. I do get it, but then again I'm not brainwashed like some fan boys these days. ;)
I may not be active these days on the org but at one time I was and was a big supporter of vbulletin. Then it went to crap and many of us left.

Enjoy the dust

[ozzy47]

Ok lets look at your flavor of the month software.

There are a number of application configuration options that are in the library/config.php file. These are advanced options and should be modified with care.

Incorrect configuration of these options may render your XenForo installation unusable. If you run into any problems, undo your modifications.

If you wish to modify any values in your config.php file, simply add a line to the end of the file. This guide assumes a basic understanding of PHP syntax.
$config['db']['adapterNamespace'] - default: 'Zend_Db_Adapter'
Controls database connection adapter class that will be used.
$config['cache']
This is discussed in the Defining a Cache (https://xenforo.com/help/cache/) section.
$config['debug'] - default: false
Controls whether debug mode is enabled. Debug mode gives more access to error messages, debugging/performance information, and development tools. It should not be run on a production forum as it may degrade performance or even open up security issues.

Not this is interesting, Debug mode gives more access to error messages

Why would I need more assess to error messages if they are not suppressed somewhere? If they are not suppressed, then why is debug mode needed to show them? Is it magic?

[Brandon Sheley]

Not sure why on earth your talking about xenforo. Are we drinking early tonight?..lol

[ozzy47]

Well you seem to think only vBulletin suppresses errors, so I am pointing out that is not the case. :)

[Brandon Sheley]

Well you seem to think only vBulletin suppresses errors, so I am pointing out that is not the case. :)

I never said that, but feel free to think that's what I said. :up:

[ozzy47]

Then what is the issue, as it had been stated, every software suppresses warnings in one way or another. If you have a issue with that, take it up with the developers that write PHP, and ask them to remove that functionality in the next version of PHP they release.

[Brandon Sheley]

I appreciate the effort ozzy, I honestly do.

carry on

[ozzy47]

I appreciate the effort ozzy, I honestly do.

carry on

I would suggest the same to you. :)

[Brandon Sheley]

I would suggest the same to you. :)

I'll pass that along to my paying customer again in the morning. :up:

[ozzy47]

What does that have to do with anything?

[Brandon Sheley]

I give up.. enjoy the evening

[ozzy47]

You to, have a good night. :)

[BirdOPrey5]

This thread has run its course.