New version ? 2.0.4. ?

[webmaster20923]

Hello,

i am interested in buying a vbulletin version for my website, but i saw that there are very many bugs in the actual version 2.0.3.

That is why, i would like to know, when does an update comes out?

What will be new in the new version?

When will this new version appear?

Thanks

[Raz Meister]

It was supposed to come out when John and James came back from whereever they went. They're back...so it should be anytime soon.

[webmaster20923]

october?
november?
december?

[Wayne Luke]

October.

There have also been very few minor bugs in 2.0.3. Most things that people have called bugs are actually either server problems outside of vBulletin or configuration issues within the software.

That is one reason why there hasn't been a release yet. The release will consist of bug fixes only. There is no exact date for its release.

[ying_ho]

That's great it will come out in October.

I would buy a copy of it.

[Kengan]

When 2.04 will come out ?

[Chen]

Originally posted by wluke
October.

[Tommy Boy]

I am interested to know, especially in light of what wluke said, if the new version will finally support manual marking of read forums.

I want to have a link in each forum called "Mark forum read", in addition to the already existing "Mark ALL forums read" link in the main page. Then, I don't want a thread to become automatically read when I read it.

I run a support forum, and sometimes I can't give a direct answer. I have to find out the answer, and post it sometimes days later. Therefore I want this thread to still be marked as unread, even if I already read it, until I manually tell it otherwise.

I think a lot of people will agree with me that the current new posts notification system, which is cookie based, is very restricted and limiting.

[Steve Machol]

The next version (2.0.4) will be for bug fixes only and will not contain any major new features such as manual marking of read forums.

[RCK]

Originally posted by smachol
The next version (2.0.4) will be for bug fixes only and will not contain any major new features such as manual marking of read forums.
:(
I suppose we have to wait for vB 3.x for this kind of missing feature...

[Tommy Boy]

Hmmm... This is a longshot, but how about using the hack someone wrote for this, make sure it works right, and make it official in the next release? :D

I was already in the payment page, all my credit card info already inside, just about to click the submit button, when my friend pointed me at this missing feature on ICQ... :eek: Turned out he was right. Our current board supports this feature, so switching to vBulletin means going a step back, as far as this feature is concerned.

Please tell me you will do it, and let me buy the damn thing already! ;)

[ethank]

I offered to give them my code, but never heard back from them.

I haven't had a chance to thouroughly document it because of layoffs, etc and how extensive the code additions/changes were (sorry everyone!).

It wasn't hard to implement, but took extensive changes. I'm hoping to have free time coming up, but nothings guranteed yet.

Ethan

[Freddie Bingham]

v2.0.4 won't include this functionality.

v2.1 probably will probably make some changes to system though. While we welcome ideas, we don't really have a need for donated code. Writing the code is the quick part of the problem, creating something that works on 1 million post forums is what takes most our time in this sort of project.

[ethank]

Originally posted by freddie
v2.0.4 won't include this functionality.

v2.1 probably will probably make some changes to system though. While we welcome ideas, we don't really have a need for donated code. Writing the code is the quick part of the problem, creating something that works on 1 million post forums is what takes most our time in this sort of project.

No reason it wouldn't work on a 1,000,000 post forum, since it just replaces a cookie comparison with a database lookup.

Ethan

[Raz Meister]

Better to be safe, than sorry ;)

[Wayne Luke]

Originally posted by ethank


No reason it wouldn't work on a 1,000,000 post forum, since it just replaces a cookie comparison with a database lookup.

Ethan

Actually optimizing those database lookups is what Freddie was referring to. On a busy board one .3 second lookup can add 10-20% to the load average of the server if it isn't done correctly.

[DVD Plaza]

I for one am VERY pleased and VERY grateful that Jelsoft will only be making bugfixes in 2.0.4 - I find it unacceptable that I would need to make extensive template changes just to install bug fixes. The 2.0.2 and 2.0.3 "fixes" quite frankly pissed me off immensly with the amount of template updates I had to make, even now I still haven't got around to doing them all - only did what was necessary to keep things going.

2.1 I would expect to have to make changes for, however a bug fix I wouldn't expect to contain a single new feature what-so-ever. Even Microsoft now committ to now adding new functionality to their OS with service packs.

[ethank]

It usually takes me about 2 days to do an upgrade because of all my hacks and template mods. The nice thing is Jelsoft's release notes always have a template-by-template change documentation and are quite thourough with what other changes they did.

I basically spend a day in Araxis Merge doing code comparisons and going through all my templates doing diffs, then another day testing. I'll probably use this 2.0.4 upgrade as an excuse to upgrade MySQL as well :)

However, this upgrade is going to be a bit of a pain because I have 2 CVS forks of vbulletin code to change. One without many hacks and one with a lot of them.

:eek:

Ethan

[tubedogg]

Originally posted by DVD Plaza
[B]I for one am VERY pleased and VERY grateful that Jelsoft will only be making bugfixes in 2.0.4 - I find it unacceptable that I would need to make extensive template changes just to install bug fixes. The 2.0.2 and 2.0.3 "fixes" quite frankly pissed me off immensly with the amount of template updates I had to make, even now I still haven't got around to doing them all - only did what was necessary to keep things going.2.0.2 was never intended solely as a bug-fix release, and 2.0.3 only included new features because work had already started and it wasn't worth trying to rip features out and inadvertantly creating bugs.
Bug-fix releases often require template changes as well. There really wasn't that much changed as far as templates in those two versions - it was more of "add/remove a word here" type changes.