1 This files describes API changes in /message/ messaging system,
2 information provided here is intended especially for developers.
6 * Removed all message_print_* functions as well as the files search.html, search_advanced.html and
7 send_form.php due to messaging UI rehaul.
8 * Deprecated the following functions as they are no longer used.
9 - message_get_course_contexts
10 - message_remove_url_params
11 - message_count_messages
12 - message_count_blocked_users
13 - message_contact_link
14 - message_get_recent_notifications
15 - message_history_link
17 - message_shorten_message
18 - message_get_fragment
20 - message_get_contact_add_remove_link
21 - message_get_contact_block_link
22 - message_mark_messages_read
23 - message_page_type_list
24 - message_can_post_message
25 - message_is_user_non_contact_blocked
26 - message_is_user_blocked
29 * get_message_processors accepts an addition parameter for testing, which will just reset processor and exit.
30 * Deprecated method message_current_user_is_involved() has been removed.
33 * Renderer method \core_message_renderer::manage_messagingoptions now accepts a user id parameter as well.
36 * Message processor extending message_output, should return true in can_send_to_any_users()
37 if it supports message sending to internal (noreply/support) users.
38 * Message API has been changed to allow attachments. Message processors that can support
39 attachments can now use additional parameter as a part of $eventdata. To send attachments,
40 $eventdata should contain properties called "attachment" (must be stored_file) and
41 "attachname" (string). Currently, email message processor is the only one to support
47 * lib/messagelib.php message_send($eventdata)
48 $eventdata->userto should contain a property called "emailstop", $eventdata->userto->emailstop
49 If it is absent it will be retrieved from the user table causing an additional database query