[fixed] Most users ever online BUG

[noppid]

This code does not always give a non zero answer and this causes the "Most users ever online" to be reset to a lower number.

Original Code.

if ((int)$maxusers[0] <= $totalonline) {


Code repaired.

if ( (int)$maxusers[0] <= $totalonline && $maxusers[0] != 0 ) {


I posted about this on version 2.2.9 but the bug is still there.

[noppid]

I think I should have called the above a patch, not a fix. The solution seems to be finding out why $maxusers[0] evaluates to zero sometimes.

[Dean C]

How come this is being overlooked?

[Paul]

How come this is being overlooked?
Hah ;)

[Steve Machol]

It's not being 'overlooked'. It was moved into the Bugs forum specifically so it would be answered and addressed. Granted this is a bit slower than usual with all the work being done on vB3.

[Alien]

I guess no word yet. :(

[Rolodex]

This is really bad business. :(

[Paul]

This is really bad business. :( As has been stated a number of times, the developers have no intentions of producing a new release of vbulletin 2.x. It appears that there is no official bug-fixing support at this time of either 2.x or 3.x.

If you are concerned about seeing a fix or attention towards this or any other bugs, I'd highly recommend finding a way to exploit it and posting your findings on a security mailing list.

Otherwise, sit back and wait for them to finish having fun with Photoshop. You've got a projected date of sometime at the very end of this month (which can probably be safely translated to December if you're lucky) for the next release of vB3, which according to at least one developer, will have changes in the template structure itself, making retaining changes across versions practically impossible.

I think they're under the impression that this makes them look good.

[Steve Machol]

As has been stated a number of times, the developers have no intentions of producing a new release of vbulletin 2.x. It appears that there is no official bug-fixing support at this time of either 2.x or 3.x.That is blatantly unfair Paul. I spend 5-6 hours 7 days a week providing official support for vB2 and forum support for vB3 when I have the knowledge to do so. It's nice to know such hard work is appreciated. :rolleyes:

As I understand it, there will be a final release of vB2 after vB3 is released, just to clear up any remaining bugs. I believe this was done with vB1.x when vB2 was released.

At any rate, I cannot guarantee that each and every 'bug' will be fixed in the vB2 series. That would be like asking Microsoft to fix ALL bugs in Windows 3.1 before releasing Windows 95, or even going back after the release and fixing them. It just doesn't happen that way.

[Steve Machol]

As has been stated a number of times, the developers have no intentions of producing a new release of vbulletin 2.x. It appears that there is no official bug-fixing support at this time of either 2.x or 3.x.That is blatantly unfair Paul. I spend 5-6 hours 7 days a week providing official support for vB2 and forum support for vB3 when I have the knowledge to do so. It's nice to know such hard work is appreciated. :rolleyes:

As I understand it, there will be a final release of vB2 after vB3 is released, just to clear up any remaining bugs. I believe this was done with vB1.x when vB2 was released.

At any rate, I cannot guarantee that each and every 'bug' will be fixed in the vB2 series. That would be like asking Microsoft to fix ALL bugs in Windows 3.1 before releasing Windows 95, or even going back after the release and fixing them. It just doesn't happen that way.

[Paul]

That is blatantly unfair Paul. I spend 5-6 hours 7 days a week providing official support for vB2 and forum support for vB3 when I have the knowledge to do so. It's nice to know such hard work is appreciated. :rolleyes: When you start posting bug fixes to all confirmed bugs, I will be very appreciative of Jelsoft's efforts at providing bug-fixing support. Configuration issues and bug identifications aren't the issue here and I never suggested they were. The problem is the lack of regular maintenance releases.

To me, this particular bug is trivial, but it has been identified as a bug and is a problem for other license holders. Given that they only have the option to run either vb2 OR vb3 and that they can only expect official support for vbulletin 2 you leave me in no other position but to critize what I view as another case of gross mismanagement. Officially support vbulletin 3 and publish bug fixes or continue releasing fixes for vbulletin 2.

As I understand it, there will be a final release of vB2 after vB3 is released, just to clear up any remaining bugs. I believe this was done with vB1.x when vB2 was released. And where has this been communicated to end-users? I'd cite a recent direct quote from Wayne Luke on the subject, but apparently the search engine here likes to just sit and timeout. I have seen comments made by developers on this forum that clearly state that there is no intention to release any further vbulletin 2.x updates. Period.

At any rate, I cannot guarantee that each and every 'bug' will be fixed in the vB2 series. That would be like asking Microsoft to fix ALL bugs in Windows 3.1 before releasing Windows 95, or even going back after the release and fixing them. It just doesn't happen that way. Microsoft supports legacy versions until well after new versions are released. Microsoft produces regular security updates and product fixes. Microsoft provides a knowledge base of issues with their products and suggested workarounds. Microsoft doesn't stop supporting current "stable" versions or providing fixes for such until well after the new product has been established as a stable product and is available in retail. Microsoft, comparitively speaking, has their act together.

Jelsoft has placed us all in a position where we can't get updates for vb2 and we can't get updates for vb3. What do you expect the response to be?

[Mike Sullivan]

I have seen comments made by developers on this forum that clearly state that there is no intention to release any further vbulletin 2.x updates. Period. My opinion has always been that each release is intended to be the final release. If things crop up, we've always held the option of doing another release. (Of course I know what you're going to say to this; see below.)

Jelsoft has placed us all in a position where we can't get updates for vb2 and we can't get updates for vb3. What do you expect the response to be? I can't say I particularly agree with the part about vB3 updates as there is very clearly going to be an update for it.

But, I will be going through these remaining bugs in the near future and evaluating the possibility of another bug-fix release.

[Paul]

My opinion has always been that each release is intended to be the final release. If things crop up, we've always held the option of doing another release. (Of course I know what you're going to say to this; see below.) This is an excellent viewpoint. It's based on real things instead of arbitrary numbers. Of course it's just your opinion.

There will be bugs in your bug fix release. That's a given. What boggles me is the general notion that any of these files are anywhere near perfect form. There will always be issues, which is why it's so important that the product continues to be updated. 2.3.2 is full of bugs that Jelsoft already knows about and it was released in the beginning of August.

I can't say I particularly agree with the part about vB3 updates as there is very clearly going to be an update for it. When? Today? Tomorrow? No, "late November." At least another month, and probably in an unusable state because there weren't any interim releases to continue testing for bugs. If I thought for a second this "Release candidate" was going to operate "as advertised" I wouldn't have a problem with this. But it won't. There will be "CVS issues," or "last minute patches" or "If you downloaded it within the last 4 hours, do it again and run these three scripts." And you'll get another slurry of bug reports that overwhelm developers into another month of testing, something that could have been avoided had continuous beta releases been made. This "Christmas" fantasy won't happen if we are to wait until November for the next set of updates.

I don't doubt that there will be another vb2 update, but that's only because I've been around here long enough to see how this place works. And if I recall correctly, 2.3.1 and .2 were rather reluctant releases as well. I don't think for a second that all, or even a majority of license holders regularly browse these forums.

So, yes, at least a month of having no choice but to 1. Fix it yourself, 2. Live with identified issues. Great value for $30.

But, I will be going through these remaining bugs in the near future and evaluating the possibility of another bug-fix release. Oh that's great. I'm glad to hear that Jelsoft will be "evaluating the possibility" whether or not they are going to tell their users how to fix these issues, or whether they want to continue to sell and support software with known bugs. Do us a favor and at least let us know what conclusion you all come up with.

[Mike Sullivan]

I've made similar changes to the first post and added a little bit more code in hopes of preventing this problem from occuring. I'm still trying to analyze why $maxusers doesn't get evaluated correctly though.

[Rolodex]

This code does not always give a non zero answer and this causes the "Most users ever online" to be reset to a lower number.

Original Code.

if ((int)$maxusers[0] <= $totalonline) {


Code repaired.

if ( (int)$maxusers[0] <= $totalonline && $maxusers[0] != 0 ) {


I posted about this on version 2.2.9 but the bug is still there.

This code doesn't work either ... what's the deal here guys? It had been working on up to daylight savings time October 2003, then miraculously, it stopped. $167 for this kind of service ... now I see why this board code is constanly pirated. Who wants to pay all of this money for this product, and then get lame support. You guys put more effort tracking down pirated copies of this software than you do trying to give support to us paid users.

Get you priorities in check and give us the service that we paid for. My suppot help is going to expire thi month, and this issue has been going on for some time. :mad:

[Mike Sullivan]

Please send me FTP access then and I'll see if I can figure out what's causing it.

[ManagerJosh]

Get you priorities in check and give us the service that we paid for. My suppot help is going to expire thi month, and this issue has been going on for some time. :mad:
I think you would need to address all the priorities in general and look from a bigger standpoint. From what I've observed, Jelsoft does an excellent job in fixing bugs that have significant threat to the security of vBulletin in addition to a superb job on fixing other bugs that affects the usability in vBulletin. I feel this is a trivial bug and technically can be put on the backlot for a while so that other bugs (which has slighly more importance) can be addressed

Now you have to understand they also have a dev team who's working hard on vBulletin 3, and that everytime they release a version of vBulletin 2 is because something came up unexpectedly (like a DDoS attack) that pushed the release date back.

Everytime they release the final version of vBulletin 2 is because they felt it would it is time to move on to a newer even more stable platform with more features, enhanced coding, and a more superior product.

I feel their priorities are straight and I wouldn't be surprised Jelsoft gets daily emails in regards to potential security threats and majority of the time it turns out to be bogus (takes time to sort these things out)

Rolodex, I can assure you that they don't give you the service you paid for. They give you service BEYOND what you pay for and I can say without any doubt that they do their job, and they do it well. Heck, if I ever started a business, I'd use their business model.

Oh and Rolodex, your support doesn't expire. Just your members area download ability expire :)

[amgqmp1]

I'm totally confused as to why you are all complaining about not getting your money's worth, about show-stopping bugs in the 2.x code base, etc.

My two cents...

1 - I don't remember exactly what we paid for vBulletin, but, I think we've gotten our couple hundred bucks out of it (and then some). I've yet to pay for an update/upgrade to vBulletin and it's been the best code I've ever bought. Period.

2 - One-on-one involvement in these forums by the dev. team is overkill by my standards, however, the fact that they are going way over reasonable expectations is commendable.

3 - Whether you use vBulletin as a hobby-board or whether it's a mission-critical component of your business I don't think anyone can fairly say that the current release version (2.3.2) has any show-stopper bugs. That being said, I thought 2.3.2 was the end of the road for 2.x and I would have been fine with that. 2.3.3 is coming soon? That's some decorative icing on an all ready well crafted cake.

4 - I think it's obvious to anyone that the Jelsoft group is a very passionate group of developers. Perhaps if they weren't put in a position where they were defending their every slightest decision 100x/day then the code would come out at a slightly more rapid pace.

That's how I feel after reading a few threads here this morning. I personally look forward to a bright future with Jelsoft's products. It's been smooth sailing so far. :)

[poolking]

amgqmp1 - You will find that 2.3.3. is a maintenance release to fix small bugs.

[Mike Sullivan]

I've made similar changes to the first post and added a little bit more code in hopes of preventing this problem from occuring. I'm still trying to analyze why $maxusers doesn't get evaluated correctly though.
I'm going to assume that my changes have fixed this issue. If you are still having problems, let me know.