2
You need to ask your new hosts for the 'server-path' to the new site, then edit 'mainfile.php' and use that path as 'xoops_root_path', e.g.
define('XOOPS_ROOT_PATH', '/var/www/vhosts/example.com/httpdocs');
Change also (if needed) the HTTP address, e.g.
define('XOOPS_URL', 'http://www.example.com');
If the new host has their MySQL databases hosted on a different server than their websites, replace:
define('XOOPS_DB_HOST', 'localhost');
with:
define('XOOPS_DB_HOST', '192.168.123.456');
using the IP address of their DB server.
And of course ensure MySQL database name, username and passwords are updated to the new ones.
The BIG problem with XOOPS is that it uses absolute paths for images in the image manager, so if the site is on a new domain you may need to open the exported SQL file in a text editor before importing and search for:
[img align=left]http://www.oldsite.com/img472dea365fad8.jpg[/img ]
replacing it with:
[img align=left]http://www.example.com/img472dea365fad8.jpg[/img ]
HTH.
A thread is for life. Not just for Christmas.