[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.
[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.
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