470801 - Import SM 1.x profile changes signature file path

Status: RESOLVED WONTFIX

(SeaMonkey :: Startup & Profiles, defect)

Description

[Ed Mullen]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1b3pre) Gecko/20081202 SeaMonkey/2.0a2
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1b3pre) Gecko/20081202 SeaMonkey/2.0a2

When installing SM 2.0a2 it imported my 1.1.13 profile.  However it changed the path to my signature file in all email and news accounts from the location specified in the 1.1.13 to the new 2.0a2 profile folder.  Additionally, it place a copy of the original signature file in the new profile folder.

I use a program to generate random signature taglines.  It generates a new sig file every 2 minutes.  Consequently, I now had a static sig file instead of a dynamic one.


Reproducible: Didn't try

Steps to Reproduce:
1.  Install SM 2.0a2
2.  Import SM 1.1.13 profile
3.  Run Mail/News

Actual Results:  
The signature file was copied from its original location folder to the new 2.0a2 profile folder.  The path in the prefs.js file was changed from the original 1.1.13 location to the new 2.0a2 profile folder.

Expected Results:  
No change to the signature file's location should be made when importing a profile.

Comment 1

[Tony Mechelynck [:tonymec]]

I seem to remember another bug report about the same problem but I can't track it down.

See also Thunderbird bug 470805.

Comment 2

[:Hb]

> However it changed the path ... from the location specified in 
> the 1.1.13 to the new 2.0a2 profile folder.  Additionally, it
> place a copy of the original signature file in the new profile folder.

That is wanted by the vast majority of users. Randomly generated signatures need special treatment which the migration routine can't offer. WONTFIX

Comment 3

[Ed Mullen]

(In reply to :Hb from comment #2)
> > However it changed the path ... from the location specified in 
> > the 1.1.13 to the new 2.0a2 profile folder.  Additionally, it
> > place a copy of the original signature file in the new profile folder.
> 
> That is wanted by the vast majority of users. Randomly generated signatures
> need special treatment which the migration routine can't offer. WONTFIX

Really?  The "vast majority of users" want the migration routine to change their settings?  Really?

The program I use writes to a static file name.  So, SeaMonkey should NOT change the file name/path.  Regardless of how the sig file is generated, if the sig file name does not change SeaMonkey should NOT change it.

And, I have no idea why I got an email notification of a change in this bug 4 years after the last change to it.

Ya think maybe this is a problem?