We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 47690
    • 22 Posts
    Hello,

    I just installed UpgradeMODX to help me with a migration of an existing site (RHEL7). The installation of UpgradeMODX went fine, and its widget appears on my dashboard, offering the option to upgrade from 2.3.2 to 2.5. I clicked the "Upgrade MODX" button. It logged me out and redirected to http://72.32.247.2/upgrade.php, which just goes to my site's home page.

    I've checked the permissions on both core/components/upgrademodx... and core/packages/upgrademodx... and ensured they're 777 the whole way down.

    The error log shows nothing.

    I'm not sure where else to look. I would so love to get to use this amazing add-on for an upgrade I was dreading! Any suggestions or advice would be hugely appreciated.

    Thanks so much in advance!

    This question has been answered by BobRay. See the first response.

    • discuss.answer
      • 3749
      • 24,544 Posts
      Check the upgrade.php file in the root of the site. If it's not there, make sure that directory is writeable. If it is there, check its permissions. Also, check your Error Log. The fact that you got sent to the upgrade.php page is a good sign. It means that the script was working up to a point.

      On many sites, 777 will not work for a PHP script. It needs to be 755 for folders and 644 for files.

      I'd strongly advise upgrading to 2.4.0 before going to 2.5.0.
        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
        • 47690
        • 22 Posts
        Thank you, Bob. There is no upgrade.php in the root of the site. However, I noticed that the root directory's owner wasn't correct. I changed that, and now upgrade.php appears and runs when I click the button. YAY!!!

        It doesn't offer me an option to migrate to 2.4.0, though. It offers 2.4.1, 2.4.2, 2.4.3, 2.4.4, and 2.5.0. Would migration to 2.4.1 do the trick before 2.5.0, or do I need to do a manual upgrade to 2.4.0 first?

        Thank you *SO SO MUCH* for your help, and for this really fantastic tool. We're behind in our upgrades due to issues when migrating manually, so you've really hit a major pain point with this one. I'll be much happier clicking a button and keeping things up to date, once I'm past this larger catch-up activity.
          • 47690
          • 22 Posts
          P.S. I did try changing the &versionsToShow property to 10, to see if it would show me earlier versions, but no joy; it still shows the same 5 versions. I cleared cache, flushed all sessions, restarted httpd; no joy.
            • 47690
            • 22 Posts
            Well, after all that, it must have been some caching issue after all. I manually edited update.php to include 2.4.0 as an option, and the upgrade to 2.4.0 went just fine. After that, UpgradeMODX showed me 10 versions automatically, per my versionsToShow property. I upgraded to 2.5.0, and, except for one small new error turning up in the log (which someone else had gotten answered previously), it looks like our site is now current and happy.

            I can't believe how simple it was, once I got past this one issue. @BobRay, you are awesome. I'm going off to make a donation to support this fantastic utility. Thank you!
              • 3749
              • 24,544 Posts
              I'm glad you got it sorted.

              Thanks for reporting back, and for the kind words. smiley
                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