Hi!
So I have lots of websites powered by the following, Xoops, Impress, Xoops Cube.,
I love them all for different reasons. (mainly based on what the site is).
I've come to a point where two (not all) of mysites I'd like to migrate back to the latest xoops, I'm so impressed with some of the recent development and themes also appear to be getting momentum again.


Now- both of these are sites that were originally 2.18 before moving to icms so many years ago...

So Just checking, is there an easy(ier) way to do this? lol -

I'm familiar with SQL and not afraid to dig into DB (in this case its basic content imports) - but was wondering if there is a module or if someone had already written about doing it. - Unfortunately I couldn't find any such post in the forum. Which is surprising. ;)

Thanks

I am happy to hear that you like the recent developments in XOOPS and are considering converting your sites back to XOOPS.

At the moment there is no script for importing ICMS Website. I don't think, it would be too difficult, but it would all depend on the modules you're using.

I actually was looking at this recently. I don't have my notes available, but I'll try and cover what I remember.

As Mamba indicates, a large portion is dependent on the modules. A lot of them will have at least a common ancestor, so it is usually not hard to find a workable replacement. Even for things unique to ?????, some creativity with SQL can extract content in a form usable in another module.

The user conversion is a potential issue depending on the size (and temperament) of your user base. The password hashing has several salts, and is quite different from anything in any Xoops, current or future. The cleanest way to do it is basically mass invalidation, requiring every active user to go through the password reset mechanism.

The system I was examining was in the 1.2.x line, the 1.3+ variants introduced additional differences, but are still similar.

I would encourage you to keep us posted on your efforts. There is a certain level of animosity that you might run into occasionally regarding mentioning our competing "cousin." Personally, I have held "a best tool for the job at the time" attitude over the years, and so I've used a lot of things. But now, if XOOPS isn't the best tool for the job, that means I have work to do

If there are any major obstacles to moving back to XOOPS, I'd like to know what they are, and if practical, make them less of an obstacle.

Thanks -
Ok they are two very different sites...
The main thing I think one of them uses the xoops method for storing password...
that one iI think is the one Ill start with.

Ill be curious to see how much I can import and I'll basically do anew xoops install locally and import data and see what happens. Will share what I learn.

Thanks!