Bug: Update Now updates immediately

With Automatically Download Updates = NO, Update Now will search for updates and then commence to download them. This applies even when updates are already available e.g.

restart Logos with 137 MB updates pending
there is no download as expected
type "Update now"; and
download commences

5277.Update Now.zip

Same should apply to Update Resources.

Find more posts tagged with

Comments

Andrew Batishko

Unless I'm misunderstanding you, this is behaving as expected, and is not a change from past versions of the application. "Update Now" is not an automatic update. It's an explicit user request to begin updating.

SineNomine

Unless I'm misunderstanding you, this is behaving as expected, and is not a change from past versions of the application.

This is a change. Formerly/outside of Beta, Update Now (and Update Resources) simply find stuff to update and indicate the possibility of downloading updates. It takes/took a separate command to commence the download. This is the only reasonable behaviour given that the size of the download--100 KB or multiple GBs or anything in-between--is unknown until the command is executed. Many of us who rely on manual updates do so precisely because of data usage limits.

I'm not on the Beta, but if these commands have been intentionally changed for the Beta, PLEASE do not bring them out of the beta. I will be annoyed, the forums will be flooded with angry threads with thousands and thousands of views, you will lose customers... bad things all 'round.

Dave Hooton

Unless I'm misunderstanding you, this is behaving as expected

The behaviour previously has always respected the no autodownload setting. I could have allowed the download at any time prior to issuing the command; and I normally use it to check for additional updates.

Andrew Batishko

Unless I'm misunderstanding you, this is behaving as expected

The behaviour previously has always respected the no autodownload setting. I could have allowed the download at any time prior to issuing the command; and I normally use it to check for additional updates.

I see now. I was mistaken in my understanding of things. Thanks for bringing this to our attention. We will get it fixed up. It looks like it's been a problem since the 6.3 release in May.

Steve Workman

I see now. I was mistaken in my understanding of things. Thanks for bringing this to our attention. We will get it fixed up. It looks like it's been a problem since the 6.3 release in May.

This should be fixed in 6.5 Beta 3.