Open Bug 1531786 Opened 6 years ago Updated 4 months ago

Update dialog should list plugins which will be disabled

Categories

(Thunderbird :: Add-Ons: General, enhancement)

enhancement

Tracking

(Not tracked)

UNCONFIRMED

People

(Reporter: digulla, Unassigned, NeedInfo)

References

Details

(Whiteboard: [dupeme])

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/72.0.3626.109 Safari/537.36

Steps to reproduce:

The update dialog contains no information which plugins might be disabled by the update. Especially in a corporate environment, I'd like to know that I can't use Thunderbird after the update anymore since the Exchance/Outlook plugins will be disabled.

I'm not asking you to get updates for all plugins at this step (would be great, though). It would be enough to see which plugins are no longer compatible with the new version. I can then postpone the update, check for updates on the Mozilla web sites and do the update when all my important plugins (i.e. those which will make Thunderbird useless for me if they don't work) have been updated.

I would be shocked if this is not a duplicate. But it is challenging finding a match in https://mzl.la/2HewX91
Can you find a match?

(But it makes for interesting reading. We come across things like
Bug 1167920 - Provide better feedback to the user when add-ons are disabled on upgrade
Bug 1505637 - Downgrading should re-enable addons disabled during an update
Bug 1476859 - Updated add-ons re-enable if they are disabled in the add-on manager. )

Component: Untriaged → Add-Ons: General
Flags: needinfo?(digulla)
Whiteboard: [dupeme]

Bug 1476859 is about telling the user when plugins suddenly get enabled again because there is a new version after the plugin was "dead" for a year or even after the user disabled them manually (seems to be fixed by bug 264750
?). I think this is another facet of what I'm asking here.

Bug 1505637 is about getting your plugins back after a downgrade (the upgrade disabled them and the downgrade left them disabled).

Bug 1167920 (and the related bug 775623) talk only about Lightning. This bug is for any plugin.

I've read through about half of the other bugs in the list but couldn't find anything similar to this feature.

Taking all the information into account, I think the update process should do the following:

  1. Get the update for the main software
  2. If possible, the updates for all plugins / extensions / themes.
  3. Display a list of plugins which will be disabled.
  4. Display a list of plugins which could be enabled (= new version available for a manually or automatically disabled plugin).
  5. Ask whether people want to update now
  6. Only after OK, disable outdated plugins and install all updates.

For the lists of plugins (#3 and #4), provide links to the homepage of the plugins so people can quickly check whether there will be a new version soon or whether an important bug (that made them disable the plugin) was fixed.

Flags: needinfo?(digulla)

I would be shocked if this is not a duplicate.

I've seen this request before, but perhaps just on the tb-plannning mailing list.

Type: defect → enhancement

This is exactly the enhancement request that I was going to make after the automatic update to 68.4.1 disabled our Exchange Calendar add-on.
They'll eventually fix the add-on (I hope), but in the meantime, we're stuck.
This has to be improved for enterprise-level adoption.

A simple approach could be to have an option "Upgrade [only] when compatible with all my existing plugins". 78 just broke half my plugin list, and it is very painful. I wonder how that feels for helpdesk in enterprise…
This way, I can leave auto-update on, and not see any update dialogs.

As a workaround, we now have an addon to check for addon compatibility to TB 91.
It also shows when there are alternatives for discontinued addons.
It updates the info every 24 hours.

https://addons.thunderbird.net/en-us/thunderbird/addon/addon-compatibility-check/

So the requested option "Upgrade [only] when compatible with all my existing plugins" can be achieved by setting TB to inform about TB updates, but do not update, then verify the list in the new addon and then manually upgrade TB, when appropriate.

Klaus

Severity: normal → S3
Duplicate of this bug: 1857460

(In reply to klaus from comment #8)

As a workaround, we now have an addon to check for addon compatibility to TB 91.
It also shows when there are alternatives for discontinued addons.
It updates the info every 24 hours.

https://addons.thunderbird.net/en-us/thunderbird/addon/addon-compatibility-check/

So the requested option "Upgrade [only] when compatible with all my existing plugins" can be achieved by setting TB to inform about TB updates, but do not update, then verify the list in the new addon and then manually upgrade TB, when appropriate.

Klaus

How do you set TB to INFORM about updates, instead of just updating (on Ubuntu 22.04)?

You need to log in before you can comment on or make changes to this bug.