Closed Bug 673672 Opened 9 years ago Closed 2 years ago

SM upgrade 2.0.14 to 2.2 fails to migrate cookies

Categories

(SeaMonkey :: Startup & Profiles, defect, major)

SeaMonkey 2.2 Branch
x86
Windows Vista
defect
Not set
major

Tracking

(Not tracked)

RESOLVED INCOMPLETE

People

(Reporter: olivier.vit, Unassigned)

Details

(Keywords: dataloss, qawanted, Whiteboard: [qaw: see comment 5 (and 6)])

User Agent: Mozilla/5.0 (Windows NT 5.1; rv:5.0) Gecko/20110706 Firefox/5.0 SeaMonkey/2.2
Build ID: 20110706120824

Steps to reproduce:

Runned the SM 2.2 installer on a computer with 2.0.14 running, installed in to a different folder.


Actual results:

Everything looked fine, but visiting any web site that uses my cookies to recognize me, I have to identifiy myself again.

It happened on 2 different machines


Expected results:

Cookie based authentication should continue to work
Severity: normal → major
OS: Other → Windows Vista
Hardware: All → x86
So when you open the Data Manager (Tools Menu) and select "Cookies only" the list is blank? All other data like bookmarks and history are fine?
The cookies I have mostly match the sites I visited these last few days. The other ones are probably from Ad networks.

My old bookmarks are still there, while I don't use them anymore. 
My 6 months of history are there also.

The fact is that I used to run Firefox Sync with passwords only, between 2 instances of SeaMonkey and 2 of Firefox, and I have chosen recently to also sync preferences (does this include cookies ?)
Could be a side effect of this change ?
Just did the upgrade on my wife's computer, she isn't using Sync and all cookies are gone, while Bookmarks and History is there.
They didn't get migrated ?
SeaMonkey 2.2 should use the same profile as SeaMonkey 2.0.x. We'll need to investigate what happened there.
What happened is that SeaMonkey 2.0 uses bookmarks.html while SeaMonkey 2.1+ switched to Places (places.sqlite) for bookmarks storage. So the question is why bookmarks did not auto import when the profile was opened by SM 2.2.
As a side note, is this (profile update) something that could have an (automated) test for ? (assuming there is none yet.)
(Or do test harnesses not support that ?)
Component: General → Startup & Profiles
Keywords: dataloss, qawanted
QA Contact: general → profile-manager
Whiteboard: [qaw: see comment 5 (and 6)]
(In reply to Philip Chee from comment #5)

Hum, was that comment meant for bug 673474 rather ?
(In reply to Philip Chee from comment #5)
> What happened is that SeaMonkey 2.0 uses bookmarks.html while SeaMonkey 2.1+
> switched to Places (places.sqlite) for bookmarks storage. So the question is
> why bookmarks did not auto import when the profile was opened by SM 2.2.

One possibility is the known fact that the migration only happens the first time. So if you upgrade 2.0 to 2.1, are not satisfied, and go back to 2.0, any later changes to your bookmarks will be lost if you later upgrade again to 2.1 or later.
Ancient version. Cookies and permissions db code changed a number of times since then and directly upgrading from 2.0.14 is no longer supported. Please reopen if you experience this problem with a current SeaMonkey version and a valid upgrade path.
Status: UNCONFIRMED → RESOLVED
Closed: 2 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.