vBulletin 4 or vBulletin 5?

The IE10 issue is fixed in vB 4.2.1

 

AFAIK, the issue was worked around in 4.2.1 by forcing IE10 in IE9 mode. The actual Jira for the issue is closed off to the public (so not fixed) and there is also at least one customer still complaining about IE10 not working properly.

Scott

 

Ah right, so all they are doing is forcing IE10 to go into IE9 compatibility mode. Typical, rather than fix the problem proper. lol

 

You may be right. I've had no complaints with vB 4.2.1 from IE10 users on 5 forums.

 

Well, maybe the work around is also satisfactory enough and the person who was complaining has another issue altogether.

Scott

 

Neither.

 

Thats pretty much correct, it was added in as a stop-gap in 4.2.1, until such time as a proper update to CKE4 could be looked into.

 

That is fine Paul, but when is the correct correction (with or without CKE4) going to happen? I think the least amount of customers would have any issues with vB4 (or IB), if a clear strategy to get vB4 straight with some of its worse issues would be clarified. i.e. a clear signal that vB4.2.2 is being worked on and will be released and what that release will entail. To most customers it seems vB4 is seriously dead in the water and they are also propagating that information all over the internet. That needs to stop, especially in your own interest (like keeping your job).

Scott

 

I had my system admin upgrade our 4.2.1 to the latest version of CKE4 a few weeks ago. Not sure what he did but it works, and its not a band aid like vBulletin did to foce IE 10 into IE9 mode.

 

Wouldn't that be great, AFAIK vb4 hasn't been worked on since vbulletin 5 was "released"..

 

Not quite accurate - vB 4.2.1 was released with several fixes after the 5.x release(s) - can't recall what version of 5 had been released but 5.01 or 5.02 I think.

 

All those fixes were completed a long long time ago and sat on the shelf while everyone was focused on vb5.

I honestly don't think much/any work or thought has been placed in to vb4 since it forked off of vB 4.1.5 or whatever it was.

 

Not true.

This is complete tosh.
Myself & Freddie spent over a year working purely on vB4, from 4.1.5 - 4.2.1.
We made a massive amount of changes, bug fixes (almost 2000), improvements & new features.

 

So Paul... what happened?

 

I wouldn't touch vbulletin 5 for at least another year (if it last that long)
At least they fixed the annoying bug that all pages in a thread had the same URL.. That was an amazing bug..lol

 

Can you be a little more specific.

 

And then you get the same scenario like with vB4.2
It got usable,People start to like it, . Even i said "ok it's getting better and there's little trust again" and what happened then? All resources where moved to the next major version. And the same scenario, which we had with vB4 started to repeat......

 

I know the answer.

Scott

 

The answer to the question

is....

IB's management either made another one of their epically poor decisions or there is a complete lack of any decision made on the direction of vB4 altogether.

Paul also said, he mentions the need to get vB4's PHP compatibility straight to the upper management, when he can and I am sure the support team do it too. But obviously, the upper management haven't taken him, the support team or the last few "vocal minority" customers complaining (or me, with a personal email to Bob himself) about the close to criminal stupidness of not fixing vB4's missing PHP compatibility seriously. As I and other customers have said before, this issue shouldn't even become one with a software like vB. Compatibility of newer PHP versions should be a part of the development and testing processes.

And the even more stupidness about all this is, some people tend to think IB is trying to leverage this PHP incompatibility to make customers buy vB5, and at the same time, vB5 simply isn't yet a viable product for customers using either vB3 or vB4 to move to, so what is the final result? Customers move away to products and companies that support them better.

It is so amazingly bad management of a product, it is almost unbelievable, because the people behind IB aren't stupid. I just think they have totally wrong motives. I mean, how can you sit there and not do what is a fairly simple release for the most major issue you have and still watch customers get more and more upset because of it and also move away from the product as "the last straw"? Simply put, it is idiotic.

Scott