hi there,
just tested the API function privatemsg_reply() in order to use it in my own module.
Seems like the thread_id isn't appended to the $message array, before $message is passed to _privatemsg_send(). That's why a NEW message (having the same subject as the thread-starting message) is sent, instead of appending a reply.
The UI-reply is done by hook_form_altering the original new_message-form, so the bug never appears when not explicitly using the api-function. Therefore it's maybe only a matter for developers :-)
A fix should be quite easy by adding the missing thread_id to the message-array.
Comments
Comment #1
berdirI noticed that too.
There should be spaced before and after the =.
Comment #2
sandfurz commentedComment #3
berdirLooks good now.
Comment #4
litwol commentedThanks!
Comment #5
naheemsays commentedThis has not been committed yet.
Comment #6
naheemsays commentedand committed now: http://drupal.org/cvs?commit=221382
Comment #7
litwol commentedThis was rather weird. using my old checkout from d.o (this one is many months old but still *clean*) i was able to commit this patch but it didnt actually arrive in the repository O_o... i even deleted privatemsg.module and ran update to restore it which still showed the patched line.
i then did a whole fresh checkout which showed me privatems.module without the patched line .... ah so weird. anyway i commited it, verified it. and closing this issue :).
http://drupal.org/project/cvs/3279