| 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. | |
| 6 | ||
| 36bbb0b7 AA |
7 | === 2.9 === |
| 8 | * Renderer method \core_message_renderer::manage_messagingoptions now accepts a user id parameter as well. | |
| 9 | ||
| 3bcf6b3c RT |
10 | === 2.6 === |
| 11 | * Message processor extending message_output, should return true in can_send_to_any_users() | |
| 12 | if it supports message sending to internal (noreply/support) users. | |
| 56b9a02e YB |
13 | * Message API has been changed to allow attachments. Message processors that can support |
| 14 | attachments can now use additional parameter as a part of $eventdata. To send attachments, | |
| 15 | $eventdata should contain properties called "attachment" (must be stored_file) and | |
| 16 | "attachname" (string). Currently, email message processor is the only one to support | |
| 17 | attachments. | |
| 3bcf6b3c | 18 | |
| d8aa5ec7 AD |
19 | === 2.2 === |
| 20 | ||
| 21 | required changes: | |
| 22 | * lib/messagelib.php message_send($eventdata) | |
| 23 | $eventdata->userto should contain a property called "emailstop", $eventdata->userto->emailstop | |
| 24 | If it is absent it will be retrieved from the user table causing an additional database query |
