We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
  • "Buggy" is an inaccurate adjective in this case: there are a lot of steps when migrating any site, and it's possible to miss something, but user error is not the same as a bug.

    I don't see "mysql5" anywhere -- which page were you referring to?

    I wrote a helper utility named test_config.php @ https://github.com/craftsmancoding/modx_utils -- I would recommend using it if you're having any trouble. The more you practice moving sites the better you get at it. All the things with permissions and plugin settings apply no matter which system you use. The only thing that's a bit of a head trip for me with MODX is the fact that MODX has 3 extra configuration files, but that's a bit of a necessary evil given that its paths/urls can be customized.
    • It's pretty easy to use the Vapor scripts to move a site.

      1. Make a new installation in the new location with the same version as your original. It's easiest if you create a Manager user with the same username and password as the original site.

      2. Run the Vapor scripts on the old installation, according to the instructions.

      3. Put the resulting transport.zip file in your new installation's core/packages directory.

      4. Install the package from Package Manager as you would any other package. You will lose the "new" login and will need to log in again with your "old" username and password.
        Studying MODX in the desert - http://sottwell.com
        Tips and Tricks from the MODX Forums and Slack Channels - http://modxcookbook.com
        Join the Slack Community - http://modx.org