Subscribe: RSS
  • So I just saw that there's a critical update to modx - and although my site isn't visited by anyone yet, I'd still like to upgrade. But how?
    The official guide is very strict with it's "do not overwrite!" rules, but what do I do when my ftp client (winscp) doesn't appear to have a merge function? A quick search brought up years old material (from people just as frustrated) and most of the advice I could glean from it was to either use cPanel or SSH. As far as I can tell my webhost doesn't have cPanel (just a file manager that doesn't to much) and I don't even know where to start with using SSH.
    So, do any of you know of a (free) ftp client that can merge directories? I'm on windows 10 btw.

    (Also no, changing webhost is not an option (one, because it's already paid for by someone else and two, because they have really great support in my native language).)

    PS. Is modx ever getting an internal upgrade function (so that we don't have to play around with doing it manually)? If I had known it would be this difficult to do, I honestly don't know if I'd have given modx a chance.

    This question has been answered by multiple community members. See the first response.

    • discuss.answer
      UpgradeMODX 1.5.5-pl is available and can be installed via the manager. https://modx.com/extras/package/upgrademodx

      I don't know what version of MODX you are running, but it is always best to upgrade on version at a time. ie:
      2.4.4 to 2.5.0
      2.5.0 to 2.6.0
      2.6.0 to 2.6.5

      UpgradeMODX will handle all the file merging/copying for you.

      Ideally you would make a full backup of your site and database before upgrading. Hopefully the hosting you are on allows you to do that?

      To simply download files via FTP you could use Cyberduck which has a Windows version. https://cyberduck.io/ I don't know if it will merge, but as I say you won't need to using the upgrade extra.
        If I help you out on these forums I would be very grateful if you would consider rating me on Trustpilot: https://uk.trustpilot.com/review/andytough.com

        email: andy@andytough.com | website: https://andytough.com
      • Oh my gods, why doesn't it say that anywhere?! I'll try that right away - thank you.

        [Edit: it worked flawlessly! (Well, okay, there was an issue with making a confic file writeable, but that may have been because I'd already tried messing around with updating it manually - anyway, it's all good now).] [ed. note: wyrdling last edited this post 1 week ago.]
        • Glad you got it working.
            If I help you out on these forums I would be very grateful if you would consider rating me on Trustpilot: https://uk.trustpilot.com/review/andytough.com

            email: andy@andytough.com | website: https://andytough.com
          • Additional question: the guide I'm following says to make sure the config.inc.php file is only readable after installation - and that you'll get an error message on the dashboard in the manager if it's still writeable - but it still is (because I haven't changed it back yet), yet there is no warning.
            So, should I change the permissions or just leave it? And if so, is it just that one file (in core/config/) or others too (I'm kinda confused by the config.core.php file in the root e.g. - what permissions should that have (I'm asking because I might have mistaken the two and I can't remember if I changed the permissions of it or not when I made the first install)?
            • discuss.answer
              The file that has to be set to restrictive permissions (400) is /core/config/config.inc.php

              The root level config.core.php can be set to the same permissions as other files -probably 644

              Having said that, to make you site more secure it is worth following these guidelines:

              https://docs.modx.com/revolution/2.x/administering-your-site/security/hardening-modx-revolution
                If I help you out on these forums I would be very grateful if you would consider rating me on Trustpilot: https://uk.trustpilot.com/review/andytough.com

                email: andy@andytough.com | website: https://andytough.com
              • Thank you!
                • @Andy, I think it's only important to upgrade to the x.x.0 versions between your version and the current version. That's where any significant changes take place.

                  @Erica, I always move the core directory above the web root and rename it so it's not accessible at all via the web. Here's a blog post on how to make the files in that moved and renamed core show in the file tree: https://bobsguides.com/blog.html/2018/02/17/show-moved-modx-core-in-file-tree/

                    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
                  • Thanks Bob. Just to clarify, you mean it would be OK to go from 2.5.2 to 2.6.5 without bothering with the 2.6.0 step?
                      If I help you out on these forums I would be very grateful if you would consider rating me on Trustpilot: https://uk.trustpilot.com/review/andytough.com

                      email: andy@andytough.com | website: https://andytough.com
                    • No, just the opposite. Sorry I misread your post. I meant that you wouldn't need to do 2.5.3, 2.5.4, etc. -- just 2.6.0 and then 2.6.5.

                      I was confused by this: "it is always best to upgrade one version at a time." Maybe it should say, "It's best not to skip the major versions (the ones ending in .0)."

                        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