191473 - we need to recreate the users PAB if they delete it

Status: RESOLVED EXPIRED

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

Description

[(not reading, please use [e-mail] instead)]

we need to recreate the users PAB if they delete it.

the user can delete it from the filesystem, which is what aaronl did because his
got corrupt.

but we need to automatically recreate it, or else bad things happen.

we expect it to be there in the autocomplete, spam, mail view, etc. code.

for example, without it, you can't close the junk mail controls dialog.

thanks to aaron for pointing this out.

Comment 1

[Samir Gehani]

Mail triage team: nsbeta1+/adt2

Comment 2

[(not reading, please use [e-mail] instead)]

Attachment: fix

Comment 3

[(not reading, please use [e-mail] instead)]

actually, on closer inspection, we properly recreate the abook.mab file if the
user deletes it.

aaronl, did you just delete the abook.mab file, or did you mess with prefs?

how did you get rid of your personal addressbook?

Comment 4

[(not reading, please use [e-mail] instead)]

whoops, didn't mean to remove keywords / whiteboard

Comment 5

[Ninoschka Baca]

Trunk build 2003-03-13: WinMe
It appears to be working for me as well.

Comment 6

[Samir Gehani]

Mail triage team: nsbeta1-

Comment 7

[(not reading, please use [e-mail] instead)]

actually, I think this was really a dup of bug #106461

I think that aaron might have had a pab, but it was corrupt.

Comment 8

[Robert Kaiser]

MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 9

[Robert Kaiser]

MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but still has no comment since the inception of the SeaMonkey project 5 years ago.

Because of this, we're resolving the bug as EXPIRED.

If you still can reproduce the bug on SeaMonkey 2 or otherwise think it's still valid, please REOPEN it and if it is a platform or toolkit issue, move it to the according component.

Query tag for this change: EXPIRED-20100420