UpgradeMODX not always aware of new version
whitebyte opened this issue · 5 comments
Sometimes it shows upgrade button, sometimes doesn't.
Yes, it's doing that for me too on some sites. I'm not sure why.
Me too! It seems 25% of the sites I'm trying to upgrade to 2.5.2 still think 2.5.1 is the latest version.
I've noticed this too, but have been unable to find the cause. It does
straighten out over time for me. I've never seen it lag for more than a
week.
On Mon, Nov 14, 2016 at 7:53 PM, digitalpenguin notifications@github.com
wrote:
Me too! It seems 25% of the sites I'm trying to upgrade to 2.5.2 still
think 2.5.1 is the latest version.—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
#9 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAUcopAnEVGslu59_8_6pmOwEvwsUQAnks5q-RB_gaJpZM4HbVOF
.
A work-around as brought up by @donShakespeare and @neoneddy on the slack channel is to edit the snippet properties and clear the lastCheck field.
UGM knows there is a new version by looking at the GitHub tags. My guess is that there may be a delay between when the new version is available for download at modx.com and the creation of the tag at GitHub. I believe an API is being created at MODX so UGM won't have to consult GitHub at all. That may solve the problem.