I think the upgrade path seems harder than it actually is to be honest.
Don't get me wrong, it can be a bit nerve racking, I have had 2 seperate upgrading 'spurts', where like you I left it too long before I got round to catching up with the updates.
It's easy to say you'll keep on top of it, just doesn't seems as easy to do it...
Anyway First things first Backup your Database AND if you can, take a complete backup of the site, that way you can just upload a working copy if things go the wrong way.
Then do all of the many upgrades you are going to have to do.
Module upgrades? I only started with XOOPS 2.0.7.3, but have never had to update all of my modules as part of the update process.
Only problem that I was told of when I first updated (a while back now) was that you don't need to upload any updates for newbb if you have the newer version)
This is what I would do:
Backup DB
Backup Site
Download the update
Check the update to see what modules are to be updated (e.g Newbb)
IF YOU HAVE A NEWER VERSION OF NEWBB THEN IGNOR THE UPDATES FOR THIS MODULE (as I was told to do so before...)
Upload the updated files to your web server (excluding newbb)
Then go to admin
> Modules Admin
Update the System
If your update included updates for modules (e.g. xoopsmembers) then I update these modules as well, not sure if its nec. but do it anyway, if there were no updates for X module I ignor it.
At this point its up to you, you could test your site, and maybe take another update of the DB, but to be honest I wouldn't bother, but that might just be me.
I just get straight on to the next update.
Your upgrade path is nice and long
Backup DatabaseBackup site if you canXoops 2.0.6 > 2.0.72.0.7 > 2.0.9.22.0.9.2 > 2.0.102.0.10 > 2.0.12a2.0.12a > 2.0.132.0.13 > 2.0.13.12.0.13.1 > 2.0.13.2The next update seems like a bit of a jump to me, I have done this update on 2 sites with no real issues, well nothing too serious anyway. However XOOPS 2.0.13.2 is secure and stable (as far as I know...) so it might be worth testing the site and taking another backup at this point, I didn't but if you have a nice fast internet connection or the site is hosted on your server, I would recommend it.UPDATE 2.0.13.1 or 2.0.13.2 to 2.2.3Quote:
Enable PHP debug
Go to your administration area => system module => preferences => general settings and enable PHP debug
Run pre-upgrade script
After uploading all files in the patch archive, access http://www.example.com/xoopsupdate.php, replacing http://www.example.com with your site's URL. This will show error messages and no real content, but don't worry.
Reload the page
Press the submit button to update the system
2.0.13.1 (or later) > 2.2.3 FINAL Done.
Areas that might cause problems:
Sometimes the blocks seem to have their viewing or listing options changed.
Mainly custom blocks in my case, but for some reason after the update to 2.2.3, my blocks from the front page vanished on 2 sites, easy enough to correct, just go to admin > Blocks > List all blocks > and make sure that the blocks are set to visible in the top page or whereever.
Also for some reason, some of the blocks may reset to the standard template, for example My recent Links from the mylinks module defaulted back to displaying 10 links rather than 5 and other strange little things like that, but again, all easy to rectify.
After the final update to 2.2.3 I had issues with my theme on 2 sites, but these were not hard to fix.
Good luck.
Dave