DownloadHelper deactivated after Firefox update (Windows 11)
Chris Chapman
Eric Marceau
[Firefox]
[1] Plug-in Level
The issue with these types of problems (Browser updates) is that the Browser's default setting for auto-update of Plug-ins is "Auto", meaning "ON".
That is an issue which may be out of VDH's control. However, the page at
https://extensionworkshop.com/documentation/manage/updating-your-extension/
seems to suggest that the Plug-in's auto-update settings are controllable by the Developer. So I leave that to them to review and, if need be, reconsider setting the default setting for auto-updates to "false", rather than "true". IMHO, "false" seems to be the mode that "protects" the end-user and advise that this should be the default. This in turn would put the onus for ALL auto-update action completely into the individual user's hands, and control and prevent all future "surprise" updates having issues at times that disrupt other user priorities.
- It would be nice if developers could review their earlier/current stance,
- decide on a stance for the application going forward, and
- communicate to the community what that stance would be. (hopefully a "false" default 🙂)
[2] Browser Level
I've tried to find a Browser global setting (Firefox) to set the "auto-update" action default as "OFF".
For Firefox, using
about:config [NOTE: proceed with caution]
and searching for "update", I found the settings
app.update.auto true [browser default]
http://kb.mozillazine.org/App.update.auto
https://support.mozilla.org/en-US/questions/1315028
Seems to suggest applicable to Browser, not plug-ins
extensions.update.autoUpdateDefault true [browser default]
https://support.mozilla.org/en-US/questions/952162
Will auto-update ONLY IF extensions.update.enabled has identified an update is available
extensions.update.enabled true [browser default]
https://blog.mozilla.org/addons/how-to-turn-off-add-on-updates/
Global control switch on whether to attempt any "Add-on update scan" for update availability.
"false" suppresses all globally
(I don't know if that would suppress the choice radio-buttons for each individual plug-in's settings.)
So, this last setting seems to be the one to modify for a global freeze on plug-ins. I am still having an internal debate on whether I want to go that route or to stick with control at the plug-in level. After all, if this last one is set false, then later set to true, ALL the plug-ins would be updated at the same time, possibly creating an impossible nightmare if each individual plug-in had similar update issues. I don't think I would want to contemplate that, as a desktop user.
However, from a standpoint of an Admin for a group of users, that
would definitely be attractive to ensure a "freeze" on deployed
infrastructure that would ensure business continuity. So, the
course to follow very much depends on your context.
Given all that, from an individual Desktop User's standpoint, unless you set "extensions.update.enabled" to "false", the issue is one of having to "repair" plug-ins after each Browser update, which dictates a User/Admin control on when and how the Browser itself should be updated, and be prepared with a set of actions for "cleanup" after each such update. That would include manual change of the auto-update setting for ALL plug-ins to "OFF" manually. 🙁
Food for thought!
Eric
just a user
Does anyone have any advice on how to deal with a problem which we have - were most times Firefox is updated this de-activates the Downloadhelper extension - plus also loses the companion App licence registration - meaning we have to re-enter this each time Firefox is updated
--
You received this message because you are subscribed to the Google Groups "Video DownloadHelper Q&A" group.
To unsubscribe from this group and stop receiving emails from it, send an email to video-downloadhelper...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/video-downloadhelper-q-and-a/5e8a2122-21d7-49bd-9e4c-19438b4fea29n%40googlegroups.com.
Eric Marceau
I don't use Windows, but maybe try what works for Linux.
If you open a Console window from "START" button, and (as user, not admin) enter
vdhcoapp install
does that work?
If not, can one of the developers indicate whether running that same command as admin be an option for Windows users?
Eric
just a user
Does anyone have any advice on how to deal with a problem which we have - were most times Firefox is updated this de-activates the Downloadhelper extension - plus also loses the companion App licence registration - meaning we have to re-enter this each time Firefox is updated
Wild Willy
I'm not part of any organization. I'm just a guy at home with his computer. In my
context, I believe it is my responsibility to set the automatic updates value for each
individual add-on independent of what I set on any other add-on. I have some add-ons
that I would like automatic updates for. But I have always disabled automatic updates
for VDH because I want to control those myself. I have always used the betas & it seems
to me I got switched back to the general availability version once several years ago. I
won't swear to that, but I have a vague recollection that I decided a long time ago to
block automatic updates to VDH.
A couple of fellow users here recently raised another reason, stronger than mine, for
blocking automatic updates to VDH. It seems they suffered the grave misfortune of the
browser deciding to update VDH while the user was in the process of using VDH to download
something. The download was abruptly terminated, causing general havoc & consternation,
not to mention annoyance. But you should be clear about this. It was the BROWSER doing
this, NOT VDH. VDH does NOT update VDH. The BROWSER updates VDH.
It's an interesting concept you raise that an add-on can control its own automatic update
policy. You don't seem 100% convinced about what you read. In any case, I think it is
prudent for the time being that everybody disable automatic updates to VDH mainly because
the browser can unilaterally decide to do an automatic update without checking whether
the add-on is in use.
In my experience, the issue with a license being lost had to do with the CoApp not being
properly recognized after an update. This seems to be more about the CoApp than the
browser extension side of things. There have been plenty of threads about that subject
recently & I refer everyone to go find those. There is a page of documentation on the
subject on GitHub. People need to become aware that there are some VDH documentation
resources in a Wiki on GitHub. Get familiar with that & get used to referring to that.
Go find it. There is a search facility on GitHub. It's easy to find the VDH stuff on
GitHub. Make the effort to find that.
Speaking of the CoApp, it does NOT automatically update. You have to go get the CoApp
yourself. A link for that is on the home page of this forum. When you go to the CoApp
repository on GitHub, you are presented with an array of choices. You must choose the
CoApp installer that is appropriate for your system. There are multiple choices for each
of Linux, Mac, & Windows. If you install the wrong one, you will be making trouble for
yourself. So be sure to pick the right one. There is also a page on the VDH web site
that points to the plethora of choices for the CoApp, but I'm not sure that page always
points to the latest CoApp. The latest CoApp at this moment is 2.0.14. That's what
everybody should be using. The safest way to make sure that's what you have is to go to
GitHub & get the right one yourself. And I hesitate to even mention 2.0.14 because
that's only what is current today. If you are reading this at some future date, 2.0.14
will almost certainly not be the latest one. No matter when you are reading this, get
whatever is the latest one on the GitHub web page.
GitHub uses the terminology "asset." Each CoApp installer is an asset on GitHub. GitHub
displays only some of the CoApp installers, some of the assets. You need to look for the
button that says it will expand all the assets. Click that to make sure you are seeing
the complete list of choices for the CoApp.
When I install a new version of the CoApp, I follow these steps:
1. In the BROWSER settings, disable the VDH add-on.
2. Run the CoApp installation, including whatever extra steps might be appropriate. I
gather there are some extra steps on Linux & Mac. I'm on Windows & I know nothing about
either Linux or Mac. So inform yourself on those platforms.
3. Back in the browser settings, enable the VDH add-on again.
4. Open the first page of VDH settings & expand each section to make sure everything
looks the way it should.