Closed
Bug 467585
Opened 16 years ago
Closed 16 years ago
Latest Minefield Trunk: extensions can't be overridden
Categories
(Firefox :: Extension Compatibility, defect)
Tracking
()
RESOLVED
INVALID
People
(Reporter: lupatrian, Unassigned)
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2a1pre) Gecko/20081202 Minefield/3.2a1pre
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2a1pre) Gecko/20081202 Minefield/3.2a1pre
Installed the latest trunk; all extensions inactive/greyed out - incl Nightly tester Tools; no button to force install. I attempted to re-install Nightly tester Tools: message that ext is incompatible with this version of Minefield.
I've never had this problem with builds before; do these compatibility issues come up from time to time with a major build change - like, something that you are aware of and that would be fixed with future builds as the exts are made compatible?
I posted my exts here: http://mysite.verizon.net/lupatrian/exts120208.jpg
Reproducible: Always
Steps to Reproduce:
1. Downloaded/installed Minefield 3.2a1pre 12/2 build
2. Opened Minefield; exts unavailable, override unavaiable
3.
Comment 1•16 years ago
|
||
Yes, when you install a version of Firefox with a new version that your extensions don't claim to be incompatible with then they get disabled. You will have to wait for the extension authors to update their extensions for the new version, most will be focusing on the 3.1 nightlies though rather than 3.2 which is what you have.
Status: UNCONFIRMED → RESOLVED
Closed: 16 years ago
Resolution: --- → INVALID
Comment 2•16 years ago
|
||
Since the report is specifically about overriding, I should point out that you can do it yourself:
http://kb.mozillazine.org/Extensions.checkCompatibility
Though, the standard warnings of overriding==bad apply here, especially for a large number of extensions at once. Use caution.
Thank you for the info. I rolled back to yesterday's build, for now. I'd just never had Nightly Tester Tools deactivate before - that one was always compatible, so I thought something might be off somewhere.
I'm never sure if I'm being helpful by reporting, or a Newbie P.I.T.A.! ~:)
If this is helpful: I reinstalled the 12/2 trunk; and set my Check Ext Compatibility to false. All exts loaded fine and seem to be working (so far, so good).
Comment 5•16 years ago
|
||
(In reply to comment #3)
> Thank you for the info. I rolled back to yesterday's build, for now.
What you probably want is to stay on the 3.1 branch.
(3.1b3pre instead of 3.2a1pre)
http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/latest-mozilla-1.9.1/
Or, you could download the 3.1 beta 2 builds:
http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/3.1b2-candidates/
You need to log in
before you can comment on or make changes to this bug.
Description
•