mahara-contributors team mailing list archive

[Robert Lyon <robertl@xxxxxxxxxxxxxxx>]

Public bug reported:

When handle_activity() is processing a viewaccess change it uses
activity_get_viewaccess_users() to see who is affected by the change.

Part of the sql check is to check the view_access table to see what
users are involved.

But the view_access option of 'loggedin' doesn't set any ids in the usr
column. This means if I set a page from no access to logged in users no-
one is notified of this change.

I'm not sure if we are wanting all logged in users to be notified or
just have a disclaimer somewhere stating that choosing logged in users
will not notify everyone of the change.

** Affects: mahara
     Importance: Undecided
         Status: New

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

Title:
  activity_get_viewaccess_users() doesn't always return users

Status in Mahara ePortfolio:
  New

Bug description:
  When handle_activity() is processing a viewaccess change it uses
  activity_get_viewaccess_users() to see who is affected by the change.

  Part of the sql check is to check the view_access table to see what
  users are involved.

  But the view_access option of 'loggedin' doesn't set any ids in the
  usr column. This means if I set a page from no access to logged in
  users no-one is notified of this change.

  I'm not sure if we are wanting all logged in users to be notified or
  just have a disclaimer somewhere stating that choosing logged in users
  will not notify everyone of the change.

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