I have a slightly unusual site migration process that is not obviously covered in the documentation.

My site is staged with the intended hosting provider but under a temporary URL. I am proposing to leave the site exactly where it is (same IP address) but point the correct URL at it by:

1. Changing the 'Main Domain' in the site cPanel (GoDaddy)
2. Changing the nameservers at the domain hosting provider (Fasthosts)

I'm pretty sure all the php file links will be fine but there are four possible concerns:

1. The database access - this appears to be pointing to localhost so should be OK?....

2. Standard images posted into an image field or a richtext field

3. Images in nicedit field that have been uploaded to the database in an 'image' field then the URL copied and used in the nicedit image dialog (not sure why the nicedit field does not have a 'browse server' option but thats another topic).

4. Files that have been handled as per #3, uploaded via a 'file' field then the URL grabbed and used in a link field in nicedit dialog.

Any icebergs here?

Thanks!

[KK]

Database shouldn't be a problem.
Images and files uploaded through editable regions of type 'image' and 'file' shouldn't be any problem either.

Images directly embedded within richtext or nicedit are actually complete links (unlike 'image'/'file' regions mentioned above). So, they'll continue pointing to the original domain. So these would be a problem.

One way to rectify such images is to first take a database dump (using Couch utility or phpMyAdmin). Then using a text editor find/replace en masse the original domain to the new domain. Re-apply the modified dump.

My suggestion would be to first do the domain switch. See what breaks and then rectify it.

Thanks KK,
That is manageable. I have started editing the HTML to convert all of the embedded links to relative paths

/couch/uploads/image/residential/image.jpg

and they are working fine so that seems to be a way of minimizing the risk offline.