MDL-63289 message: Deprecate is_user_non_contact_blocked method
[moodle.git] / message / upgrade.txt
CommitLineData
d8aa5ec7
AD
1This files describes API changes in /message/ messaging system,
2information provided here is intended especially for developers.
3
216b8947
MG
4=== 3.6 ===
5
6* The following functions have been finally deprecated and can not be used anymore:
7 * message_get_course_contexts()
8 * message_remove_url_params()
9 * message_count_messages()
10 * message_count_blocked_users()
11 * message_contact_link()
12 * message_history_link()
13 * message_shorten_message()
14 * message_get_fragment()
15 * message_get_contact_add_remove_link()
16 * message_get_contact_block_link()
17 * message_mark_messages_read()
18 * message_page_type_list()
19 * message_can_post_message()
20 * message_is_user_non_contact_blocked()
21 * message_is_user_blocked()
beeadbf7
MN
22* The following functions have been deprecated and should not be used any more:
23 - message_add_contact()
24 - message_remove_contact()
25 - message_unblock_contact()
26 - message_block_contact()
27 - message_get_contact()
28 Please see their declaration in lib/deprecatedlib.php to view their alternatives (if applicable).
c886e2c9
MN
29* The following methods have been deprecated and should not be used any more:
30 - \core_message\api::is_user_blocked()
263ad984 31 - \core_message\api::delete_conversation()
e5eba802 32 - \core_message\api::is_user_non_contact_blocked()
15663b0b
MN
33* The method \core_message\api::can_delete_conversation() now expects a 'conversationid' to be passed
34 as the second parameter.
beeadbf7 35* The following web services have been deprecated. Please do not call these any more.
fa024820
MN
36 - core_message_external::block_contacts(), please use core_message_external::block_user() instead.
37 - core_message_external::unblock_contacts(), please use core_message_external::unblock_user() instead.
38 - core_message_external::create_contacts(), please use core_message_external::create_contact_request() instead.
60b67bbc 39 - core_message_external::delete_conversation(), please use core_message_external::delete_conversations_by_id() instead.
f7dfa9ba
SA
40* The following function has been added for getting the privacy messaging preference:
41 - get_user_privacy_messaging_preference()
216b8947 42
d0d1e97a
MN
43=== 3.5 ===
44
45* Changed the database structure so there are no longer two tables for messages, with the only
46 difference being that one stores read messages. The 'message' and 'message_read' tables are
47 still present in core but will no longer be populated by core APIs. The data will be
48 transferred to the new database structure via an ad-hoc task. Please be patient. This can
49 take time.
50 The new database structure is as follows -
51 'messages' - Stores the messages with a 'useridfrom' field specifying the user who sent the
52 message and a 'conversationid' field specifying which conversation it is for.
53 'message_conversations' - The list of conversations.
54 'message_conversation_members' - The list of users in each conversation.
55 'message_user_actions' - The list of user actions against a message, eg. read/deleted.
56 'notifications' - This has a very similar structure to the old table 'message' and still
57 has a one-to-one relation between users.
58 Due to these huge differences the events message_sent, message_deleted and message_viewed
59 have changed quite a lot. Please, if you have any observers or are triggering these events
60 in your code you will have to make some changes!
61* The webservice external function 'core_message_mark_message_read' now only marks messages as
62 read, and not notifications. A new external function 'core_message_mark_notification_read' was
63 added to mark notifications as read.
64* Deprecated the following functions.
65 - message_move_userfrom_unread2read
66 - message_get_blocked_users
67 - message_get_contacts
68 - message_mark_message_read
69 - message_can_delete_message
70 - message_delete_message
71 - \core_message\api::mark_all_read_for_user
72 Please see their declaration in lib/deprecatedlib.php to view their alternatives (if applicable).
73* Final deprecation of the following functions.
74 - message_get_recent_notifications
75 - message_search
76 - message_get_history
77 - message_get_recent_conversations
78* Added new events for when a notification is sent and viewed.
6f0731ad
MN
79* Removed the database table 'message_working'. The 'message_working' table was introduced when
80 the messaging system was first introduced in Moodle, so, a long time ago. It was never necessary.
81* Replaced the usage of the table 'message_popup' to a new table 'message_popup_notifications'.
d0d1e97a 82
5b0769db
MN
83=== 3.2 ===
84
85* Removed all message_print_* functions as well as the files search.html, search_advanced.html and
86 send_form.php due to messaging UI rehaul.
87* Deprecated the following functions as they are no longer used.
88 - message_get_course_contexts
89 - message_remove_url_params
90 - message_count_messages
91 - message_count_blocked_users
92 - message_contact_link
93 - message_get_recent_notifications
94 - message_history_link
95 - message_search
96 - message_shorten_message
97 - message_get_fragment
98 - message_get_history
99 - message_get_contact_add_remove_link
100 - message_get_contact_block_link
101 - message_mark_messages_read
102 - message_page_type_list
103 - message_can_post_message
104 - message_is_user_non_contact_blocked
105 - message_is_user_blocked
106
e61a9638
MN
107=== 3.1 ===
108* get_message_processors accepts an addition parameter for testing, which will just reset processor and exit.
59a968dc 109* Deprecated method message_current_user_is_involved() has been removed.
e61a9638 110
36bbb0b7
AA
111=== 2.9 ===
112* Renderer method \core_message_renderer::manage_messagingoptions now accepts a user id parameter as well.
113
3bcf6b3c
RT
114=== 2.6 ===
115* Message processor extending message_output, should return true in can_send_to_any_users()
116 if it supports message sending to internal (noreply/support) users.
56b9a02e
YB
117* Message API has been changed to allow attachments. Message processors that can support
118 attachments can now use additional parameter as a part of $eventdata. To send attachments,
119 $eventdata should contain properties called "attachment" (must be stored_file) and
120 "attachname" (string). Currently, email message processor is the only one to support
121 attachments.
3bcf6b3c 122
d8aa5ec7
AD
123=== 2.2 ===
124
125required changes:
126* lib/messagelib.php message_send($eventdata)
127 $eventdata->userto should contain a property called "emailstop", $eventdata->userto->emailstop
128 If it is absent it will be retrieved from the user table causing an additional database query