moodle/message/upgrade.txt

50 lines
2.0 KiB
Plaintext
Raw Normal View History

This files describes API changes in /message/ messaging system,
information provided here is intended especially for developers.
=== 3.2 ===
* Removed all message_print_* functions as well as the files search.html, search_advanced.html and
send_form.php due to messaging UI rehaul.
* Deprecated the following functions as they are no longer used.
- message_get_course_contexts
- message_remove_url_params
- message_count_messages
- message_count_blocked_users
- message_contact_link
- message_get_recent_notifications
- message_history_link
- message_search
- message_shorten_message
- message_get_fragment
- message_get_history
- message_get_contact_add_remove_link
- message_get_contact_block_link
- message_mark_messages_read
- message_page_type_list
- message_can_post_message
- message_is_user_non_contact_blocked
- message_is_user_blocked
=== 3.1 ===
* get_message_processors accepts an addition parameter for testing, which will just reset processor and exit.
* Deprecated method message_current_user_is_involved() has been removed.
=== 2.9 ===
* Renderer method \core_message_renderer::manage_messagingoptions now accepts a user id parameter as well.
=== 2.6 ===
* Message processor extending message_output, should return true in can_send_to_any_users()
if it supports message sending to internal (noreply/support) users.
* Message API has been changed to allow attachments. Message processors that can support
attachments can now use additional parameter as a part of $eventdata. To send attachments,
$eventdata should contain properties called "attachment" (must be stored_file) and
"attachname" (string). Currently, email message processor is the only one to support
attachments.
=== 2.2 ===
required changes:
* lib/messagelib.php message_send($eventdata)
$eventdata->userto should contain a property called "emailstop", $eventdata->userto->emailstop
If it is absent it will be retrieved from the user table causing an additional database query