Topics

How Do I Stop the NVDA Updater from Monitoring Specific Addons?


Kenny <kwashingtonbox@...>
 

Hello,


I'm noticing the excellent NVDA Add-on Updater doesn't always point to the newest version of specific NVDA add-ons I have installed.


BrowserNav
Current Version: 1.11
New Version: 1.9


Tony's enhancements
Current Version: 1.7
New Version: 1.4

Keep unchecking the box next to the add-ons being referenced, and clicking close, but the Add-on Updater keeps on notifying me there are new updates available which are actually older versions.


Any idea how to stop this? Don't want to uninstall the Add-on updater for it does well with other NVDA add-ons.


 

You do not mention what version of NVDA you're using.  That matters, as "the newest" is, as far as add-ons go, "the newest compatible with the NVDA you're running."

The Browser Nav page notes that the last version compatible with NVDA 2019.X is Browser Nav version 1.1.   I believe version 1.9 is compatible with 2020.X (even though the actual add-on page for the stable version is still showing several versions back).

The latest stable version of Tony's Enhancements is 1.4, and Add-On Updater does not deal with development versions.  And even the development page for that add-on only has a link to version 1.4.  I can find absolutely no reference to a Version 1.7 being "live" anywhere.

You can always uninstall the add-ons, then manually download and reinstall them.  It could be that will cure the problem going forward.
--

Brian - Windows 10 Pro, 64-Bit, Version 1909, Build 18363  

Science has become just another voice in the room; it has lost its platform.  Now, you simply declare your own truth.

      ~ Dr. Paul A. Offit, in New York Times article, How Anti-Vaccine Sentiment Took Hold in the United States, September 23, 2019

 

 


Kenny <kwashingtonbox@...>
 

I'm using NVDA Version: 2020.1.


I downloaded the files for installing Tony's add-ons directly from his Github page. Not sure if those versions are newer then the one's NVDA are pointing too in the Updater.


They're definitely older for the Browser Nav 1.9 version that the updater wants me to install doesn't have the newly added "Browser Marks" option Tony introduced a few weeks ago. The 1.11 version I have installed does.


Maybe it's just my PC then. I'll just keep closing the add-on updater notice when it pops up. It's just annoying me somewhat.


On 6/15/2020 4:27 PM, Brian Vogel wrote:
You do not mention what version of NVDA you're using.  That matters, as "the newest" is, as far as add-ons go, "the newest compatible with the NVDA you're running."

The Browser Nav page notes that the last version compatible with NVDA 2019.X is Browser Nav version 1.1.   I believe version 1.9 is compatible with 2020.X (even though the actual add-on page for the stable version is still showing several versions back).

The latest stable version of Tony's Enhancements is 1.4, and Add-On Updater does not deal with development versions.  And even the development page for that add-on only has a link to version 1.4.  I can find absolutely no reference to a Version 1.7 being "live" anywhere.

You can always uninstall the add-ons, then manually download and reinstall them.  It could be that will cure the problem going forward.
--

Brian - Windows 10 Pro, 64-Bit, Version 1909, Build 18363  

Science has become just another voice in the room; it has lost its platform.  Now, you simply declare your own truth.

      ~ Dr. Paul A. Offit, in New York Times article, How Anti-Vaccine Sentiment Took Hold in the United States, September 23, 2019

 

 


Kenny <kwashingtonbox@...>
 

I figured out how to stop the Add-on Updater from checking BrowserNav, and Tony's enhancements for updates.


Under NVDA Settings -> Add-on Updater -> Do not Update Add ons [List]. Checked the boxes for the 2 add ons in question and no more false update alert.


On 6/15/2020 5:57 PM, Kenny via groups.io wrote:

I'm using NVDA Version: 2020.1.


I downloaded the files for installing Tony's add-ons directly from his Github page. Not sure if those versions are newer then the one's NVDA are pointing too in the Updater.


They're definitely older for the Browser Nav 1.9 version that the updater wants me to install doesn't have the newly added "Browser Marks" option Tony introduced a few weeks ago. The 1.11 version I have installed does.


