I hit a problem due to missing the site files and the FTP access I have been given won't allow me to retrieve them unless I move everything one by one which would take some time. Really not a fan of this hosting provider.
Vapor does look like it will work if I can find where the "Vault" is in Revolution.
or some import documentation for vapor in MODX revolution
-
☆ A M B ☆
- 191 Posts
Yes, Vapor was created to package up a site for easy import into MODX Cloud. Personally I don't have any experience with it, but it seems like you might be able to use it to do the packaging up part, then just download and unarchive the file it creates, and skip the import into MODX Cloud part.
Some of the instructions—the latter steps—are specific to MODX Cloud, like anything dealing with the Vault.
And they denied my access request with another terrible excuse.
I have the Vapor package but I am not sure how to move this into my new hosting area for MODX Revolution, any suggestions on how best to approach this?
Martyn
Should be able to place the vapor package in the core/packages folder of your new site then go to package manager, click the drop down on the download extras button and select search locally for packages, then install your vapor package.
jpdevries
-
☆ A M B ☆
- 24,524 Posts
Just put the Vapor's directory in the root of the original site. If you have to, use the File Manager to upload all of the files - a pain, but if you don't even have FTP access you don't have much choice.
Once you can run Vapor on the site, get the package that it creates from the core/packages/ directory. Put the package zip file in the core/packages/ directory of the new site, then install it from local like any other package. You'll find that you need to log in once or twice during the process, since it's overwriting the new database.
Oh, one other important thing... make sure you're logged in as a Manager user when running the Vapor script. I'm not sure exactly what permissions you need, if your user isn't a "sudo" administrator user.
Vapor does sound interesting, even to me as a non-Cloud person, is it documented anywhere? And is it open source (officially)?
-
☆ A M B ☆
- 24,524 Posts
Usage outside of importing to the Cloud is not officially documented. The point is, Vapor creates a <sitename>.package.zip file that can be imported into any existing site. So making a new installation and putting that package into its core/packages/ directory makes it possible to simply install it from the Package Manager like any other package.
Going to be working on this tonight, when it works I'll put some documentation together for someone to make available if anyone else has the same issue
A big thank you to Sottwell and everyone else who has been in touch, I'll be back in touch if I have any further issues or once its worked.
