We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 29091
    • 88 Posts
    Hi.

    I saw the security alert and upgraded to Rev 2.3. It took all night to upload the files, and then when I got home from work the next day I could finally go to the setup dir and make the upgrade, which went off without a hitch. But I am welcomed with the MODx 2.3.1 bug fix upgrade. So now I have to do it all again.

    What complicates that issue is that I have so many sites to upgrade. Don't get me wrong, I like having the upgrades. But, could we please not rush a distribution to market if I have to upgrade it all over again the very next day? All that work I did yesterday is now pointless because there is no difference archive between 2.3 and 2.3.1 and I have to upload the whole thing all over again, which will take all night and prevent me from doing anything online. I have lots of work to do, and almost all of it requires me to use online resources or at least be online.

    Please consider a difference archive of the changed files from the very last version. That's all I request.
      Doug Peters, Symbiotic Design. (605) 251-8973
      http://W3DN.com | http://www.DomainHostmaster.com
      • 3749
      • 24,544 Posts
      Normally, I think you'd see at least a description of the patch and a link to the commit at GitHub, but in this case so many files had to be changed that it will be much faster to do an upgrade install than to modify them all.

      You can see the changes here if you want to wade through them: https://github.com/modxcms/revolution/commits/develop

      After many years of using MODX, I can tell you that this is a very rare event.

      All that said, I definitely feel your pain.
        Did I help you? Buy me a beer
        Get my Book: MODX:The Official Guide
        MODX info for everyone: http://bobsguides.com/modx.html
        My MODX Extras
        Bob's Guides is now hosted at A2 MODX Hosting
        • 9995
        • 1,613 Posts
        There is a easier way to upgrade without uploading all files.
        There is 1 .php file you need to upload and you can upgrade with 1 click.
        (I haven't used it yet thow.)

        Can't find the link, maybe someone can post it?

          Evolution user, I like the back-end speed and simplicity smiley
          • 28042 ☆ A M B ☆
          • 24,524 Posts
          https://github.com/evolution-cms/installer

          Needs to be updated to fetch the latest versions.

          The URL for the latest is http://modx.com/download/direct/modx-2.3.1-pl.zip, so you'd need to edit lines 40 and 41 to reflect that.
          	'name' => 'MODX Revolution 2.3.1-pl Standard Traditional (23.07.2014)',
          'link' => 'http://modx.com/download/direct/modx-2.3.1-pl.zip',
          

          You can also modify to add links to the advance and SDK versions and for 2.2.15 as well.
            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
            • 9995
            • 1,613 Posts
            when I change it and run the installer for 2.3.1-pl I get:

            503 Error
            Page not found
            The page you requested was not found.

            running in a subdomain
              Evolution user, I like the back-end speed and simplicity smiley
              • 28042 ☆ A M B ☆
              • 24,524 Posts
              You have to put the install.php file in the directory where you want MODX to be installed. When it's run, it romoves itself, so you have to upload it again if you want to run it again. If it can't find the setup file, more than likely there was a problem downloading the MODX .zip file.

              I've modified the original to address Revolution installation only, and updated it to install the three versions of the latest Revo - as of this post, 2.2.15 and 2.3.1.

              https://github.com/sottwell/installer [ed. note: sottwell last edited this post 12 years, 2 months ago.]
                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
                • 18373 ☆ A M B ☆
                • 3,141 Posts
                There's a diffview here, perhaps with some git-fu that can be made into an archive of just changes https://github.com/modxcms/revolution/compare/v2.3.0-pl...v2.3.1-pl
                  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.
                  • 3749
                  • 24,544 Posts
                  The problem is that the site to be updated would have to be under Git to use the difference and have a proper .gitignore to keep the local files from being deleted.

                  Given those conditions, I think this might do it:

                  git diff v2.3.0-pl v2.3.1-pl > patch.diff


                  Then, after getting the git.diff file on the site, and assuming that 'git status' shows it up to date:

                  git apply --check patch.diff


                  Assuming that check shows no problems:

                  git apply --ignore-space-change --ignore-whitespace patch.diff


                  Does the version at GitHub still require a 'build" step before setup? That might keep this process from working.

                    Did I help you? Buy me a beer
                    Get my Book: MODX:The Official Guide
                    MODX info for everyone: http://bobsguides.com/modx.html
                    My MODX Extras
                    Bob's Guides is now hosted at A2 MODX Hosting