Closed
Bug 269492
Opened 20 years ago
Closed 20 years ago
Update Extension: CookieCuller
Categories
(addons.mozilla.org Graveyard :: Public Pages, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: dy0, Unassigned)
Details
(Whiteboard: Requires DB edit)
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0 My CookieCuller 1.1.0 extension is already compatible with FF 1.0 but right now update.mozilla.org is listing it as compatible up to 1.0PR. Please update the compatibility database. Thanks. Reproducible: Always Steps to Reproduce: 1.Browse to u.m.o 2.list FF 1.0 extensions 3. Actual Results: Didn't see my CookieCuller extension list Expected Results: listed my extension as compatibile with FF 1.0
Updated•20 years ago
|
Assignee: psychoticwolf → jedsbugs
Status: UNCONFIRMED → NEW
Ever confirmed: true
Comment 1•20 years ago
|
||
Bulk Moving Extension/Theme listing bugs to new component. (Filter: masslistingspam)
Component: Update → Listings
Product: mozilla.org → Update
Version: other → unspecified
Reassigning to Wolf for DB edit.
Assignee: Bugzilla-alanjstrBugs → psychoticwolf
Summary: Update the update.mozilla.org db: CookieCuller 1.1.0 is already compatible with FF 1.0 → Update Extension: CookieCuller
Updated•20 years ago
|
Assignee: psychoticwolf → nobody
And the XPI file hosted on U.M.O needs to be updated. The install.rdf file's maxversion string needs to be changed to "1.0". My original cookieculler-1.1.0.xpi file, found at http://downloads.mozdev.org/cookieculler/cookieculler1.1.0.xpi, is correct. The file on U.M.O, cookieculler-1.1.0-fx.xpi, was modified, without my knowledge and authorization I might add, to contain a maxversion string of "0.10". Thanks.
Comment 4•18 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
•