We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 20407
    • 82 Posts
    Trying out MODX Cloud, and the documentation on importing via Vapor could be beefed up a bit. I had numerous errors over SSH (memory, disk space) but eventually it appears to have worked over HTTP. The documentation doesn't mention, for instance, that Vapor doesn't create the zip; you have to do this part manually (unless I'm missing something). Posting this in case it helps someone.
    • You are definitely missing something. It should work exactly as written. If you're getting memory and disk space errors using SSH then you have bigger problems.
        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
        • 20407
        • 82 Posts
        Quote from: sottwell at Mar 21, 2014, 01:23 AM
        You are definitely missing something. It should work exactly as written. If you're getting memory and disk space errors using SSH then you have bigger problems.
        Well I increased the memory and disk space, but still got errors with SSH but not with HTTP. So you're saying Vapor claims to be successful when it actually isn't? MODX Cloud also claimed to be successful in importing and upgrading the site, and yet I'm just getting a blank page when I launch it, so it must not have actually been successful either. For something that's supposed to be easier, Cloud has been anything but so far.
        • When using the HTTP method, are you logged in to the original site's Manager? If you aren't logged in, then several items won't be added to the package. It's also possible that with HTTP it's just stopping if memory or disk space runs out. Your server's error logs may have more information.

          I've used Vapor both to and from Cloud installations as well as other hosting including localhost. I've never had any trouble, other than one site that was too big to work with the HTTP method, and it worked fine with SSH.
            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
            • 20407
            • 82 Posts
            Update:
            Finally got this working. What I learned and what should be documented:

            • Vapor requires enough disk space to create a directory of all your files PLUS a zipped copy of that directory, so probably a minimum of 2.5 x the amount of space your site uses.
            • Vapor has an option to exclude certain files and directories. See https://github.com/modxcms/vapor . Unfortunately, you can't exclude subdirectories of 'assets', which in my case is where the bloat was. Also, it's not clear how to specify the paths of what you want to exclude (what is the path relative to?).
            • According to my hosting provider, a cpanel setting called 'fork bomb protection' was causing Vapor to fail (PHP out of memory errors and/or maybe 'could not copy' errors in the logs). Vapor finally worked after this was turned off. They said 'fork bomb protection' is not needed if you have 'cagefs' installed.
            • Vapor may report success with HTTP even though it didn't actually complete. If it doesn't create a zip file in the 'packages' directory, it didn't work. When it finally did work for me over SSH, the success message was 'Completed extracting package: [filename]. Vapor execution completed without exception in x [seconds].'
            • MODX Cloud may claim to be successful importing a package even though it isn't.