Maybe it's just my PC then. I'll just keep closing the add-on updater notice when it pops up. It's just annoying me somewhat.


On 6/15/2020 4:27 PM, Brian Vogel wrote:
You do not mention what version of NVDA you're using.  That matters, as "the newest" is, as far as add-ons go, "the newest compatible with the NVDA you're running."

The Browser Nav page notes that the last version compatible with NVDA 2019.X is Browser Nav version 1.1.   I believe version 1.9 is compatible with 2020.X (even though the actual add-on page for the stable version is still showing several versions back).

The latest stable version of Tony's Enhancements is 1.4, and Add-On Updater does not deal with development versions.  And even the development page for that add-on only has a link to version 1.4.  I can find absolutely no reference to a Version 1.7 being "live" anywhere.

You can always uninstall the add-ons, then manually download and reinstall them.  It could be that will cure the problem going forward.
--

Brian - Windows 10 Pro, 64-Bit, Version 1909, Build 18363  

Science has become just another voice in the room; it has lost its platform.  Now, you simply declare your own truth.

      ~ Dr. Paul A. Offit, in New York Times article, How Anti-Vaccine Sentiment Took Hold in the United States, September 23, 2019

 

 


 

Hi Kenny,

Part of the reason is that the add-ons community did not receive a notice from Tony about new versions of his add-ons. Also, unless requested by add-on authors, there are no separate development releases channel for add-ons.

There are two other reasons:

  1. There is (or was) a huge discussion in the add-ons community about modernizing add-on release workflow and related materials. In the old days, add-ons workflow was intimately tied to NVDA translations, and NV Access people had a hard time maintaining the original version of this workflow (things have improved in recent months somewhat through communication between the original author of this workflow and NV Access staff). However, since the bulk of maintaining add-ons and translations workflow was carried out by people outside of NV Access through NV Access facility, it was felt that, for security reasons and for maintenance, NV Access staff decided to think about modernizing all this. Add-on Updater is merely the first step of this process, and if things go well, there will come a day when I can quietly retire from NVDA development after donating Add-on Updater code to NV Access.
  2. The person responsible for majority of add-on update metadata maintenance (yours truly) is away from his office at the moment for various reasons (mental health and academics being the highest of highest of priorities). For this reason, there is a delay between when an add-on author publishes an announcement about updated add-ons and when they will show up via Add-on Updater. I will indeed return to actively manage add-on update publishing in a few weeks.

Cheers,

Joseph


Kenny <kwashingtonbox@...>
 

Thanks Joseph for clearing the mystery up for me. It's really no big deal. I just disabled the Updater from monitoring the two add-ons in question. All is well again.


On 6/16/2020 3:41 AM, Joseph Lee wrote:

Hi Kenny,

Part of the reason is that the add-ons community did not receive a notice from Tony about new versions of his add-ons. Also, unless requested by add-on authors, there are no separate development releases channel for add-ons.

There are two other reasons:

  1. There is (or was) a huge discussion in the add-ons community about modernizing add-on release workflow and related materials. In the old days, add-ons workflow was intimately tied to NVDA translations, and NV Access people had a hard time maintaining the original version of this workflow (things have improved in recent months somewhat through communication between the original author of this workflow and NV Access staff). However, since the bulk of maintaining add-ons and translations workflow was carried out by people outside of NV Access through NV Access facility, it was felt that, for security reasons and for maintenance, NV Access staff decided to think about modernizing all this. Add-on Updater is merely the first step of this process, and if things go well, there will come a day when I can quietly retire from NVDA development after donating Add-on Updater code to NV Access.
  2. The person responsible for majority of add-on update metadata maintenance (yours truly) is away from his office at the moment for various reasons (mental health and academics being the highest of highest of priorities). For this reason, there is a delay between when an add-on author publishes an announcement about updated add-ons and when they will show up via Add-on Updater. I will indeed return to actively manage add-on update publishing in a few weeks.

Cheers,

Joseph