Closed (won't fix)
Project:
Privatemsg
Version:
6.x-2.x-dev
Component:
Code
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
30 Nov 2009 at 23:46 UTC
Updated:
26 Jul 2016 at 14:43 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
walker2238 commentedAny updates on this?
Comment #2
berdirStatus: I tried to get this working, turned out to be more complex than I thought. I actually wasn't able to get it working correctly ;)
Question: Why are you asking? #956378: Simplify and clean up the /messages list page will probably include an option to exclude yourself from the Participants list (Will even be the default, I think)
Comment #3
walker2238 commentedI'm asking because I believe I created an issue in regards to being able to get the sender of the message. Anyways it was over a year ago and I saw this issue so I figured it was most likely on the back burner.
If I recall correctly, there is no way to find the sender of the last message in the participants thread.
Comment #4
berdirAttaching a first, proof of concept patch.
Notes:
- All tests pass
- Currently, participants are ordered by their id. I don't know yet if it possible to do anything else.
- A very basic performance test with disabled sql cache showed that this is a bit faster (~11,5req/s vs. 10req/s). I need to do more testing with a bigger database and a user that has more messages.
Comment #5
berdirComment #6
berdir#4: load_participants_separate.patch queued for re-testing.
Comment #7
berdirI played around with this, but wasn't that successfull, the new separate query is actually slower than the current list query.
Not sure how to proceed here, this will most likely have to wait until pm_thread is in. Maybe we can add a pm_thread_participants table, listing all participants of a thread, the problem there is that we only want to show participants which actually sent a message to you.
Comment #8
berdirWork in progress patch, will probably fail some tests.
Comment #10
oadaeh commentedThis issue is being closed because it is against a branch for a version of Drupal that is no longer supported.
If you feel that this issue is still valid, feel free to re-open and update it (and any possible patch) to work with the 7.x-1.x branch (bug fixes only) or the 7.x-2.x branch.
Thank you.