Trying to document myself before doing this upgrade I've found some contradictory posts in the forums that still keep me unsure how to proceed. In essence, options are:

A.- Going the full way, step by step through all these:

2.2.2 to 2.2.3a upgrade
2.2.3a to 2.2.4 upgrade
2.2.5 full version (no upgrade patch is available)
2.2.5 security patch
2.2.5 to 2.2.6 upgrade

B.- Skip some of those steps: probably the first two, since 2.2.5 full will overwrite everything previous; and most likely the security patch, which should be covered well enough by 2.2.6 upgrade. Hence, only two steps would remain:

Overwrite 2.2.2 with 2.2.5 full
2.2.5 to 2.2.6 upgrade

C.- Forget all about the gradual approach and just apply 2.2.6 full version directly on top of 2.2.2

From what is said in the UPDATE.html instructions that come with the 2.2.6 full package, I gather that option C.- should be OK. Those instructions state "Upgrade From Previous 2.2.x", so I understand that applies to 2.2.2 as well.

However, I've read somewhere that if you do it like that things may not turn up well, and that option B.- might be safer. This doesn't make much sense to me, but certainly I'd love to hear some advice from you before I start messing up my site.

BTW, the 2.2.6 UPDATE.html literally instructs to "Upload the 2.2.x files, overwriting existing files", but I assume before that chmod 444 should be applied in order to protect mainfile.php, right? If so, that would better be noted in the instructions, don't you think?.

Thanks for reading me and please have a nice day.
MD

Sniff... :(

200 hits already and yet not a single comment to my post...

Nobody has ever gone through this upgrade before?

I'd like to get some more information on this topic as well, because I'm running 2.2.4 and would like to upgrade. I'm a bit fuzzy on the 2.2.4 -> 2.2.5 upgrade. Is there really no upgrade script for that?

I'm looking for the best way to get from 2.2.4 up to the latest version.

Any help is much appreciated!

- b -

Hello, I am a 2.2 fun.
I remember that I did upgraded step by step (at publication time) and never faced any problem.
Usually you have to read the readme.txt file for upgrading patch. On the full version step I did just overwrite the files and updated system module.

You're talking about the full version step from 2.2.4 to 2.2.5, right? What about the other modules (other than the system module)? When you uploaded and overwrote the files, do you keep your other module directories in there and then re-install them from the module admin panel?

- b -

Other module, you mean pm and profile?
Update them too.

In my opinion:
:: php file modified in new version -- >> need overwrite files;

:: if any MySQL changes or mainfile.php changes for the new version -- >> usualy is provided an upgrade php script that add MySQL tables, alter tables ... an so on, so upload files overwrite, run upgrade script, update modules (system, pm or profile ifany changes on them) that should manage other changes;

:: if there are templates changes in new version, than after overwrite file update modules is needed (from package - system, pm, profile - I mean that modules that are actually modified);



Now, lets see the changelog -- please read changelog.txt

So, I think you should just overwrite the files ( except mainfile.php ), update system, pm and profile modules, and than delete files from templates_c folder (except index.html).

In the XOOPS 2.3.0 Alpha 2 release annoucement they say:

Quote:
So may be the best upgrading strategy for us 2.2.2 users is just wait until that happens and go straight to 2.3 and don't mess with any middle steps.