View source for Developer Area/Core Subsystems/Notifications

Mahara has a notifications framework for getting messages to users through a variety of means.

<div class="wikitext">

Notification types are plugins, currently there exists three:

Internal - all activity shows up in the user's 'recent activity' page Email - user gets an email per notification Emaildigest - user gets an email each day with a summary of all notifications.

For each type of activity (discussed later), the user can direct it to one of these different plugins.

Notifications will always go to the activity log, but if a different notification plugin has been selected, they will go there marked as read.

For all the types of activity, you need to call activity_occured and pass it the activity type (described below) and an array (or stdclass object) of information. Each activity type expects different information.

The different types of activity are:

<div id="section_1">

===watchlist (artefact)===

Activity that occurs on an artefact (edit)

Will notify any users who are monitoring that artefact or any artefacts that have this artefact as a child.

Requires $data-&gt;artefact (id of artefact) and should have $data-&gt;subject

</div><div id="section_2">

===watchlist (view)===

Any new items added to the view, or the view name/description etc changed.

Will notify any users who are monitoring the view.

Requires $data-&gt;view (id of view) and $data-&gt;subject (eg 'artefact was added')

</div><div id="section_3">

===watchlist (community)===

Unclear what activity on a community is so far.

Will notify any users who are monitoring the community.

Requires $data-&gt;community (id of community) and $data-&gt;subject (eg 'user was added etc)

</div><div id="section_4">

===maharamessage===

System message. Will notify all users the message is sent to.

Requires $data-&gt;message and $data-&gt;subject (contents of message) and $data-&gt;users (array of user ids)

</div><div id="section_5">

===usermessage===

Message from one user to another. Will notify the user the message is sent to.

Requires $data-&gt;message and $data-&gt;subject(contents of message), $data-&gt;userto (id of user message is sent to), $data-&gt;userfrom (id of user message is sent from)

</div><div id="section_6">

===feedback (artefact)===

Feedback on an artefact. Will notify the artefact owner.

Requires $data-&gt;artefact (id of artefact) and $data-&gt;view (id of view) and $data-&gt;subject and $data-&gt;feedback (contents of feedback)

</div><div id="section_7">

===feedback (view)===

Feedback on a view. Will notify the view owner.

Requires $data-&gt;view (id of view) and $data-&gt;subject and $data-&gt;feedback (contents of feedback)

</div><div id="section_8">

===newview===

A new view is created. Will notify any users who have access to this view (through friends list, user list or group list (view permissions))

Requires $data-&gt;view (id of new view) and $data-&gt;owner (id of user owning new view)

</div><div id="section_9">

===viewaccess===

View access has changed. Will notify any users who have access to this view (through the same 3 ways as newview), and who AREN'T in the list of oldusers passed in

Requires the same two args as newview and $data-&gt;oldusers (as calling activity_get_viewaccess_users($view, $owner); will return)

</div><div id="section_10">

===contactus===

The Contact Us form is filled out. Will notify all admin users subscribed (as per <span class="wikiunknown"><u>AdminNotifications</u>[http://old.eduforge.org/wiki/wiki/mahara/wiki?pagename=AdminNotifications&action=create ?]</span>.

Requires $data-&gt;subject, $data-&gt;message, $data-&gt;userfrom (if loggedin), $data-&gt;fromname, $data-&gt;fromemail

</div><div id="section_11">

===TODO: other admin messages===

</div></div>