We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
MODX Community Forums Archive

Provisioner Compatibility?

    • 36786 ☆ A M B ☆
    • 209 Posts
    Ben Morrison Reply #1, 13 years, 9 months ago
    It says on the documentation Provisioner won't work on the most up to date version of modx. Is this still the case? If that is still the case, are their alternatives? Thanks!
      Ben Morrison
      Hacking templates to pieces since 2003
      • 33337
      • 3,975 Posts
      Zaigham (aka zi) Reply #2, 13 years, 9 months ago
      I've tried latest version of Provisioner on latest MODX release a couple weeks ago, it didn't work. It logs in but does not load any remote data. So yes, it is useless for now.

      But I still encourage you to use it on your installation, only take a couple of minutes to know if it works.

      No other alternatives as far I am aware.
        Zaigham R - MODX Professional | Skype | Email | Twitter

        Digging the interwebs for #MODX gems and bringing it to you. modx.link
        • 18373 ☆ A M B ☆
        • 3,141 Posts
        Mark Hamstra Reply #3, 13 years, 9 months ago
        The site you are importing to can be any version; the site you are importing from should be on 2.1.3 or below. Last time I checked anyway.
          Mark Hamstra • Developer spending his days working on Premium Extras and a MODX Site Dashboard with the ability to remotely upgrade MODX and extras to make the MODX world a little better.

          Tweet me @mark_hamstra, check my infrequent blog at markhamstra.com, my slightly more frequent ramblings at MODX.today or see code at Github.
          • 28042 ☆ A M B ☆
          • 24,524 Posts
          sottwell Reply #4, 13 years, 9 months ago
          I haven't tried it myself, but the Vapor site packaging utility is said (although I haven't heard any official statement on this) to work on any site. As I understand it, first upload the Vapor scripts to site A and run it to package the site, according to the first set of instruction in the page linked below. Then download the package, upload it to site B's core/packages directory and "install" it using the package manager like any other local package.

          https://modxcloud.com/userguide/how-tos/import-sites-with-vapor.html
            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
            • 36786 ☆ A M B ☆
            • 209 Posts
            Ben Morrison Reply #5, 13 years, 9 months ago
            Dang, oh well thanks guys!
              Ben Morrison
              Hacking templates to pieces since 2003
              • 28000 ☆ A M B ☆
              • 397 Posts
              sonicpunk Reply #6, 13 years, 6 months ago
              Is this still the case? I have a client that would like to have a testing environment for his website. They are not interested in moving to cloud. Has anyone another alternative for this use-case, whereby the client wants a testing version and an easy way to integrate new changes into the live version?
                Benjamin Davis: American web designer living in Munich, Germany and a MODX Ambassador. I am also co-founder of SEDA.digital, a MODX Agency.