Closed (outdated)
Project:
Privatemsg
Version:
7.x-2.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
12 Apr 2012 at 09:49 UTC
Updated:
4 Sep 2023 at 14:20 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
jrao commentedSurprisingly hard to get this right, and the tests took forever to run. Let's see if this patch works.
Comment #2
berdirShould use two spaces instead of tabs.
Took me a while to understand that the first if is just setting the default value. Shouldn't it be possible to change that to a empty($author_added[$mid]), which would make the first condition unessary?
I have to say that I'm not sure if I do understand why this is necessary. Why exactly do we need to send the author a notification? There's always the possibility that there is a bug in the tests :)
Comment #3
jrao commentedTab issue and empty($author_added[$mid]) issue fixed.
For why we need to send author a notification, the reason is privatemsg_message_change_recipient is called when we need to add user as message recipient when handling non-user recipients, so if privatemsg_message_change_recipient is adding author, this means one or more non-user recipient included the author, I think in this case sending notification to author is the right thing to do. The test case for this is in pm_email_notify.test, search for "Send a message to all users"
Comment #4
ptmkenny commented#3: privatemsg-1529498-3.patch queued for re-testing.
Comment #5
ivnish