Thanks for the reply.
I did find a 2.3.3b upgrade package.
The upgrade instructions are in the release notes file.
Not sure that I can use this package for the 2.3.3 install I have so will leave it for now. Probably will not bother upgrading as nothing is too clear.

This post did not start too well as I spent 15 minutes trying to find out where to login. Tried to post ,(thinking I would get a login page, no way jose) but was returned to the forum.
The only login mod I could find was at the bottom right of the Home Page.

The reason I am posting is I cannot find an upgrade from 2.3.3 to 2.4.1.

I cannot find an upgrade guide in documentation or a Search.

Curious to know if I am supposed to install a new version as the download page only has the full installation, or whether I can simply overwrite the files with the new version.

I have rewritten various files in the existing installation and have done quite a lot with the templates.

Reading a few posts on the forum I see various upgrading issues but still cannot find a definitive guide.

Is there one?

Thanks in Advance.

I would like to know if moving them to another directory in XOOPS installation root, i.e. domain root/xoops installation directory (root)/folder for data & lib/xoops_data & xoops_lib

The reason I ask is that I still get a warning that these folders should be moved even though I have a new directory and also have renamed the xoops_data & lib directories.

The installation was working as above, however when I tried to move the folders into domain root below the XOOPS installation directory and altered mainfile.php I got white screened and could not access admin.
The site was up though.

Why should I have got a warning when I have done the aforesaid renaming and creating a new directory?

Tried to reverse the process now my whole installation is messed up.

Cannot get to admin.

I posted too soon. Went into XOOPS today to finally to put the site live and realised that my URL's were a mess.
Spent another 4 hours looking for URL's.
Finally found them, I think.

Files that needed editing:
MYsql database.(4 instances)
root/mainfile.php
root/xoops_data/caches/xoops_cache/xoops_adminmenu_XoopsGuiDefault.php (150 instances)

/root/xoops_data/caches/smarty_cache/system-rational-default+.html (2 instances)

Note the path above is the path before you move your lib & data directories.

The above instances were on a new installation and migration.

Lets hope I have got everything!

Whilst configuring modules appears easy the migration process is a real mare.

Getting white Screened on Admin now as I got a warning that xoops_data & xoops_lib folders should be moved even though they are in a new directory and also have renamed the xoops_data & lib directories.

Because of this I moved them to another directory in domain root, whereas domain root/xoops installation directory (root)/folder for data & lib/xoops_data & xoops_lib was where they were before.

The installation was working as above, however when I tried to move the folders into domain root below the XOOPS installation directory and altered mainfile.php I got white screened and could not access admin.
The site was up though.

I cannot understand the warning when I have done the aforesaid renaming and creating a new directory.

So now the installation is a mess again.

Never had this much trouble configuring a CMS before so now revert back to being unconverted.

Thanks sailjapan, I figured that in the end. Been working with files so had a one track mind on the culex Post.
Anyway all is sorted now see:
https://xoops.org/modules/newbb/viewtopic.php?topic_id=69112&post_id=314761#forumpost314761

Thanks for all the posts here.

Well this time no problems.

As tcnet pointed out in the a Post I made here:
https://xoops.org/modules/newbb/viewtopic.php?topic_id=68989&post_id=314137#forumpost314137

Initially I tried with an older version installed by Installatron.

Using the latest release I installed on one Server, configured and installed Modules and Themes, edited the theme I will be using to suit the site on the different server, followed the Steps on this page by mboyden.

I am not used to editing the sql file for migrations, (normally do any alterations to file paths etc when the CMS is migrated through admin backend, menu, global etc). However using notepad++ the Search mechanism made it simple to edit and replace any possible causes for error.

This was a fresh install I migrated with very little added data. Total time spent on migration including Server time for backups and dumping onto new Server, 45 minutes.

Easy when you find the right Guide.

Thanks to all who posted for the help and advice.

Xoops has a new convert, this is probably the simplest CMS I have used, that is why the migration issue was important to me.

It's the best walk through I think I have seen to migrate a site.

Can I ask why XOOPS is not storing url's as relative to the database automatically.

I am still a little confused as to why the database would be storing information contained within the script.
For example if the absolute and root paths are defined within the script there is no need to add anything to the database. Sure menu items and external url's will enter a database, but the base configuration has no need to be anywhere but the config file, in this case mainfile.php.
There are rare times when there may be two config files.
Normally one in root and one in admin, if there is to be two, (often found in e-commerce cms).

I appreciate your guide and I followed the link, did not get that on a search, but like most searches one does need to know the right search term to get the answer.

I will look into the database and try again.

I appreciate the responses I get here.
But there is no root/admin folder.
There is a root/modules/profile/admin folder but no settings.php.
I am still a little confused as to why a php based cms should require more than 1 file to connect to a database, (security comes to mind here) and why the database would be storing information contained within the script.
For example if the absolute and root paths are defined within the script there is no need to add anything to the database. Sure menu items and external url's will enter a database, but the base configuration has no need to be anywhere but the config file, in this case mainfile.php.
There are rare times when there may be two config files.
Normally one in root and one in admin, if there is to be two, (often found in e-commerce cms).
As far as this post goes though 'tcnet' pointed out my original error. Do not install an old version.
The new version I installed was a breeze.
Went well this time although previous versions did not for me.
My issue now is solely with migration, so rather than duplicate postings, I posted here:
https://xoops.org/modules/newbb/viewtopic.php?topic_id=69112&post_id=314761#forumpost314761

This posting was done originally attempting to migrate a 2.2.2a version.

I thank you 'culex' for taking the time to post though.

All Server environments are different.
But the requirements for XOOPS are met on all the Servers I have tried to migrate the installation too.
The Servers I am using have had all the above listed CMS's moved to and from no problems at all.
MySQL databases are all slightly different in some way and if there is a problem a query will normally arise.
I do this on a regular basis as I always use three hosts for my website domains and if there are problems I just change my DNS.
I have 17 domains and each of those sites has three servers or hosts and on each site maybe 2 or three CMS's.
I did put XOOPS onto dedicated domains with it's own database as sometimes scripts do not like to be either in a shared database or even on a domain with another script.
The reason I am trying XOOPS is to see if it migrates easily as my clients use the domain registrar I use as it can swich DNS in under 3 hours. I rarely wait longer than an hour.
The migration process is also important because rather than backing up to the computer we back up to the replicated sites. Thereby keeping 3 copies of a website on completely different Servers or Hosts.

Thanks for the reply.
I did clear the all caches after initial errors to no avail. I did not think that the database would fill up with references on a new installation relating to paths.
That is what a config file is for isn't it?
It would be easier in that case to make a new install, but that would mean of course that the old database is not importable without what seems to be too much editing prior to migration.
So my original statement appears correct.
Xoops does not migrate.
The reason I think this is an important issue is that with the proliferation of hosting services it is important to be able to move an installation immediately a host causes a problem.
Uptime is King.
The best thing to do of course is to have the website on two or more Servers and back up to the spare servers. I have all my sites on three servers.
If there is a problem I change the DNS and have limited downtime. My DNS is usually switched in under an hour.
This would not be possible with an XOOPS installation as the backups would be too time consuming.