We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 32025
    • 305 Posts
    Yes I know my curent installation is old! My client wants to udpate his platform to the latest revo version (2.2.10). I looked in my admin control panel and I see: rev 6066 (1.0.2 in admin)

    First this is version 1.0.2 correct? I also have a v1.3.8a downloaded in this clients folder so I wanted to make sure I did not update as of yet (to version 1.3.8). The reason why I ask the obvious is I wanted to make sure I did not upgrade to v1.3.8a but the database might not have udpated via the control panel. There was a program a few years back that I updated but the admin panel did not reflect. I am not sure if it was this program that's why I ask.

    There are zero modules installed not even the contact form so that should help. What conerns me about this upgrade is this site has lots of static pages. If I have to backup, copy, and paste each page it's going to add considerable time to the project.

    Also, this older installation is in the root folder so I really don't know what I am going to do if I run into major problems. Meaning I would like the old site to stay live while I build the new site, but don't know how to do this side by side since my old installation is already in the root.

    Any tips for udpating? I did not see anything in the documentation that goes all the way back to my version. I am assuming I will run into major problems, but I would like some advice so I know what to look for.
      Making the web a better place on site at a time! Dayton Web Design: http://www.dayton-web-design.com/
      • 30912
      • 463 Posts
      Do you mean MODx 1.0.2? as that is an Evolution codebase and not Revolution?

      If its Evo > Revo then you have a bit of work ahead of you, there is a script somewhere that helps with the conversion but i have never used it (and cant recall the name at the moment - Sorry)
        • 44375
        • 92 Posts
        I posted some details about this process on this thread

        https://forums.modx.com/thread/87544/snippet-to-assist-upgrade-from-evo-ditto-to-revo-getresources

        Note my upgrade was considerably more complex than yours sounds.
          • 44375
          • 92 Posts
          The Extra that will help you is Provisioner, but do everything on a test/development copy of the site first. There are a few gotchas which I describe in the thread above, so ensure IDs are ported between versions so you don't have to update [[~ID]] links in your articles, chunks, etc.
            • 32025
            • 305 Posts
            This site was my very first time using MODx, so I might have installed Evo on this first site but I am unsure. I know I have always used Revo since, but this will not help me here. I really don't know if this is Evo or Revo but I do have the original downloaded files. How can I tell? Is there a file in one of the folders that will label this as Evo or Revo?

            I do know its version 1.0.2 because it's not only labeled in my admin control panel, but its my original downloaded folder is names as such.

              Making the web a better place on site at a time! Dayton Web Design: http://www.dayton-web-design.com/
              • 22840
              • 1,572 Posts
              Revo started at 2.0.0 so there has never been a revo version 1.0.2, it's safe to say your on Evolution with a 1.0.2 version number
                • 30912
                • 463 Posts
                if its 1.0.2 then its Evolution, the latest version of it is 1.0.12.

                If you wanted to continue using Evolution for this site you could also try clipperCMS (http://www.clippercms.com/) its a fork from the Evolution codebase as MOdx will eventually stop support Evolution and will update over the top of Evo.

                If you do want to move it to revolution you have two options.

                1) try and use provisioner to upgrade it
                2) manually rebuild the site switching out the corresponding tokens in the templates and also switching the required snippet calls eg getResources to replace Ditto, Formit to replace eForm.
                  • 32025
                  • 305 Posts
                  Everyone thank you. Since the site is very simple without any additional modules, I think I might build the new one from scratch. I have to completely redesign the template anyway so the only migration would be all my pages. I suppose I will just copy and paste backups to my computer.

                  Any suggestions building the new site next to this one in the root? Maybe I should build the new one under a sub-folder till its completely ready. Then download and backup the entire site in this test folder, then delete the old site and all files on the server, last upload the site built in the folder to the root and import database. Finally, change the config file. Would this be the suggested way to go?

                  I obviously want to get off the Evo platform so I am guessing I should start over with fresh install so there are no problems.
                    Making the web a better place on site at a time! Dayton Web Design: http://www.dayton-web-design.com/
                    • 30912
                    • 463 Posts
                    installing MODx to a subfolder is fine, thats how I generally do it when doing that level of migration.

                    if your developing on the server the site is on (i.e installed to a subfolder on the physical host) you can just move them around on the FTP once its complete and rerun the setup file to change the paths in the config

                    Good luck smiley