mahara-contributors team mailing list archive

[Robert Lyon <robertl@xxxxxxxxxxxxxxx>]

Ah actually the triggers are working as expected (I just didn't switch
notifications to inbox)

What the problem turns out to be is the inbox block on dashboard loads
via ajax from 15.10 onwards so that the javascript meant to wire up the
'markasread' javascript functions are not connected.

Needed to fire off the 'pageupdated' trigger once the block had loaded
so it could wire up the needed functions.

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

Title:
  Read messages are not getting set to read

Status in Mahara:
  In Progress

Bug description:
  Mahara: 15.10.1
  DB: MySql
  OS: Linux
  Browser: Chrome and FF

  Since the 15.10 upgrade, the 'read' message counter is not working
  properly.

  It doesn't appear that the triggers are updating the usr.read field.

  * I've tried with both multi recipient module on and off.

  * I manually reset all usr.read = 0 in the DB (just to start with a
  clean slate)

  * sent messages to a different user

  * logged in as the other user and their counter hadn't increased.

  I then went into the user's inbox and clicked on the message (i.e. to
  read it), the usr.read field never got updated. Neither did the
  module_multirecipient_userrelation.read get updated (or
  notification_internal_activity.read when mutil-recipient is off).

  Using Chrome's developer tools, I can see that there is no network activity to the server to update the field as read:
  * either when I click on the message
  * or when I select 'Mark as read' from the bulk action with the message selected.

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