Questions about How to Move My MODx Site to a new server.

I'm reviewing the information found at http://rtfm.modx.com/revolution/2.x/administering-your-site/moving-your-site-to-a-new-server, and have a novice question.

My current build is 2.2.8. Should I perform an update to 2.2.14 first, and then follow the steps?

I saw mention of running the setup script again and not sure how to approach. Once I've transferred all of my files, do I upload a new MODx install, unpack on server and then drag the setup folder out into the root where my site will be? Thus, my previous question, because it seems as though a 2.2.14 setup script could not be run on an older build of MODx.

Any tips, or pitfalls to watch out for greatly appreciated.

I would upgrade the current site and do a lot of testing to make sure everything works OK. Don't remove the setup/ directory in that process.

Then you can zip up the whole site, move the .zip file to the new location, unzip it in cPanel, and run setup again there (after moving the content of the database).

One tip you shouldn't actually need: When you run setup at the new site, don't proceed if the "upgrade install" checkbox is not checked. (IOW, don't do a "new" install -- that will wipe out the stuff you moved.)

Thanks Bob: Sounds like a plan.

However, I am once again back at this whole "merge directories" quagmire. I've just been reviewing your guide, but I was under the impression that went files get upacked on my mac, that's where permission issues occur. Or it in only when I ftp unpacked directories and files?

Here is what I do: http://bobsguides.com/modx-upgrade-faq.html.

It's about upgrading, but the part about getting the files in place should be the same for you.

I strongly recommend against using FTP to transfer the files individually. It very often results in missing or corrupted files.

I would not upload individual files. I guess I am just unclear as to how the merge occurs. My MODx site is all located in the root. They are not in a directory in the root.

So if I unpack the MODx install on my mac, then open the folder, select each item, and then compress those items, the Mac makes an Archive.zip. I can change the name to something else at that point. So when I uploade that zip, and then use the host File Manager to unpack it, are you saying that will automatically allow the merge of directories? I'll re read your guide to see if I have missed something.

I guess I can try it and see what happens.

Earlier today I backed up the database, and then also using the File Manager selected and zipped all of the site files and downloaded both to my computer. So at least I have a backup stored both other server and on my mac.

See my post in the other thread.

Actually. I just ran a test on my own mac. When I unzip the archive I made, the contents are then still stored within a folder called: Archive. Thus, I am still faced with the issue of moving the new MODx files out to the root and merging them with the existing site directories.

I know I know. I actually just recently signed up with a Reseller Account at Skytoaster. But — and there's always a but — I don't have the liberty of moving this site over there. My client paid for 5 years of hosting. And... he's a friend. I basically get free pizza for helping him. At this point, I'm not sure I can eat the amount of pizza necessary to cover my time:)

Quote from: BobRay at Jul 10, 2014, 06:40 PM

See my post in the other thread.

It's always interesting to work with clients who pay 2+ years in advance, as in almost every case the problem is related to the hosting environment. You might try asking GoDaddy if they can do a prorated refund to account credit, in short cash in a few years for renewing domain names early.

Don't forget there are other costs beyond the hosting. I would look at what hosting his site would cost you in billable hours, and if you spend more than those billable hours trying to fix stuff related to the hosting environment move the site. It's been cheaper on several occasions to move someone to our hosting, instead of fixing the problem with their current hosting provider.

I agree 100% Patrick.