It was the import that failed. I could see everything in the Evo site from within the Revo site (very cool by the way).
The bottom of my browser displayed a status that looked like this:
When the failed import was done, that displayed "Done" instead of the manager URL. Just another clue.
Also, does it matter that the domains that I’m using are all on our dedicated server?
I’m actually going to set up another subdomain, do a fresh install of Revo, installed Revogateway into another Evo site (I have about 15 to convert and starting to wonder if the 6 of mine should be set up as contexts in Revo, but alas I’m just too conservative).
It worked on a fresh Revo site. It failed on the site that had the Demo site "modxss" installed.
What I did different from the failed import:
1) Installed Revo (installed Revogateway on the Evo site, but that’s not different)
2) Installed Provisioner via Revo’s Package Management
3) Logged into the Evo site via Provisioner
4) Imported the site with Snippets and Chunks selected.
4a) Still need to SFTP the template files over. Just so you know, I don’t expect that as a feature of Provisioner.
My question then is: why did Provisioner fail to import into the default web context that was populated? The warning says that the import is going to overwrite anything and everything selected to import.
Nice work! Thank you for your efforts on this. I’ve now gotta hold my own hand and try creating a new context and see if Provisioner will import a different Evo site into that.