Open Bug 383006 Opened 17 years ago Updated 14 years ago

Can't import more than one user profile by single migration (multiple execution of -migration are required)

Categories

(SeaMonkey :: Startup & Profiles, enhancement)

enhancement
Not set
normal

Tracking

(Not tracked)

People

(Reporter: GavinFlower, Unassigned)

References

(Depends on 1 open bug, )

Details

User-Agent:       Mozilla/5.0 (X11; U; Linux i686 (x86_64); en-US; rv:1.9a6pre) Gecko/20070602 SeaMonkey/2.0a1pre
Build Identifier: Mozilla/5.0 (X11; U; Linux i686 (x86_64); en-US; rv:1.9a6pre) Gecko/20070602 SeaMonkey/2.0a1pre

I installed the seamonkey pre alpha, and it only allowed me to import one user profile of the 2 defined.

The import dialog had both listed with radio buttons.

The default was selected.

I clicked on the other and the default became unselected.

I clicked on default and the other became unselected.

I imported the default.

There appears on way to import more than one profile.


Reproducible: Always

Steps to Reproduce:
see above
Actual Results:  
Could only import one user profile

Expected Results:  
Should be able to import all user profiles

I am using Fedora Core 6 with uptodate patches, 
and have a Dual core AMD 64 chip
Same on Win2000
Really annoying. Actually, why is it needed to **import** instead of just using existing profiles ??
If you want to import multiple profiles, you can invoke the migration a second time, right?

The vast majority of users have one profile and the majority of users with multiple profile would want to import only one profile, so the dialog is designed for that use case.
See http://wiki.mozilla.org/SeaMonkey:New_for_2.0 for information about importing more than one profile.

Its needed because it was a project decision in part to allow us to start with cleaner profiles - some profiles may have been around since the 4.x days.

Otherwise, I think this is invalid/works for me.
(In reply to comment #2)
> If you want to import multiple profiles, you can invoke the migration
> a second time, right?

The UI gives no clues on how to do that.  I only found out through the
wiki page above and I only found that because I was about to file this
as a bug and searched for duplicates first and found this bug.
(Hence I think this is a valid bug that should be fixed before release).

> The vast majority of users have one profile

Seems reasonable, but do we have any collected data that can tell us
the facts instead of just guessing?

> and the majority of users with multiple profile would want to import
> only one profile

I disagree, I would guess the opposite is true.  I for one have multiple
profiles and I want to migrate them all.  I don't see why a user would
like to trash all but one profile just because he/she upgrades to a
newer version.

I think we should remove the "select a profile to migrate" step and just
migrate them all (keep the initial "Import all items from:" step as is
though).
BTW, the wiki page should also list steps for migrating a profile
which has spaces in the name.  For example a profile named Default User:

Run: seamonkey -ProfileManager
click Create Profile and give it the name of the profile you want to migrate
click Exit when you have created the profile
Run: seamonkey -P 'Default User' -migration
click through the migration, make sure you select Default User when it asks.
Exit
Run: seamonkey -ProfileManager
and select the profile in the list

In other words, it's just -createProfile that doesn't accept profile
names with spaces in them (bug 51509).
Changing summary according to explanation by comment #5.
Severity: major → enhancement
Status: UNCONFIRMED → NEW
Depends on: 385128
Ever confirmed: true
OS: Linux → All
Summary: Can't import more than one user profile → Can't import more than one user profile by single migration (multiple execution of -migration are required)
Version: unspecified → Trunk
(In reply to comment #5)
>BTW, the wiki page should also list steps for migrating a profile
>which has spaces in the name.
Fixed.
Hardware: PC → All
I actually use a second profile for viewing stuff that do not want other members of the family to see - this could be as innocuous as researching possible holiday destinations prior to discussing it with them...

Another use of multiple profiles was when I had 3 members of the family using the same computer, each had their own profile, so that their histories were specific to their interests - for example my 6 year old son was fixated by various aspects of public transport.

>>> CONCRETE SUGGESTION <<<
I think when upgrading to a new version of Seamonkey. there should be a check box for each profile (with no 'ALL' option!) so it is an active decision which ones to transfer.  This would tend to eliminate dead (unused) ones.  Obviously(?), if there was only one profile, it should be automatically carried across.
Hi,

First, I've not yet upgraded, and am just trying to figure out how to proceed ...

- Am I correct to understand that these "profiles" are NOT equivalent to one's various email accounts within the Mail function, and that the latter will ALL migrate with the upgrade automatically?

If not: on the Wiki page, it says:
**********
  Profile Migration

The profile migration dialog will come up on the first start of a SeaMonkey 2.x on your machine. It will allow you to migrate your existing settings into a profile called "default".

If you wish to migrate more than one profile or set the profile name, run SeaMonkey with the following arguments (it needs to be run twice):

    * -createProfile <ProfileName>
    * -P <ProfileName> -migration 

Note: spaces in <ProfileName> are NOT permitted with -createProfile. Instead, use -ProfileManager and create the profiles using the GUI. 
***********
I am not that sophisticated a user (surprise!) How the heck do I "run SeaMonkey with the following arguments "??

Thanks!
I maintain an old address (as I still get mail there) and my wife has a separate profile.  We have had these conveniences for a while, and are not sophisticated enough to "run with the following arguments" and I have trouble finding the files with the stored data.  PLease help this old fogey user.
You need to log in before you can comment on or make changes to this bug.