mahara-contributors team mailing list archive

[Mahara Bot <1837194@xxxxxxxxxxxxxxxxxx>]

Reviewed:  https://reviews.mahara.org/10246
Committed: https://git.mahara.org/mahara/mahara/commit/ab0a0975896c3b6135356bab0a08508e40a6d8be
Submitter: Robert Lyon (robertl@xxxxxxxxxxxxxxx)
Branch:    master

commit ab0a0975896c3b6135356bab0a08508e40a6d8be
Author: Peter Spicer <peter.spicer@xxxxxxxxxxxxxxx>
Date:   Tue Aug 6 18:28:52 2019 +0100

Bug 1837194: Allow going directly to a message from a URL

For normal messages, going to the inbox and unhiding a message is fine,
but if the message is one that will have been synced to an LMS, the user
is quite likely to come from the LMS via a direct link to the message itself.

This allows us to expand a message - albeit on the proviso that it is on
the first page of results, though this is a scenario that never came up in
a year of user testing.

I did include a Behat test, though I had to write a new step to cover the
specifics of 'going directly to a message'.

Change-Id: I0e68fcc37f1ed453b6c43ce939d8c2a3a60b292e

-- 
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/1837194

Title:
  Adding notifications hooks for plugins

Status in Mahara:
  Fix Committed

Bug description:
  At Moodlemoot UK 2019, I demoed a piece of work we'd done for QMUL to
  better integrate their Moodle and Mahara -
  https://www.youtube.com/watch?v=Ixy4Ah9webQ for the presentation - and
  said I'd talk to the Mahara team about getting it into core so I could
  then release the rest of it as plugins.

  Essentially we made a few core hacks to 18.04 to support some
  additional behaviours around notifications sent to a user:

  * ability to add extra parameters in the inbox URL to open a specific message
  * call out to plugin functions if defined when a new notification is issued
  * call out to plugin functions if defined when a notification is read
  * call out to plugin functions if defined when a notification is deleted

  These hook points would allow a plugin to optionally do something with
  these notifications, such as sending the notifications out to a Moodle
  webservice, or updating the Moodle when a notification is read in
  Mahara, and with a view to being as efficient as possible to avoid
  affecting those who don't have the integration set up.

  I'll review the patches ASAP that I did for 18.04 to see what needs
  changing for 19.10 but I'd appreciate it if we could look at getting
  them in for that release and adding Behat tests for the first item, I
  don't think I can do anything for the others.

  The functionality I'm looking at adding is explicitly giving options
  to plugin authors, not changing core Mahara behaviour in case that's a
  concern.

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