Closed Bug 291259 Opened 19 years ago Closed 19 years ago
Need Ability to Force Migration from a particular type
some customers need the ability to bypass the migration wizard where it asks for a migration source to migrate from. They should be able to force migration from a particular type (like Netscape 4.x) and if there is only one profile for that type then the process should not require any user intervention at all.
Status: NEW → ASSIGNED
Target Milestone: --- → Thunderbird1.1
(this can wait until you get back David) 1) Get rid of several obsolete profile prefs: profile.migration_behavior, profile.allow_automigration, profile.migration_directory 2) Add a new preference, profile.force.migration which can be set to the name of the migrator we want to force migration from. Left empty, the user will see the normal list of all available sources we can migrate from. If you give it a value, we automatically force migration from that type. 3) Add support for passing a migrator object into the migration UI. If we do get a migrator, adjust the wizard to skip over the list of migration sources. 4) GetDefaultMailMigratorKey now returns the key and a migrator object if and only if profile.force.migration is set to a migration source which has at least one profile. If we are forcing migration to a migration source which does not have any profiles we return an error so that ::Migrate will fall out and not bring up the wizard at all.
Attachment #181389 - Flags: superreview?(bienvenu)
this is fixed on the aviary 1.0 branch for our customer. Will get feedback on it tomorrow.
Comment on attachment 181389 [details] [diff] [review] the fix do we need to relnote this? Or do we think folks who've set these hidden prefs already (the ones that are going away...) will have already migrated?
Attachment #181389 - Flags: superreview?(bienvenu) → superreview+
Status: ASSIGNED → RESOLVED
Closed: 19 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.