Commit | Line | Data |
---|---|---|
d8aa5ec7 AD |
1 | This files describes API changes in /message/ messaging system, |
2 | information provided here is intended especially for developers. | |
3 | ||
e61a9638 MN |
4 | === 3.1 === |
5 | * get_message_processors accepts an addition parameter for testing, which will just reset processor and exit. | |
59a968dc | 6 | * Deprecated method message_current_user_is_involved() has been removed. |
e61a9638 | 7 | |
36bbb0b7 AA |
8 | === 2.9 === |
9 | * Renderer method \core_message_renderer::manage_messagingoptions now accepts a user id parameter as well. | |
10 | ||
3bcf6b3c RT |
11 | === 2.6 === |
12 | * Message processor extending message_output, should return true in can_send_to_any_users() | |
13 | if it supports message sending to internal (noreply/support) users. | |
56b9a02e YB |
14 | * Message API has been changed to allow attachments. Message processors that can support |
15 | attachments can now use additional parameter as a part of $eventdata. To send attachments, | |
16 | $eventdata should contain properties called "attachment" (must be stored_file) and | |
17 | "attachname" (string). Currently, email message processor is the only one to support | |
18 | attachments. | |
3bcf6b3c | 19 | |
d8aa5ec7 AD |
20 | === 2.2 === |
21 | ||
22 | required changes: | |
23 | * lib/messagelib.php message_send($eventdata) | |
24 | $eventdata->userto should contain a property called "emailstop", $eventdata->userto->emailstop | |
25 | If it is absent it will be retrieved from the user table causing an additional database query |