Subscribe: RSS
  • Hi,

    Spotted an oddity. Security Feed caught my eye indicating 2.6.5 release. But my 2.6.4 sites using UpgradeMODx indicate "MODX is up to date". Then looked at an older 2.6.1 site and UpgradeMODx correctly states 2.6.5 as an upgrade option.

    As UpgradeMODx on the dashboard (at least on my default setup) is more prominent than the security feed then many MODexers may miss the need to upgrade. And of course they'll have to do it the manual way.

    Bug in UpgradeMODx perhaps.

    Note both my sites (2.6.4 and 2.6.1) are on the same server/setup. So can't be a server issue.
    PHP Version 7.0.30

    Parthian

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

    • I had the same issue. I was able to trick it into seeing 2.6.5 as an available upgrade by changing two things.

      In the System Settings I changed settings_version from 2.6.4 to 2.6.3

      In the file /core/docs/version.inc.php I changed

      $v['minor_version']= '4'; // Current minor version.

      to
      $v['minor_version']= '3'; // Current minor version.


      Then I was able to use UpgradeMODx to upgrade to 2.6.5. After the upgrade both the entries that I had changed to incorrect version numbers correctly read 2.6.5.

      I have raised the issue on Github: https://github.com/BobRay/UpgradeMODX/issues/43

        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
      • discuss.answer
        The default "time to check" in UGM is 1 week from the last check (though you can change that). The versionlist file is not updated until that happens.

        One way that definitely works to force it to take another look is to manually delete the core/cache/upgrademodx/versionlist file.

        I think you can also set the lastCheck property of the UpgradeMODXWidget snippet to a much older date and clear the cache.
          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
        • Quote from: BobRay at Jul 14, 2018, 05:54 AM

          One way that definitely works to force it to take another look is to manually delete the core/cache/upgrademodx/versionlist file.

          I just deleted the contents of that file. Popped back to the Dashboard. And 30 seconds later I'm on 2.6.5

          Hopefully UpgradeMODx will be built into modx3.0 - didn't discover it for some reason until a few months ago. Saves so much tiresome linux stuff AND crucially makes MODx viable for non experts to manage.

          If Wordpress does it MODx should do it. In terms of making maintenance and adding editor users etc nice and easy instead of an IT assault course.

          Thanks Bob. And hopefully you'll find a fix - how about making the interval 1 day instead of a week?
          • Thanks Bob.
              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
            • @parthian: You can set the interval property of the dashboard widget snippet. You can make it 1 day if you like (or 1 second), though the check will slow down the loading of the dashboard a little.

              Because widgets can't use property sets, the value will be overwritten when you upgrade the UpGradeMODX package. I'm thinking of moving it to a System Setting.
                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
              • I always forget about Properties and Property Sets. A MODx concept I always seem to bypass. Noted and updated to 1 day - until UpgradeMODx is updated.

                Most people will not even know there is a default weeks wait between checks. UpgradeMODx will confidently and emphatically state "MODX is up to date" when it isn't.
                I once had a site hacked within a week of a security warning that I hadn't noticed - so it does happen.

                I think this is a no-brainer Bob. Set it to 1 day by default with your next update please. Make UpgradeMODx even more of a joy.
                • I agree that one day is probably a better option. When I created the package, MODX had not had a security alert for a long time and I liked to wait a week or so after an update to see if any serious bugs had been reported.

                  I'm also toying with the idea of adding a button or link on the Widget panel that would force an instant update to the version list.
                    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