Closed Bug 224714 Opened 21 years ago Closed 16 years ago

if pab.filename not set, pab doesn't migrate

Categories

(MailNews Core :: Profile Migration, defect)

x86
Windows 2000
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: Bienvenu, Assigned: Bienvenu)

References

Details

(Whiteboard: fixed-aviary1.0)

Attachments

(1 file, 1 obsolete file)

Some installations don't have pab.filename set in prefs.js, but in an autoconfig js file, which doesn't get downloaded at profile migration time. This results in the pab not getting migrated.
Attached patch proposed fix (obsolete) (deleted) — Splinter Review
fix checked in.
Status: NEW → RESOLVED
Closed: 21 years ago
Resolution: --- → FIXED
Attached patch better fix (deleted) — Splinter Review
move where we add the pab filename to before we start iterating over the prefs.
Attachment #134775 - Attachment is obsolete: true
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Attachment #149371 - Flags: superreview?(mscott)
Attachment #149371 - Flags: superreview?(mscott) → superreview+
Whiteboard: fixed-aviary1.0
Product: MailNews → Core
David, Fixed? or obsolete? mozilla/mailnews/base/src/nsMessengerMigrator.cpp not found
QA Contact: esther → profile-migration
I guess obsolete - it was for migrating from 4.x, which we don't do anymore.
Status: REOPENED → RESOLVED
Closed: 21 years ago16 years ago
Resolution: --- → INVALID
Product: Core → MailNews Core
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: