Closed
Bug 537002
Opened 15 years ago
Closed 7 years ago
update from 1.18 to 2.0 causes big problems / profiles disappear / adressbook disapear
Categories
(SeaMonkey :: Startup & Profiles, defect)
Tracking
(Not tracked)
RESOLVED
INCOMPLETE
People
(Reporter: herbert.stimpel, Unassigned)
Details
(Keywords: dataloss, Whiteboard: DUPEME)
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.1; .NET CLR 3.0.04506.648; .NET CLR 3.5.21022; .NET CLR 1.1.4322; InfoPath.2; .NET CLR 2.0.50727)
Build Identifier: seamonkey 2.0 update
update from 1.18 to 2.0.
- my 4 profiles disappeared
- adressbook disapeared
- mails disappeared
- auto import function doesn´t bring an effect.
2 Hours of work on each if my 4 engines until ist runs properly again (I found out how the new folder structure looks like and wich files are needed, then I copied the old files into the new structure and imported the adressbook once new).
That´s not a good update. I AM VERY ANGRY !!!
Reproducible: Always
Steps to Reproduce:
same at 4 PCs
Actual Results:
seeabove
Expected Results:
update like the updates before ( from 1.12 to 1.18)
update like the updates before ( from 1.12 to 1.18),
take over the existing profiles and adressbooks.
Comment 1•15 years ago
|
||
Isn't it "just" that your 1.1.x profile was not migrated?
Whiteboard: DUPEME
Version: unspecified → SeaMonkey 2.0 Branch
| Reporter | ||
Comment 2•15 years ago
|
||
Yes, it is "just" !
No information was given before. It looks like a normal update, e.g. from 1.17 to 1.18., but afterwards much work was to be done and data were missing !
Comment 3•14 years ago
|
||
This sounds like a migration problem. I would have expected other bugs to exist about it but I can't find them back.
Comment 4•10 years ago
|
||
We have "Bug 525038 - -migration does not start migration manager", what for unknown reasons has been marked as DUP of "Bug 537002 - update from 1.18 to 2.0 causes big problems / profiles disappear / adressbook disapear", what has a really unclear bug report
Comment 5•7 years ago
|
||
All these versions are really ancient and migration from them is no longer supported.
Lets mark this resolved. If it occurs using a supported version and a valid upgrade path please reopen.
Status: UNCONFIRMED → RESOLVED
Closed: 7 years ago
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•