2.2.4?!

[ja5es]

What the -- I haven't even had time to upgrade to 2.2.3!

[Faruk]

Heh, I haven't even upgraded from 221 to 222, let alone 223, totally forgetting 224 even!




oh, and the reason is: too many hacks installed, don't feel like re-applying 15-16 hacks all over again, that took me about 2 months to do all-in-all... :/

[HenryG2]

Well, I heard it was either this or 2.2.3c


Maybe they'll have MS SQL support.

[Floris]

no it is true

Yeah,

you can now upgrade to 2.2.4

After 2.2.1 we now went to 2.2.2 last week, yesterday to 2.2.3 and few hours later 2.2.3b and this morning to 2.2.3c and just now to 2.2.4

My forum is getting so freshed up

[JamesUS]

I upgraded from 2.2.0 -> 2.2.3 about a week ago (weekend before last) - but I haven't done any of the a/b/c/.4 releases yet so I'll have to do those today

[Mark Hewitt]

[Floris]

Originally posted by JamesUS
I upgraded from 2.2.0 -> 2.2.3 about a week ago (weekend before last) - but I haven't done any of the a/b/c/.4 releases yet so I'll have to do those today

haha

If you run any version of 2.2.3 you can just do a full upgrade to 2.2.4 by running upgrade17.php from admin dir

You are a mod, you know this right?

[Joe Gronlund]

im all upgraded

[DirectPixel]

...this is like those Jaws movies, lol...first you hear the spooky music to create suspense, then, when you least expect it, the shark appears.

In this case, you get those spooky upgrades, then, when you least expect it, vB3.0 comes out.

[JamesUS]

Originally posted by xiphoid


haha

If you run any version of 2.2.3 you can just do a full upgrade to 2.2.4 by running upgrade17.php from admin dir

You are a mod, you know this right?

Yup I did know that It's not the running of the upgrade scripts that I'm bothered about...my main concern is the files which will need to be rehacked again!

[JWB]

Unless a big security problem comes out Im sticking with 2.2.1! The current security problem only affects those smarties who upgraded to 2.2.2 (which had to upgrade to 2.2.3).. So I figured I would just wait for 3 before I rehack everything..

[Freddie Bingham]

Originally posted by JWB
Unless a big security problem comes out Im sticking with 2.2.1! The current security problem only affects those smarties who upgraded to 2.2.2 (which had to upgrade to 2.2.3).. So I figured I would just wait for 3 before I rehack everything..

2.2.1 does have a security problem.

[DirectPixel]

hehehehe...always best to have new version, not just because of security fixes. Also because of bug fixes, and typo correction.

[klisis]

you know, John mentioned of security hole , I don't know how serious it is though, and released 2.23 and 4. John released 2.24 on weekend, I think the security hole was quite serious.

[JWB]

Oh no!! I thought that only 2.2.3 had it.... Garbage.. I guess Ill have to start working on it..