<![CDATA[ UpgradeMODX 2.6.4 to 2.6.5 Not Available. 2.6.1 to 2.6.5 No Problem - My Forums]]> https://forums.modx.com/thread/?thread=104045 <![CDATA[UpgradeMODX 2.6.4 to 2.6.5 Not Available. 2.6.1 to 2.6.5 No Problem]]> https://forums.modx.com/thread/104045/upgrademodx-2-6-4-to-2-6-5-not-available-2-6-1-to-2-6-5-no-problem#dis-post-559545
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]]> parthian Jul 13, 2018, 02:18 PM https://forums.modx.com/thread/104045/upgrademodx-2-6-4-to-2-6-5-not-available-2-6-1-to-2-6-5-no-problem#dis-post-559545 <![CDATA[Re: UpgradeMODX 2.6.4 to 2.6.5 Not Available. 2.6.1 to 2.6.5 No Problem]]> https://forums.modx.com/thread/104045/upgrademodx-2-6-4-to-2-6-5-not-available-2-6-1-to-2-6-5-no-problem#dis-post-559615
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.]]> BobRay Jul 15, 2018, 10:27 PM https://forums.modx.com/thread/104045/upgrademodx-2-6-4-to-2-6-5-not-available-2-6-1-to-2-6-5-no-problem#dis-post-559615 <![CDATA[Re: UpgradeMODX 2.6.4 to 2.6.5 Not Available. 2.6.1 to 2.6.5 No Problem]]> https://forums.modx.com/thread/104045/upgrademodx-2-6-4-to-2-6-5-not-available-2-6-1-to-2-6-5-no-problem#dis-post-559611
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.]]> parthian Jul 15, 2018, 03:02 PM https://forums.modx.com/thread/104045/upgrademodx-2-6-4-to-2-6-5-not-available-2-6-1-to-2-6-5-no-problem#dis-post-559611 <![CDATA[Re: UpgradeMODX 2.6.4 to 2.6.5 Not Available. 2.6.1 to 2.6.5 No Problem]]> https://forums.modx.com/thread/104045/upgrademodx-2-6-4-to-2-6-5-not-available-2-6-1-to-2-6-5-no-problem#dis-post-559583
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.
]]> BobRay Jul 14, 2018, 05:27 PM https://forums.modx.com/thread/104045/upgrademodx-2-6-4-to-2-6-5-not-available-2-6-1-to-2-6-5-no-problem#dis-post-559583 <![CDATA[Re: UpgradeMODX 2.6.4 to 2.6.5 Not Available. 2.6.1 to 2.6.5 No Problem]]> https://forums.modx.com/thread/104045/upgrademodx-2-6-4-to-2-6-5-not-available-2-6-1-to-2-6-5-no-problem#dis-post-559580 andytough Jul 14, 2018, 12:30 PM https://forums.modx.com/thread/104045/upgrademodx-2-6-4-to-2-6-5-not-available-2-6-1-to-2-6-5-no-problem#dis-post-559580 <![CDATA[Re: UpgradeMODX 2.6.4 to 2.6.5 Not Available. 2.6.1 to 2.6.5 No Problem]]> https://forums.modx.com/thread/104045/upgrademodx-2-6-4-to-2-6-5-not-available-2-6-1-to-2-6-5-no-problem#dis-post-559577 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?]]> parthian Jul 14, 2018, 08:35 AM https://forums.modx.com/thread/104045/upgrademodx-2-6-4-to-2-6-5-not-available-2-6-1-to-2-6-5-no-problem#dis-post-559577 <![CDATA[Re: UpgradeMODX 2.6.4 to 2.6.5 Not Available. 2.6.1 to 2.6.5 No Problem (Best Answer)]]> https://forums.modx.com/thread/104045/upgrademodx-2-6-4-to-2-6-5-not-available-2-6-1-to-2-6-5-no-problem#dis-post-559564
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.]]> BobRay Jul 14, 2018, 05:54 AM https://forums.modx.com/thread/104045/upgrademodx-2-6-4-to-2-6-5-not-available-2-6-1-to-2-6-5-no-problem#dis-post-559564 <![CDATA[Re: UpgradeMODX 2.6.4 to 2.6.5 Not Available. 2.6.1 to 2.6.5 No Problem]]> https://forums.modx.com/thread/104045/upgrademodx-2-6-4-to-2-6-5-not-available-2-6-1-to-2-6-5-no-problem#dis-post-559562
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

]]> andytough Jul 13, 2018, 11:42 PM https://forums.modx.com/thread/104045/upgrademodx-2-6-4-to-2-6-5-not-available-2-6-1-to-2-6-5-no-problem#dis-post-559562