Thanks for all the answer. :)

System: 2.1 --> XOOPS 2.5.6 (or soon 2.5.7) ** I am running xoops 2.5.6 and I have updated the system module but it still saying 2.1. (But in the bottom right corner it says "Powerd by Xoops 2.5.6)
MyAlbum: 3.07 --> I'll do soon some updates ** I wait for that and see if it fix the problem.
Wordpress ME: 0.33 --> That's our friends form Japan, so I don't know. ** We only have a few articles so I will maybe start using something else. If I remember right we got lots of spame with this module.
Memberlis: 1 --> I don't know it ** My bad. Should be Memberlist.
More info about "Memberlist":
Version : 1
Skapare : Kazumi Ono
( http://www.myweb.ne.jp/ )
Credits : The XOOPS Project
Licens : GPL see LICENSE
Shows a list of registered users
From 2011 so I guess it's better to use your version.

Web links: 1.3 --> Version 3.11
Addresses: 1.5 --> I was looking at version 1.80
Liaise; 1.27 -->you should use xForms
PD-Downloads: 1.2 --> you should use WF-Downloads
Mastop Publish: 1.1 - you should use Publisher ** Is it easy to export to publisher?
SmartObject Framework: 1 --> OK
SmartAssociate: 1.12 --> I don't know it ** On the icon it says "SmartPartner".
News: 1.56 --> switch to Publisher ** Is it easy to export to publisher?
Pical: 0.91 --> I am not sure I know it ** Calendar module
More info about "Pical":
Version : 0.91
Skapare : GIJ=CHECKMATE
PEAK Corp.(http://www.peak.ne.jp/)
Credits : PEAK Corp.
Licens : GPL see LICENSE

Forum: 3.08 --> 4.33 from Irmtfan
Happy Linux Framwork: 0.6 --> 1.80
Xoops DB Backup: 3.3 --> OK

Inactive: ** All inactive will be removed from the server
Marquee: 1.31 --> 2.49
Xoops Stats: 0.6 --> Statistics 0.7
P'tites annonces: 1.4 --> I'm not sure I know it ** When we used it we used it like a buy and sell module
Content: 0.5 --> Publisher
MRBS: 1.41 --> OK
Wordpress ME: 0.33
Membership: 2.3 --> I just released 2.4 under the name XM-MemberStats

What would be the best way to continue?
1) Update the module on the production site.
2) Install a new homepage with the new modules and then export the old data to the new site (If it's possible?) Then remove the old homepage and add the new one to the production address.

Best Regads
Ahlis

Best bet is to try doing your upgrades on a test site locally on your local PC if at all possible. It will be much faster for you in the long run and you will be able to try different things.

For a variety of reasons you should not work on your production server to do such an upgrade.

If you MUST work on your production server you COULD make a sub directory on your production server, duplicate your database and do all of the work there if you so desired too if you are not sure... Not suggested but still better than actively working on the active production server. If you use a sub directory on your active server and get everything working it is simple to move it back.

Thanks. Will try to do a local homepage where I could do all the testing. I guess I would ask more question later on when starting with this. :)

Step 1: Take a backup from the production site then add it to the local server and get it running there. (Both CMS and databas)

Step 2: Installing the new modules and updating the modules that could be updated. Remove unused modules.

Step 3: Try to export the data to the new modules.

Step 4: Take a new backup from the production site.

Step 5: Add the local site to the production server.

Step 6: Add new data to the homepage that was missing when I first downloaded the databas.

Could this be the way to go?

Best Regards
Ahlis

That sounds like a good plan.

Just make sure you remember to delete the cache files and clear the session data when you move it back and forth.

If you are using windows and install something like WAMP you can try using different versions of PHP which can be helpful when moving from an old system to a new one especially if the old modules have an export option.

The only files you should have to adjust when moving things around are the mainfiles.php and the xoops_data/data/secure.php files.

It is suggested to upgrade to 2.5.6 and when 2.5.7 final is available to upgrade to it. Going from 2.5.6 to 2.5.7 should be painless and require very little if any modifications to anything.

Rodney

Thanks for the tips.

I will use windows and maybe wamp or xampp.

Best Regards
Ahlis

Quote:
Take WAMP Server - it's the best

Okey. Then i would use vamp. :)