Changing state of "Update Automatically" for an add-on doesn't update database entry

VERIFIED FIXED in mozilla1.9.3a5

Status

()

Toolkit
Add-ons Manager
P1
normal
VERIFIED FIXED
8 years ago
8 years ago

People

(Reporter: whimboo, Assigned: Unfocused)

Tracking

Trunk
mozilla1.9.3a5
Points:
---
Dependency tree / graph
Bug Flags:
in-testsuite +
in-litmus -

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [rewrite])

(Reporter)

Description

8 years ago
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.3a5pre) Gecko/20100427 Minefield/3.7a5pre

When you have open the extended digest view for an add-on and click on the "Update Automatically" checkbox it will get checked/unchecked but the new value doesn't get written into the database.

Can we please get this fixed until Friday so we can also test add-on updates?
http://hg.mozilla.org/projects/addonsmgr/rev/a7fb4bb4133b

Also filed bug 562599.
Flags: in-testsuite?
Flags: in-litmus?
Whiteboard: [rewrite] → [rewrite][fixed-in-addonsmgr][needs-review]
Priority: -- → P1
Assignee: nobody → bmcbride
Status: NEW → ASSIGNED
(Reporter)

Comment 2

8 years ago
Looks good but until bug 562622 has been implemented it's not possible to run real tests to check for that setting.
Status: ASSIGNED → NEW
Priority: P1 → --
(Reporter)

Updated

8 years ago
Status: NEW → ASSIGNED
(Reporter)

Updated

8 years ago
Priority: -- → P1
(Reporter)

Updated

8 years ago
Blocks: 562679
r=me based on the landed changeset
Whiteboard: [rewrite][fixed-in-addonsmgr][needs-review] → [rewrite][fixed-in-addonsmgr][needs-landing]
http://hg.mozilla.org/mozilla-central/rev/70e46b11e31f
Status: ASSIGNED → RESOLVED
Last Resolved: 8 years ago
Flags: in-testsuite?
Flags: in-testsuite+
Flags: in-litmus?
Flags: in-litmus-
Resolution: --- → FIXED
Whiteboard: [rewrite][fixed-in-addonsmgr][needs-landing] → [rewrite]
Target Milestone: --- → mozilla1.9.3a5
(Reporter)

Comment 5

8 years ago
Marking as verified based on check-in and passing automated tests.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.