Notification to more than one recipient

Bug #1246702 reported by Tobias Zeuch on 2013-10-31
This bug affects 1 person
Affects Status Importance Assigned to Milestone

Bug Description

The current notification system stores the complete message with all meta-data in a single entry in a single table. When the recipient deletes the notification, the message-entry is deleted in the same moment. That has some disadvantages:
When a notification is deleted that was part of a conversation, the conversation thread is cut at the message.
When you try to implement an outbox without touching the notification-system, the user cannot delete messages from the outbox. But when the reciever deletes the message, it disappears from the outbox as well.

The idea is to store the message in a separate table from the user relation. This way, the message can be easily extended to reach several users. Storing the Deleted-Information in the second table, the message remain in the database until all participants have deleted it, thus preserving the metadata, from whom and to whom it was sent.

We startet implement such a message system as a plugin that blends in with the former notification system. The bug report serves as reference for gerrit

description: updated
Changed in mahara:
importance: Undecided → Wishlist
status: New → Confirmed
summary: - wishlist: Notifictation to more than one recipient
+ Notification to more than one recipient
Tobias Zeuch (tobias-zeuch-8) wrote :

Anyone willing to have a look at this? I did a rebase, would love to advance with the patch.

Submitter: Ghada El-Zoghbi (<email address hidden>)
Branch: master

commit b7606a0a85754e0c635a62d8505a5de297d01a28
Author: Tobias Zeuch <email address hidden>
Date: Thu Oct 31 13:41:48 2013 +0100

New plugin as user-message system to multiple recipients

Bug 1246702: This is a plugin that replaces the current user notifications with a
message system for multiple recipients.

- The plugin redirects calls to sendmessage.php and inbox.php.
- New Usermessages are stored in a separate table from the userrelation, where there
is also kept track of whether the notification has been read or deleted.
- Messages aren't deleted from the database, until all participantas (sender and all
recievers) delete it.
- The plugin comes with an outbox that shows messages that have been sent by the
logged in user.
- Both inbox and outbox show new messages and old messages alike.

Note that the code is at pre-release state:
The message-count per user is kept up to date with database-triggers, as is done for
the old system.
For this new system, you might not want to install it on a productive system or it
might mess up your message count when you deactivate the plugin.

Change-Id: I586af86266b5fb0e2d676bd1401b7d879d0122ef
Signed-off-by: Tobias Zeuch <email address hidden>

Changed in mahara:
milestone: none → 1.10.0
status: Confirmed → Fix Committed
tags: added: nominatedfeature

for the manual: You can only search for people when you typed their entire first name. Still need to test if regular users can only see display name or other parts of the name.

Tobias Zeuch (tobias-zeuch-8) wrote :

The plugin uses the built in user search functionality. Can you check if you have the "Exact user search" turned on under "Plugin administration" - search: internal?

Submitter: Robert Lyon (<email address hidden>)
Branch: master

commit 05c7dc69329e9cecde306d17376a463e98010b9f
Author: Aaron Wells <email address hidden>
Date: Thu Sep 25 13:51:10 2014 +1200

Install the multirecipientnotification artefact by default

Bug 1246702

Change-Id: I5fcc98779c0a496b64273ebbc7f8f7312d91bfcc

Aaron Wells (u-aaronw) on 2014-10-21
Changed in mahara:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers