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.
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?
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.
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.
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?
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.
Quote:
Originally Posted by Disco_Stu
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.
09-07-2014, 05:58 PM
Linear Mode
