Why Does My MODx site occasionally stop working?

If the site isn't too big (lots of large images or video files) you can use Vapor to make a package of your site, then install it like any other local package.

As far as the archive directory OS X leaves you with, it's easy in CPanel to just move each of the top-level directories (assets, core, etc) and files (index.php, etc) using CPanel's file manager. I do it all the time.

It's best to then run setup again in upgrade mode, possibly even in advanced upgrade mode so it will correct the database details as well as the paths and URLs in the configuration files.

Hi Susan. Thank you for responding. My interpretation of merging means that for example webRoot/modxInstallDirectory/components/ where "components" needs to be merged with webRoot/components and there is no way to do that with the File Manager. The File Manager only allows me to overwrite the directory.

In the past on another server, I used SSH to accomplish the merge, but SSH is not an option on this server. Enabling SSH on this server will force a move to a newer cPanel environment and essentially delete all the files for my site. I spoke with support about it and they said that I would have to re-upload my site at the new server location.

I think at think point, I may just have to accept there is no way for me to upgrade MODx on the current server, unless support can do a merge for me. Maybe they have more access and freedom to work with the files on the server. The newer cPanel environment should be more flexible, I hope, but I feel as though I need to upgrade MODx before I attempt to move it. If all else fails, I can just rebuild the whole site from scratch on a newer server and forget about trying to do an upgrade.

I give up!

Just got off the phone with goDaddy. No way to merge the directories. So... they are going to migrating all the contents over to cPanel for me. If the site still works once it arrives at cPanel I will be shocked.

You will need to check the three config.core.php files and make sure they point to the correct path to your new /core/ directory, as well as the /core/config/config.inc.php file. That file has the database connection information, as well as a number of pre-configured paths and URLs that will need to be edited. Either you can edit them manually (search-and-replace is handy here) or upload the same version's setup directory and run setup in advanced upgrade mode. It will rewrite all of the necessary config files for you.

Then make sure that your browser cache and cookies are cleared for the domain, and also manually delete everything in the /core/cache/ directory. In all the years I've worked with MODX, I've never had a site that didn't transfer without too much trouble.

I'm bracing for impact. Thanks for the tips. Was also reading related information yesterday.