We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 54653
    • 10 Posts
    I have a MODX 2.5.7 installation and would like to use UpgradeMODX to upgrade it to 2.6.5.
    Many posts point to the need to first upgrade to the main point release (in my case 2.6.0) and then from there to the latest one (i.e., 2.6.5).
    However, UpgradeMODX shows 2.6.1 as the earliest upgrade I can perform (see attachment).

    Would it be OK to upgrade from 2.5.7 to 2.6.1 and then from there to 2.6.7?
    Otherwise, is there any way to force UpgradeMODX to list 2.6.0?

    Thanks,

    Massimo
      • 38783
      • 571 Posts
      If you go to Snippets / UpgradeMODXWidget / Properties you should be able to unlock the default properties by clicking on the 'Default Properties Locked' button and changing the 'versionsToShow' to a higher number.

      This will get the job done, but bear in mind that UpgradeMODXWidget will revert to its default settings if it (not MODX) is ever upgraded. In an ideal world you would do this with a modified property set that will not get overwritten. See here for more info on property sets"
      https://docs.modx.com/revolution/2.x/making-sites-with-modx/customizing-content/properties-and-property-sets
        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: [email protected] | website: https://andytough.com
        • 54653
        • 10 Posts
        Andy,

        thanks for the quick reply and pointing me to the right direction.
        I changed VersionToShow to 7, but UpgradeMODX is still listing version 2.6.1 to 2.6.5.
        I cleared cache, went as high as 10 (see attachment), but no change in the list.

        I am thinking the issue may be the versionlist file in {core}\cache\upgrademodx directory.
        It shows exactly the same 5 versions I see.

        Maybe I need to add an entry there for 2.6.0?

        Thanks again

        Massimo
          • 3749
          • 24,544 Posts
          Try manually deleting the files in the core/cache directory.

          FYI, the new version of UGM, which should be available in the next few days, will automatically show enough versions to include your current version regardless of the versionsToShow setting. It will also automatically select the next x.x.0 version above the one you have.
            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
            • 54653
            • 10 Posts
            Thanks Bob. A few minutes after sending this post, a new versionlist file with many more version listed showed up in cache (maybe because I flushed the cache, removed the cache folder, reinstalled UpgardeMODX, etc.). Anyway, after all of that (not sure what fixed it...), I was able to upgrade to 2.6.0 and, after a quick check, to 2.6.5!

            Things looked good. UpgradeMODX shows I am at 2.6.5, everything works (other than the security and news feeds showing a spinning sign with the word 'Loading' which, after I flushed MODX cache, removed the cache folder and changed the feeds' URLs from http to https turned out to be a browser caching issue since both feeds showed up immediately in another browser.

            BUT... (I know, there is always a 'but'!) I did not notice some errors in core/logs directory (please let me know if you think I should be worried):

            These were the errors in the 2.6.5 installation log file (possibly directory permission issues?):

            2018-10-17 19:01:02] (ERROR @ /project/hyperdev/modx-2.5.7-pl/core/xpdo/transport/xpdovehicle.class.php : 181) Could not copy /project/hyperdev/modx-2.5.7-pl/core/packages/core/modContext/457ca7a0b0eaefc2ca1c7c6e01be469a/0/ to /project/hyperdev/modx-2.5.7-pl/index.php
            [2018-10-17 19:01:02] (ERROR @ /project/hyperdev/modx-2.5.7-pl/core/xpdo/transport/xpdovehicle.class.php : 181) Could not copy /project/hyperdev/modx-2.5.7-pl/core/packages/core/modContext/457ca7a0b0eaefc2ca1c7c6e01be469a/1/ to /project/hyperdev/modx-2.5.7-pl/ht.access
            [2018-10-17 19:01:02] (ERROR @ /project/hyperdev/modx-2.5.7-pl/core/xpdo/transport/xpdovehicle.class.php : 181) Could not copy /project/hyperdev/modx-2.5.7-pl/core/packages/core/modContext/55899c07a0be09d324666a6a7964aa95/0/ to /project/hyperdev/modx-2.5.7-pl/manager/assets
            [2018-10-17 19:01:02] (ERROR @ /project/hyperdev/modx-2.5.7-pl/core/xpdo/transport/xpdovehicle.class.php : 181) Could not copy /project/hyperdev/modx-2.5.7-pl/core/packages/core/modContext/55899c07a0be09d324666a6a7964aa95/1/ to /project/hyperdev/modx-2.5.7-pl/manager/controllers
            [2018-10-17 19:01:02] (ERROR @ /project/hyperdev/modx-2.5.7-pl/core/xpdo/transport/xpdovehicle.class.php : 181) Could not copy /project/hyperdev/modx-2.5.7-pl/core/packages/core/modContext/55899c07a0be09d324666a6a7964aa95/2/ to /project/hyperdev/modx-2.5.7-pl/manager/templates
            [2018-10-17 19:01:02] (ERROR @ /project/hyperdev/modx-2.5.7-pl/core/xpdo/transport/xpdovehicle.class.php : 181) Could not copy /project/hyperdev/modx-2.5.7-pl/core/packages/core/modContext/55899c07a0be09d324666a6a7964aa95/3/ to /project/hyperdev/modx-2.5.7-pl/manager/min
            [2018-10-17 19:01:02] (ERROR @ /project/hyperdev/modx-2.5.7-pl/core/xpdo/transport/xpdovehicle.class.php : 181) Could not copy /project/hyperdev/modx-2.5.7-pl/core/packages/core/modContext/55899c07a0be09d324666a6a7964aa95/4/ to /project/hyperdev/modx-2.5.7-pl/manager/ht.access
            [2018-10-17 19:01:02] (ERROR @ /project/hyperdev/modx-2.5.7-pl/core/xpdo/transport/xpdovehicle.class.php : 181) Could not copy /project/hyperdev/modx-2.5.7-pl/core/packages/core/modContext/55899c07a0be09d324666a6a7964aa95/5/ to /project/hyperdev/modx-2.5.7-pl/manager/index.php
            [2018-10-17 19:01:02] (ERROR @ /project/hyperdev/modx-2.5.7-pl/core/xpdo/transport/xpdofilevehicle.class.php : 103) Could not install files from /project/hyperdev/modx-2.5.7-pl/core/packages/core/xPDOFileVehicle/ffa5502778b3fb87d28d02f45d927841/ to /project/hyperdev/modx-2.5.7-pl/connectors/
            [2018-10-17 19:01:02] (ERROR @ /project/hyperdev/modx-2.5.7-pl/core/xpdo/transport/xpdofilevehicle.class.php : 103) Could not install files from /project/hyperdev/modx-2.5.7-pl/core/packages/core/xPDOFileVehicle/1149241767cb39815df8fc2114a9936f/ to /project/hyperdev/modx-2.5.7-pl/connectors/
            [2018-10-17 19:01:02] (ERROR @ /project/hyperdev/modx-2.5.7-pl/core/xpdo/transport/xpdofilevehicle.class.php : 103) Could not install files from /project/hyperdev/modx-2.5.7-pl/core/packages/core/xPDOFileVehicle/abadc8773bbd03d54796490a67534a63/ to /project/hyperdev/modx-2.5.7-pl/connectors/
            [2018-10-17 19:01:02] (ERROR @ /project/hyperdev/modx-2.5.7-pl/core/xpdo/transport/xpdofilevehicle.class.php : 103) Could not install files from /project/hyperdev/modx-2.5.7-pl/core/packages/core/xPDOFileVehicle/229a573898f3733982f59f406bed73e1/ to /project/hyperdev/modx-2.5.7-pl/connectors/
            


            and these the ones in the error.log file (maybe a consequence of the above install errors?):

            [2018-10-18 09:43:06] (INFO @ /project/hyperdev/modx-2.5.7-pl/core/model/modx/processors/system/config_check.inc.php : 65) [configcheck] core has not been moved outside web root!
            [2018-10-18 09:43:06] (DEBUG @ /project/hyperdev/modx-2.5.7-pl/core/model/modx/processors/system/config_check.inc.php : 120) [configcheck] access check http return code: 500
            [2018-10-18 09:43:06] (DEBUG @ /project/hyperdev/modx-2.5.7-pl/core/model/modx/processors/system/config_check.inc.php : 127) [configcheck] Core folder is not accessible by web this time.
            [2018-10-18 09:43:06] (DEBUG @ /project/hyperdev/modx-2.5.7-pl/core/model/modx/modlexicon.class.php : 417) Language string not found: "Download"
            [2018-10-18 09:43:06] (DEBUG @ /project/hyperdev/modx-2.5.7-pl/core/model/modx/modlexicon.class.php : 417) Language string not found: "Download"
            [2018-10-18 09:43:06] (DEBUG @ /project/hyperdev/modx-2.5.7-pl/core/model/modx/modlexicon.class.php : 417) Language string not found: "Download"
            [2018-10-18 09:43:06] (DEBUG @ /project/hyperdev/modx-2.5.7-pl/core/model/modx/modlexicon.class.php : 417) Language string not found: "Download"
            [2018-10-18 09:43:06] (DEBUG @ /project/hyperdev/modx-2.5.7-pl/core/model/modx/modlexicon.class.php : 417) Language string not found: "Download"
            [2018-10-18 09:43:06] (DEBUG @ /project/hyperdev/modx-2.5.7-pl/core/model/modx/modlexicon.class.php : 417) Language string not found: "Form"
            [2018-10-18 09:43:06] (DEBUG @ /project/hyperdev/modx-2.5.7-pl/core/model/modx/modlexicon.class.php : 417) Language string not found: "Form"
            [2018-10-18 09:43:06] (DEBUG @ /project/hyperdev/modx-2.5.7-pl/core/model/modx/modlexicon.class.php : 417) Language string not found: "Form"
            [2018-10-18 09:43:06] (DEBUG @ /project/hyperdev/modx-2.5.7-pl/core/model/modx/modlexicon.class.php : 417) Language string not found: "GitHub"
            [2018-10-18 09:43:06] (DEBUG @ /project/hyperdev/modx-2.5.7-pl/core/model/modx/modlexicon.class.php : 417) Language string not found: "GitHub"
            [2018-10-18 09:43:06] (DEBUG @ /project/hyperdev/modx-2.5.7-pl/core/model/modx/modlexicon.class.php : 417) Language string not found: "GitHub"
            [2018-10-18 09:43:06] (DEBUG @ /project/hyperdev/modx-2.5.7-pl/core/model/modx/modlexicon.class.php : 417) Language string not found: "Security"
            [2018-10-18 09:43:06] (DEBUG @ /project/hyperdev/modx-2.5.7-pl/core/model/modx/modlexicon.class.php : 417) Language string not found: "Widget"
            [2018-10-18 09:43:06] (DEBUG @ /project/hyperdev/modx-2.5.7-pl/core/model/modx/modlexicon.class.php : 417) Language string not found: "Widget"
            [2018-10-18 09:43:06] (DEBUG @ /project/hyperdev/modx-2.5.7-pl/core/model/modx/modlexicon.class.php : 417) Language string not found: "Widget"
            [2018-10-18 09:43:06] (DEBUG @ /project/hyperdev/modx-2.5.7-pl/core/model/modx/modlexicon.class.php : 417) Language string not found: "Widget"
            [2018-10-18 09:43:06] (DEBUG @ /project/hyperdev/modx-2.5.7-pl/core/model/modx/modlexicon.class.php : 417) Language string not found: "Widget"
            [2018-10-18 13:54:45] (INFO @ /project/hyperdev/modx-2.5.7-pl/core/model/modx/modsessionhandler.class.php : 164) There was an error retrieving or creating session id: ab9ufr6paqnfoo4jacfo95bgd0
            [2018-10-18 14:11:01] (INFO @ /project/hyperdev/modx-2.5.7-pl/core/model/modx/modsessionhandler.class.php : 164) There was an error retrieving or creating session id: 77o38sj6b01fk9rsqee7gor4r6
            


            Thanks in advance,
            Massimo [ed. note: massimo last edited this post 5 years, 5 months ago.]
              • 3749
              • 24,544 Posts
              I don't know what that means, but it does look like the setup log errors indicate file permission problems on those files (or the manager directory is not writable, or setup doesn't know that the Manager directory has been renamed).

              I have not seen those errors at Bob's Guides when updating with UGM, nor has anyone else reported anything similar -- yet.

              The Error Log errors look like missing lex strings from UpgradeMODX. They are the area values for the Widget Snippet's properties.

              Try pasting this code at the end of the core/components/upgrade/modx/lexicon/en/properties.inc.php file:

              $_lang['Download'] = 'Download'; 
              $_lang['Form'] = 'Form'; 
              $_lang['GitHub'] = 'GitHub'; 
              $_lang['Security'] = 'Security'; 
              $_lang['Widget'] = 'Widget'; 


              Let me know if that makes them go away.

              BTW, those lexicon errors should only show up if you have debug mode on in the MODX System Settings, or you have PHP set with error reporting and show errors.
                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
                • 54653
                • 10 Posts
                Bob,

                those strings in properties.inc.php file were definitely missing. I added them and hopefully those warnings will disappear.
                The permissions on the file are
                -rw-rwSr-- 
                (basically 644) the file is owned by apache (the user that web server runs as) and the group permissions include developers, me and the apache accounts), therefore the setup tool and the plugin installation feature should have had no problem writing to it.

                As far as debug level, it is not set to value in MODX's system settings. Should it be explicitly set to 'off'?

                Thanks,

                Massimo
                  • 3749
                  • 24,544 Posts
                  Here's what I'm guessing happened with the lexicon errors. The code that throws the error was added in a MODX version (maybe 2.6.0). People complained, so it was modified in a later version to only throw the errors in debug mode. Your version was probably between those two events. If I'm right, the errors would have gone away on their own once you installed 2.6.5.

                  I don't know what's going on with the copy error. It happened during setup, after UGM was finished running, so I don't think it has anything to do with UGM. I could be wrong.
                    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