After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 212026 - Contact lists should depend on contacts not email addresses
Contact lists should depend on contacts not email addresses
Status: RESOLVED DUPLICATE of bug 250431
Product: evolution
Classification: Applications
Component: Contacts
unspecified
Other All
: Normal minor
: ---
Assigned To: evolution-addressbook-maintainers
Evolution QA team
: 207701 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2001-10-08 16:35 UTC by elpilluli
Modified: 2004-04-13 10:30 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description elpilluli 2001-10-08 16:35:47 UTC
Contact lists should depend on contacts, not email addresses. That way, changing an email address for an specific contact will then change the lists that contact is included to accordingly.




thanks.
Comment 1 Damon Chaplin 2001-10-24 20:01:14 UTC
I think you mean in the calendar event/task editor dialogs here,
don't you?

Do you mean it should just depend on the contact's name?
Maybe we could fall back to that if the email address can't be
found.

I think that means changing the ESelectNames thing.

But there is a chance of getting the wrong person, with the same
name.
Comment 2 elpilluli 2001-10-25 08:21:41 UTC
   Well, My initial comments were for contact lists. They seem to
depend on email addresses only, not contacts. So If you create a list
with several of your contacts, and later change one email address of
one of these contacts, the list doesn't get updated as it doesn't
depend on contacts but seems to copy the email address of each
contact, duplicating your addressbook which seems confusing.

Comment 3 yminsky 2001-12-30 15:12:46 UTC
A related problem:  when you export a contact list, rather than
getting the full contact information, it exports a VCF file containing
only the emails.  This is not the natural behavior --- I was quite
surprised when I emailed a contact list to my wife and discovered that
it didn't contain the addresses it should have.
Comment 4 Chris Toshok 2002-01-23 03:03:47 UTC
the contact list can support either direct email addresses or links to
contacts (links will update when the contact they link to changes).

you have to drag the contacts into the list editor for a link to be
created.  enterring the email address into the field gives you a
non-linked contact.

you can tell which is which by looking in the list inside the contact
list editor.  If the address looks like:

  Chris Toshok <toshok@ximian.com>

it's a link to a contact.  if it looks like:

  toshok@ximian.com

it's just a normal email address (that won't be updated).
Comment 5 elpilluli 2002-01-30 08:54:28 UTC
Tried to verify the fixed but didn't work for me (evolution 1.0.1).
Created a new list by drag and drop a few contact into the list (they
show as "Name Surname <mail@ximian.com>", etc.). Close the list, open
the contact to change the email address, save, open th elist again and
the email of the specific contact dones't get updated.



Comment 6 Chris Toshok 2002-01-30 19:47:50 UTC
Ah, I see what the problem is.  Turns out that the contact list isn't
being updated immediately when you update a card it depends on.  If
you Search->Clear you'll see the changed contact list.
Comment 7 elpilluli 2002-01-31 07:23:31 UTC
It does not work for me :-? Even doing a Search->Clear the list
doesn't get updated when I change an email address. I've even closed
evolution, open it again and the list is still not updated.
Comment 8 André Klapper 2004-03-10 12:22:50 UTC
could be a duplicate of #7701, not sure though...
Comment 9 Gerardo Marin 2004-03-11 00:47:27 UTC
*** bug 207701 has been marked as a duplicate of this bug. ***
Comment 10 André Klapper 2004-04-13 10:30:20 UTC
marking this one as a dup of 50431, since 50431 is used for tracking
and target milestone.

*** This bug has been marked as a duplicate of 250431 ***