mahara-contributors team mailing list archive

[Mahara Bot <1246702@xxxxxxxxxxxxxxxxxx>]

Reviewed:  https://reviews.mahara.org/2686
Committed: http://gitorious.org/mahara/mahara/commit/b7606a0a85754e0c635a62d8505a5de297d01a28
Submitter: Ghada El-Zoghbi (ghada@xxxxxxxxxxxxxxx)
Branch:    master

commit b7606a0a85754e0c635a62d8505a5de297d01a28
Author: Tobias Zeuch <tobias.zeuch@xxxxxxxxxxxxxxxxxx>
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 <tobias.zeuch@xxxxxxxxxxxxxxxxxx>

-- 
You received this bug notification because you are a member of Mahara
Contributors, which is subscribed to Mahara.
Matching subscriptions: Subscription for all Mahara Contributors -- please ask on #mahara-dev or mahara.org forum before editing or unsubscribing it!
https://bugs.launchpad.net/bugs/1246702

Title:
  Notification to more than one recipient

Status in Mahara ePortfolio:
  Confirmed

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/mahara/+bug/1246702/+subscriptions