Adium

Opened 12 years ago

Closed 12 years ago

#9725 closed defect (fixed)

Meta contacts logs are separate from their contacts logs

Reported by: ripos Owned by: nobody
Milestone: Adium 1.3 Component: Logging
Version: Severity: normal
Keywords: Cc:
Patch Status:

Description

Logging for meta contacts is not working for me for most of my contacts.

I have some chat with alice@…, later she talked with me (> hi alice) from her icq account 111-111-111 (> and now I am from icq), after I realized, that she has two different contacts I have created meta contact for her. We have a long chat over icq (> long chat).

Now history in Log viewer is looking pretty strange.

alice@gmail.com   | empty
111-111-111       | > long chat
Alice Boob        | > hi alice > and now I am from icq
  alice@gmail.com | > hi alice
  111-111-111     | > and now I am from icq

In result, if I want to view history with somebody I look at current icq number (-I) or gtalk email and then find it myself in history logs. Only there I can see real history of talking. When I press -L it shows only history of talking before contacts merging.
And of course, for some contacts it is working perfectly. Even more, demerging and merging back does not help.
I think, that some issue with importing names from Address Book and assigning manual alias have something to do with it, but I have not any proof.

Change History (11)

comment:1 Changed 12 years ago by Jordan

Resolution: worksforme
Status: newclosed

When you have a conversation with a contact that is not a member of a metacontact, then you add them to a metacontact, it does not merge the logs. It will begin to merge the logs only after they are a part of the metacontact. This is normal behaviour.

If you have found that communicating with a contact that is currently a member of a metacontact results in a completely separate log for that sub-contact, then that is a bug, but what you're currently describing is how it's supposed to work.

comment:2 Changed 12 years ago by Zachary West

Resolution: worksforme
Status: closedreopened

This is definitely a bug. Meta contacts should be combined in the log viewer at all times.

comment:3 Changed 12 years ago by Evan Schoenberg

Also, the description by jas above is incorrect; being in a metacontact makes no change to how a contact's transcripts are stored. The combination is solely a matter of display and is unrelated to history.

comment:4 Changed 12 years ago by Jordan

Ahh interesting. I have two cases of this then:

  1. Some accounts that are definitely a part of a metacontact are showing as separate logs in the transcript viewer and are not under the metacontact. This sounds like the display issue Evan describes...
  2. Some accounts actually have two logs, one outside of the metacontact, and some within. This could be just old logs that couldn't be merged though?

comment:5 Changed 12 years ago by Jordan

Milestone: Adium X 1.3

comment:6 Changed 12 years ago by Carlos Morales

comment:7 Changed 12 years ago by Evan Schoenberg

I need someone running a system showing this problem to volunteer to run through several iterations of debug builds, as I'm not seeing it locally. Speak up if you're out there :)

comment:8 Changed 12 years ago by Jordan

I don't think I'll be of any help. In my case, it appears to be merging all logs for accounts that are currently part of the metacontact. I was looking at really really old logs that are also in the log directory that are not showing up under the metacontact.

The only exception to this in my case is bonjour users that are part of a metacontact are always separate.

comment:9 Changed 12 years ago by Zachary West

I'm having this happen locally.

comment:10 Changed 12 years ago by Jordan

Component: Adium CoreLogging

comment:11 Changed 12 years ago by Evan Schoenberg

Resolution: fixed
Status: reopenedclosed

(In [23540]) Special case handling of services for 'to' groups and AIChatLogs to know about jabber/gtalk/livejournal and aim/icq/.mac. This isn't perfect (and the code remains really complicated), but it achieves the desired result. Fixes #9725

Note: See TracTickets for help on using tickets.