Buying vBulletin 6 months before major upgrade?

Do I think they'll make it? Maybe, but they might release it, despite it being in a pretty rough state.

On my computer, the currently active users box doesn't work on regular basis. Many times the member names continue right out of the box and cause my screen to scroll left and right.

Beta 3 and it's still not resolved yet.

 

I just fell outta mah chair! :monkey:

 

Honestly I'm really impressed with how fast they are moving. I'm focusing on beta4 for the moment.

The new guy they hired is making quick work of sorting through the bug tracker issues.

It will be close.

 

So who's actually going to purchase vB4 then? Even thought you feel unsure about their future and development structure?

 

Me.

I upgraded 1 of 2 licenses. I do not have to use it though. I get unlimited updates for v3 on the v4 license.

I can also use my v3 license under the v3 licensing terms as long as I do not download v3 updates for that license.

 

I was going to, but decided I'd save the money for Christmas shopping. Not only that, but if I upgraded to vB 4, I'd need a custom skin, which I cannot afford since I could hardly afford the $160 upgrade if I wanted it.

0 of 3 licenses have been upgraded; and it's going to stay like that. I just see no point in upgrading if I'm not going to use it.

 

I bought the upgrade and I'm regretting it right now. It's just not worth it for basically a glorified skin redesign with a hastily-done CMS added in. I'm thinking very hard about moving off of vBulletin altogether now.

 

I seriously was thinking about that too... (http://www.adminaddict.net/forum/vbulletin/really-dont-know-what-do-about-vbulletin-4-a-4892/) but decided to just stick with 3.8.x. If vBulletin makes a turn for the better, I'll consider jumping back on-board with 5.x.

 

I'be bought the upgrade but I'm having serious second thoughts about ever moving to vB4. It's just impossible to skin properly. The whole stylevar system is meaningless and not flexible enough. Why can't we easily add additional CSS definitions like before (for example)? And the new variable system might as well be chinese. How on earth is it better to change something like $variable[something] to {vb: var raw : variable.something } which is how I think it is now? It drives me crackers trying to fathom it all out.

 

I totally agree with you :p they know when their new vBulletin version would release but they did not and will not announce it because some people will just hold off their purchase and wait for the new version lol. I feel regret for someone :o who just purchased the vB 3x version few days before the vB4 was available for sale. It was like they paid 180$ for the owned license and after one year they will have to spend 170$ more to upgrade = 450$.

Oh I dont even think about the vBulletin version 5 now, few more years I guess lol.