Closed Bug 41887 Opened 26 years ago Closed 21 years ago

first time you launch addressbook after migration, address book names are wrong

Categories

(SeaMonkey :: MailNews: Address Book & Contacts, defect, P3)

x86
All
defect

Tracking

(Not tracked)

RESOLVED INVALID
Future

People

(Reporter: sspitzer, Assigned: cavin)

References

Details

(Keywords: polish, Whiteboard: [nsbeta3-])

Instead of "Personal Addressbook", it shows up as "abook.ldif" I knew about this when I turned on the migration code, but I never got around to fixing it. this is a low priority bug. I'll talk to chuang about how to fix it.
Is this corrected the second time after relaunch?
QA Contact: lchiang → esther
if you quit and restart, the ab names are correct. my guess is the problem lies with the ab datasource not notifying the observer (the tree) that he name has changed.
moving to M18.
Target Milestone: --- → M18
Good polish candidate. Nominating for nsbeta3 and polish.
Keywords: nsbeta3, polish
Keywords: relnote2
Mail triage is marking nsbeta3-
Whiteboard: [nsbeta3-]
Target Milestone: M18 → Future
Keywords: relnote3, relnoteRTM
This is purely cosmetic - is it worth relnoting? The blurb: It seems unclear to me whether this bug requires either of a "developer" or "user" release note for Netscape 6 RTM. If anyone feels it does, can they please draft one and then nominate with the relnote-user or relnote-devel strings in the Status Whiteboard. Thanks :-) Gerv
Keywords: relnote2, relnote3
I think this is fixed with bug 50584. Mark fixed.
Status: NEW → RESOLVED
Closed: 26 years ago
Resolution: --- → FIXED
QA Contact: esther → laurel
Using oct24 commercial branch build linux rh6.0, Win98 This is OK for most address books immediately after migration, first session shows PAB and Collected AB. However, my main Linux profile shows the PAB as "tmp35C20FF500A1928.ldif" until the second launch, then it goes to Personal Address Book. I don't recall everything about this AB, but I probably imported it at some time in 4.x. Chuang: is this an issue for another bug, and do you know if it's an existing one? Asking you, but will also look myself. Just trying to cover the bases.
Maybe I didn't fixed all cases. I only checked for "abook.ldif" and convert it into "Personal Address Book". Seth will have more idea. Anyway, we can reopen this bug.
Will reopen for the non abook.ldif case mentioned
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Keywords: relnoteRTM
QA Contact: laurel → pmock
Assign it to myself..
QA Contact: pmock → fenella
*** Bug 70403 has been marked as a duplicate of this bug. ***
QA Contact: fenella → nbaca
The fix will be included in the patch for 70396. We use filename instead of the real display.
Depends on: 70396
reassigning to cavin
Assignee: chuang → cavin
Status: REOPENED → NEW
Does the problem still exist? I don't see it though. Can we close it and deal with bug 70396 separately?
Marking WORKSFORME. Please reopen it if the problem still exists.
Status: NEW → RESOLVED
Closed: 26 years ago → 24 years ago
Resolution: --- → WORKSFORME
Reopening because of non-abook.ldif case.
Status: RESOLVED → REOPENED
Resolution: WORKSFORME → ---
The Personal Address Book and Collected Addresses address book are ok. The problem occurs when other address books are migrated from 4.x. For instance in 4.x I also have the following address books: - Catonsville: which is an address book that I defined - Infospace Directory - Verisign Directory After migrating and opening the address book window for the 1st time it displays: - Catonsville.ldif - infospace.dif - verisign.ldif After an exit/start the address book window now displays: - Catonsville (as expected) - infospace - completely gone - verisign - compltely gone Expected Results: - Catonsville not to have an ldif extension during the first launch - infospace - if this is not supported then can it be removed for the 1st launch? - verisign - if this is not supported then can it be removed for the 1st launch?
Product: Browser → Seamonkey
As we no longer are able to import (standard) address books from 4.x and ldap directories are WFM, I think we can close this bug as invalid, we'd also have had more instances of this bug if we had problems with 6.x to mozilla, but I don't think they are as the code bases were very much closer.
Status: REOPENED → RESOLVED
Closed: 24 years ago → 21 years ago
QA Contact: nbaca → addressbook
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.