Closed Bug 667987 Opened 13 years ago Closed 13 years ago

Make globally installed Add-ons updatable

Categories

(Toolkit :: Add-ons Manager, defect)

5 Branch
All
Windows XP
defect
Not set
critical

Tracking

()

VERIFIED DUPLICATE of bug 300967

People

(Reporter: Ulf.Zibis, Unassigned)

Details

User Agent: Mozilla/5.0 (Windows NT 5.1; rv:5.0) Gecko/20100101 Firefox/5.0
Build ID: 20110615151330

Steps to reproduce:

I moved most of my Add-ons to "C:\Program Files\Mozilla Firefox\extensions.


Actual results:

They got automatically updated via update from 4.0.1 to 5.0, but that's all.
Now I have few incompatible Add-ons. If they would become compatible some day, I can't have them updated, if the are installed globally. That more than a pity.
They will reside there for ever :-(



Expected results:

Please make globally installed Add-ons updatable!
I can make them enabled via "Addon Compatiblity Reporter", but that's a security risk.
Blocks: 638839
Severity: normal → critical
OS: Other → Windows XP
No longer blocks: 638839
Component: General → Add-ons Manager
Product: Firefox → Toolkit
QA Contact: general → add-ons.manager
Status: UNCONFIRMED → RESOLVED
Closed: 13 years ago
Resolution: --- → DUPLICATE
Status: RESOLVED → VERIFIED
(In reply to Dave Townsend (:Mossop) from bug 300967 comment #30)
> We're not going to support automatically updating extensions in anywhere
> other than the profile.

This statement appears wrong!
I updated FF from 10.0.0 to 10.0.1.
After restart I was informed, that the 'Minimap Addon' is no more compatible.
(Version 0.3.13 was installed globally)
I acknowledged for search for compatible updates.
After, version 0.3.17 was automatically installed properly in global extensions folder.
As we can see, global extensions update (1) is possible and (2) happens under the condition, that add-on became incompatible.
So please make global extensions up-datable, automatically and/or via Add-ons Manager, even if they are just outdated.
Version: 5 Branch → 10 Branch
Version: 10 Branch → 5 Branch
You need to log in before you can comment on or make changes to this bug.