Closed
Bug 293066
Opened 20 years ago
Closed 20 years ago
IE View link gives an error, updates fail
Categories
(addons.mozilla.org Graveyard :: Public Pages, defect)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
1.0
People
(Reporter: paul, Unassigned)
References
()
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.7) Gecko/20050406 Firefox/1.0.3
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.7) Gecko/20050406 Firefox/1.0.3
IE View (GUID: {6e84150a-d526-41f1-a480-a67d3fed910d}) is listed as 0.8+ - 1.0
in the listings, but selecting it from the front page list gives the error:
"Incompatible Extension or Extension No Longer Available" pretty regardless of
the Firefox version selected. Is this a problem in the system, or is there
something I should change in my install.rdf?
Reproducible: Always
Steps to Reproduce:
1. Select Firefox Extensions link from top menu
2. Click ieview (#5 in the list at the moment)
3. Boom
Actual Results:
Error message as above
Expected Results:
Loaded the main IE View listing pageI'm assuming it's a symptom of the same problem that the Tools|Extensions|Update function never finds new IE View versions. In my tests, and via reports from various users, those with versions below 1.0 never see the new 1.0 (and soon 1.2, in all likelihood) versions.
Summary: IE View link from most-popular-extensions page gives an error → IE View link gives an error, updates fail
p.s. more than happy to do additional groundwork/tracing to narrow down the error -- just let me know what sort of sniffing you'd like to see.
Comment 3•20 years ago
|
||
Is this still the case?
Works for me, pointing users to https://addons.mozilla.org/extensions/moreinfo.php?id=35&application=firefox
Status: NEW → RESOLVED
Closed: 20 years ago
Resolution: --- → WORKSFORME
Comment 5•19 years ago
|
||
AMO BUGSPAM FOR COMPONENT MOVE AND DELETE (FILTER ME)
Component: Listings → Web Site
| Assignee | ||
Updated•9 years ago
|
Product: addons.mozilla.org → addons.mozilla.org Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•