Let's say I am user A and am connected with user B. User B now requests to connect with user C, who accepts. I am not connected with user C, so when B and C become buddies I do not see that in my buddies' activities! This is due to the fact that user C was the originator of the 'add' action and I do not have access to his activities. Logically, I would definitely expect to see that my buddy B has connected with user C.
This problem can be solved if you consider that BOTH users B and C performed an 'add' action - user B requested to be connected and user C accepted the request. I'm attaching a patch that creates an additional activity record for the original requestor when requests are accepted. Now I will be able to see that B connected to C. If I then connect with C myself, my activities will show that I connected with user C and buddies' activity list will show that user C connected with me.
The only downside is that user B's buddies' activity list will now show two records - one for A connecting with C and another for C connecting with A. This is probably minor, compared to the original problem of missing information. It can also be dealt with by custom theme methods. By the way, the All Activities list will correctly show only one record.
What do you think?
| Comment | File | Size | Author |
|---|---|---|---|
| buddylist2activity_accept_request.patch | 827 bytes | Roman S |
Comments
Comment #1
sirkitree commented5.x unsupported