is there going to be a vbulletin 2.2.7?

[Dimava]

I'm thinking about adding a lot of "hacks" to a site that I admin, but before I do, I want to know if there will be a 2.2.7


thanks,

Dimava

[ccd1]

Why does it matter?

[Dimava]

because if I hack up 2.2.6, and then 2.2.7 comes out, it means i'll have to reapply all the hacks again

[leadZERO]

Search the forums this has been asked a number of times already.

[ccd1]

That's not completely true. I've had hacks from 2.2.3 that have carried on to 2.2.6 flawlessly.

The only way the hacks stop working is if they're replaced--before you upgrade, check to see what files and templates will be replaced and if yours is there, then you will have to reinstall it.

The thing is when vB3 comes out, you will have to redo everything.

[Dimava]

no, I mean I'll have to edit all of the 2.2.7 files again

[ccd1]

I know what you mean and I just told you that you don't have to. You only have to upload the files that changed.

[Freddie Bingham]

Yes there will be a 2.2.7 released this month.

[hypedave]

Originally posted by freddie
Yes there will be a 2.2.7 released this month.

Wow I dont believe it, I was actually right for a change, well im glad to hear that I was right on a vb 2.2.7 being released soon.

[Dimava]

Originally posted by freddie
Yes there will be a 2.2.7 released this month.

Thanks, just what I wanted to here :cool:

[TObject]

I can’t believe it!

Maybe instead of releasing new versions so often you guys need to concentrate on testing and quality control.

Just a suggestion...

[John]

I'm sorry if you feel 2 months is too short a time between releases. There is also no obligation to upgrade if you do not want to.

All the best,
John

[hypedave]

hey all I gotta say is keep up the good work, its takes alot of hard work to fix things, especially when there are so many different vb configurations out there. You guys coud have easily looked over certain problems, but you didnt.

[bigmattyh]

Maybe instead of releasing new versions so often you guys need to concentrate on testing and quality control.It's very easy to criticize; doing a job well is much harder.

At any rate, great work, vB team! I'm very much looking forward to vB3, as is just about everyone else, and I'm sure we'll have a whole lot more to applaud you on soon. :)

[The Prohacker]

Originally posted by TObject
I can’t believe it!

Maybe instead of releasing new versions so often you guys need to concentrate on testing and quality control.

Just a suggestion...


Actually, its standard to make a final release of a version line..

Fix all last bugs, etc, before they release vB 3 into beta testing :D

As I remember a developer saying, most of us won't care about the 2.2.7 release because we'll be doing something else :D

[Floris]

It is impossible to 'test' for each possible situation and/or bug/exploit/securityflaw. It will take years, and in those years, new PHP versions etc are released, and that means more updating and doing the majority of those tests again.

Fixing little errors over time and giving users the oppertunity to manually apply them (see bug forum) or wait for a complete update (2.2.7 i.e.) is nothing more then normal and a great effort from the developers and the vB team behind them. I would hate to register today, download 2.2.2 because they maybe wanted it to be final. Install it on my new dedicated hosting with high costs, to find out that it is not working with PHP 4.2.2 Instead, I am happy to see that 2.2.7 might be there, working with all the latest releases, and those little annoying typo's / bugs / tweaks applied/fixed. Wee. And if I have to upgrade 1 week later to 2.2.8 because a new security flaw has been discovered with 4.2 or some MySQL/Apache version, gee np. If you complain about having to re-apply the hacks, then it is up to you to make it more simple. Keep a little database (read: piece of paper) with changes made per hack. This way re-applying them is so easy. // comment your lines where they start and end, and include any mysql table changes. How hard can it be. Saves a lot of complains too. There is no NEED to upgrade to 2.2.7, no real security issue's or anything. The choice is always yours. Because even when security issues could be fixed with upgrading to 2.2.7, Jelsoft says 'we highly advice', and I read nowhere 'HAHA, all lusers MUST upgrade' or whatever.

I am glad I am able to report issues with the software, and seeing the developers care enough to fix it and include it in their next release. I know enough companies that immediatly drop support on their product, as soon as they think about a new version.

What I wanted to say.
Personally I am happy with the trouble and time Jelsoft members have put in their product. Thank you for this. It makes the purchase worth its money.

[TObject]

Originally posted by bigmattyh
It's very easy to criticize;

But I like to criticize.

:rolleyes:

[ccd1]

Yep, I'm guessing vB 2.2.7 will be vB Final

[Kier]

Originally posted by baragon0
Yep, I'm guessing vB 2.2.7 will be vB Final We certainly hope that 2.2.7 will be the final release of vB2, but then again, when the next version of PHP or MySQL or Apache comes out, there might be an incompatability (or something like that) that would force us to release a 2.2.8... but of course that is beyond our control.

[Xenon]

somewhere i've read 2.2.6 would be the last vb2, and it's good to hear it isn't

good to hear there will come out 227 :)

[Chruser]

Things would actually be made easier for some people if all of the updates would be released separately, step-by-step. Even if it would be 200 whole different things to do in files, it would still have time for some people.

[okrogius]

Originally posted by Chruser
Things would actually be made easier for some people if all of the updates would be released separately, step-by-step. Even if it would be 200 whole different things to do in files, it would still have time for some people.

I'm pretty sure most vb users don't alter their source code, therefore easier for them to upgrade. If you do altert it running a comparison program on new version and old version should be no problem.

[Marshalus]

I just upgraded from 2.2.5 to 2.2.6 last night (I know, I'm lazy ;) ) and using "Beyond Compare 2" the whole process took around 45 minutes to an hour, and that's because I've got a LOT of hacks. For someone with a minimal hacked board, it shouldn't take more than 30 minutes to do the work if you're efficent about it.

I personally have no problem with upgrading. It keeps things running smooth, and when you run a site with as many hits as mine, running smooth is the #1 thing on your mind.

[Chen]

Beyond Compare 2? Sounds good, I'm using Araxis but I'll have to check out this new version. :)