Closed Bug 530570 Opened 16 years ago Closed 16 years ago

[Collector Extension] Fennec: Installs only one add-on at a time

Categories

(addons.mozilla.org Graveyard :: Collector Extension, defect, P2)

x86
Linux
defect

Tracking

(Not tracked)

RESOLVED FIXED
BW-1.1

People

(Reporter: kinger, Assigned: mackers)

References

Details

After restarting, I found that it had only installed one of the two add-ons from my collection, and then proceeded to install the second add-on. Is it only installing one add-on at a time?
Possible dupe of, or related to, bug 520369.
Nope, it should install all extensions in the collection, then restart. It shouldn't give you the restart button until finished. Do you have STR with a particular collection?
I increased the the wait between installing each collection to 3000ms. Might improve matters. I'm testing with the following collection. Both extensions install without problems. https://preview.addons.mozilla.org/en-US/firefox/collection/2b2dcbf0-46ea-b649-a3a2-cd439eebef43
(In reply to comment #3) > I'm testing with the following collection. Both extensions install without > problems. > > https://preview.addons.mozilla.org/en-US/firefox/collection/2b2dcbf0-46ea-b649-a3a2-cd439eebef43 Dave, I get 'Collection not found!'. Do you have any other test collections with more than one add-on? I think this bug is fixed, but I need to verify with another collection.
Ahh, it must have been clobbered by the preview db sync. Try this one: https://addons.mozilla.org/en-US/firefox/collection/166d8c08-d129-373c-e845-c0d78eb5aa38 Remove Weave and URL fixer first.
(In reply to comment #5) > Try this one: > > https://addons.mozilla.org/en-US/firefox/collection/166d8c08-d129-373c-e845-c0d78eb5aa38 Works for me. Tested on: - N900 - Firefox 1.0 - Collector build from src revision 61634.
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → FIXED
Component: Collections → Collector Extension
QA Contact: collections → collector-extension
Product: addons.mozilla.org → addons.mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.