We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 26903
    • 1,336 Posts
    This is an auto-generated topic for Provisioner 1.5-beta by shamblett.

    Brief Description:

    This package allows provisioning of a Revolution site from either a remote Revolution or Evolution site. Resources, elements, files, packages and user information can be viewed/imported. Please read the user guide in /assets/components/provisioner/docs for exact usage details. Also remember to install the revogateway connectors pack into any Evolution site you wish to use. Updated for Revolution RC3 usage, specifically the addition of the site identifier API key.
      Use MODx, or the cat gets it!
      • 14883 ☆ A M B ☆
      • 450 Posts
      First download!

      I hadn’t used Provisioner previously; I just set up a 2nd Revo instance (RC-3), upgraded my existing instance to RC-3, and installed Provisioner 1.4. When it didn’t immediately work (granted, I hadn’t read the manual and wasn’t doing it right), I went back to the site and saw that 1.5 had been released. Installed that, read TFM, and attempted to connect from my new instance to my old instance.

      On the Administration tab, I’ve specified account, password, URL and identifier all correctly to use the admin account on my other Revo instance. Type is set to Revo, and Action to Login. But when I click on ’Go’, nothing is happening. The ’please wait’ message flashes by super fast, but no connection seems to be made, and nothing is showing up from the other site.

      Ideas?
        • 26903
        • 1,336 Posts
        Ok, what happens if you then logout? The lack of any feedback on the login would seem to say the login works Ok but then you should see resources when you go to the resource tab and refresh the tree, or any other tab for that matter and do the same. Now the package is on extra’s I’ll do an install into one of my test sites and check it out, there’s always the possibility my local installs are working but I’ve borked the transport package somehow, stay tuned.
          Use MODx, or the cat gets it!
          • 26903
          • 1,336 Posts
          Just another thought, do you have the php curl package installed, this is a separately installable package on my servers, could you check your setup.
            Use MODx, or the cat gets it!
            • 26903
            • 1,336 Posts
            Ok, I’ve just installed 1.5-beta into a brand new RC3 install through the package manager and it seems to work OK with both Revo and Evo sites, so It’s looking at the mo like a local prob your having.
              Use MODx, or the cat gets it!
              • 14883 ☆ A M B ☆
              • 450 Posts
              I do have CURL installed; I’m running xampp1.7.2 as my LAMP bundle, and it is installed by default.

              I have Provisioner 1.5 installed on the old/acceptance site too, and it does work from that side - I can connect to the new/production modx installation and see everything that is there. But it won’t work the other way around.

              Here’s something weird. When I try run Provisioner from "old" to "new" (which works), I see the following in my server logs (the logs for the site being connected to):
              POST /connectors/security/login.php HTTP/1.1" 200 80


              But when I try to run it from "new" to "old" (which is failing), I see this (again, in the logs for the site being connected to):
              POST /assets/components/provisioner/connector.php HTTP/1.1" 200 -
              POST /assets/components/provisioner/connector.php?action=administration/status HTTP/1.1" 200 -
              


              The connection that isn’t working is requesting completely different files than the one that is working. I have the correct URL specified in each one (pointing to the /connectors directory). This seems really strange...
                • 26903
                • 1,336 Posts
                The first one is Provisioner’s login request to your remote server, this is OK. The second one is a bit odd, this is Provisioner refreshing its admin page status which it does on page refresh, this is a local event as you can see its talking to Provisioners own connectors, this should only be a local server event, not a remote one, its as though Provisioner thinks it is actually installed on the remote server, not the local one, odd indeed.
                  Use MODx, or the cat gets it!
                  • 14915
                  • 43 Posts
                  Hello,

                  thanks for making such a useful tool. I’d like to experiment with importing data from an Evolution instance, but I don’t know where to download the relevant evogateway package mentioned in the user guide.

                  Also, I’d like to read data from a site that’s password protected using Apache’s basic authentication. I read in this thread that this package uses curl, so could you please point me to the file / class / function that I have to modify to make it work?

                  Thanks in advance!

                  Regards,

                  - Jay
                    • 33337
                    • 3,975 Posts
                    The revogateway is for Evolution smiley
                      Zaigham R - MODX Professional | Skype | Email | Twitter

                      Digging the interwebs for #MODX gems and bringing it to you. modx.link
                      • 33337
                      • 3,975 Posts
                      I tried to use it on Revo PL to connect to MODx 0963 and MODx 1.0.2, but it doesnt load anything except users.

                      Any ideas? smiley
                        Zaigham R - MODX Professional | Skype | Email | Twitter

                        Digging the interwebs for #MODX gems and bringing it to you. modx.link