Closed
Bug 13719
Opened 26 years ago
Closed 26 years ago
when you run -installer, and try to migrate a profile you already have migrated, it should warn you
Categories
(MailNews Core :: Profile Migration, defect, P3)
Tracking
(Not tracked)
VERIFIED
INVALID
M15
People
(Reporter: Bienvenu, Assigned: dbragg)
Details
I was trying to migrate a profile I'd already migrated, and it didn't warn me
when I picked that profile again (granted it didn't have "migrate" in front of
the profile name, but I think that's rather subtle). And it should try to detect
if the directory it would migrate to exists, and if not, offer to re-migrate.
migrate a profile that's already been migrated is not part of the feature work
that we had planned.
this sounds like an issue for post beta... and we need to evaluate the
situations and determine the value of doing/not doing so.
Status: NEW → RESOLVED
Closed: 26 years ago
Resolution: --- → INVALID
Marking invalid since there is no "migrate" button anymore. You simply select a
profile and if it hasn't been migrated it gets migrated. If it has been or is a
native 5.x profile, SeaMonkey just starts. There's no way for the user to
migrate an already migrated profile.
Updated•26 years ago
|
Status: RESOLVED → VERIFIED
Updated•21 years ago
|
Product: MailNews → Core
Updated•17 years ago
|
Product: Core → MailNews Core
You need to log in
before you can comment on or make changes to this bug.
Description
•