Any reason not to just FTP files for server migration?

Reading the instructions about moving servers, it says to package up the files. I'm a UNIX command moron. I'd rather just FTP them being careful to grab hidden files (I use Filezilla). Is there any reason to *not* do that?

Files can become corrupt during transfer so a lot of people suggest against it, that said though I've never had a problem with it ( that I can remember ).

Quote from: paulp at Jul 15, 2014, 03:48 PM

Files can become corrupt during transfer so a lot of people suggest against it, that said though I've never had a problem with it ( that I can remember ).

Thanks. I grew up with DOS so I keep typing in DOS commands and get errors. Easier to just Filezilla.

I've never had a problem ftping files. I do recall having an issue once trying to unzip a MODX package via cPanel.

Over the years, I've seen *many* reports from people with missing or corrupted files when transferring them individually with FTP (often using Filezilla).

It may work, but can also fail down the road when you access some part of the Manager you've never used before. Theoretically, it could also corrupt the database when you hit a corrupted file.

This is the method I use, and it's a lot faster than FTP: http://bobsguides.com/modx-upgrade-faq.html (it's about upgrading, but the file transfer part would work for migration).

If you have shell access, there are also some shell scripts around for doing it even faster.

I used to have frequent problems with Evo, usually when transferring the tinymce plugin files. I had a problem once with Revo, then stopped using FTP to transfer all the files.

Now I use the install.php script, which works fine, except for advanced installations where things have been moved or renamed.

But updating an advanced installation is complicated in any case, since the core directory has to be moved and any other folders that were renamed have to be manually updated anyway.
http://www.sepiariver.ca/blog/modx-web/upgrading-modx-advanced-installs

But at least they are all unzipped and in place in their default locations, so it isn't difficult to get the installation ready to run update.

I'm working on an advanced installation/update version that will ask you where you want the core directory on a new installation, moving it there before forwarding you to Setup. On an update, it will scan the config.core.php file to find where the new core files should go and what the name of the config.inc.php file should be. It will then scan the config.inc.php file to find out what the names of the assets, controllers and manager folders are, and move the new files into place if they are customized.