Reviewed:  https://reviews.mahara.org/11505
Committed: 
https://git.mahara.org/mahara/mahara/commit/214c899aa47cc4fd8ab20e6e80f44e083df6a081
Submitter: Lisa Seeto ([email protected])
Branch:    master

commit 214c899aa47cc4fd8ab20e6e80f44e083df6a081
Author: Robert Lyon <[email protected]>
Date:   Mon Dec 21 09:51:54 2020 +1300

Bug 1908837: Setting $releaseuser correctly

When archiving a collection

Change-Id: I4c978de93e04dcdedc328f5d31f8dc13d9208159
Signed-off-by: Robert Lyon <[email protected]>

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

Title:
  Trying to get property of non-object in
  module/assessmentreport/lib.php line 60

Status in Mahara:
  Fix Committed
Status in Mahara 19.10 series:
  Confirmed
Status in Mahara 20.04 series:
  Confirmed
Status in Mahara 20.10 series:
  Confirmed
Status in Mahara 21.04 series:
  Fix Committed

Bug description:
  When releasing a collection and the assessment report is enabled there
  is an error with the $releaseuser

  It is given as a string instead of an object

  To test:

  1) Have a group that accepts submission and has submission archiving turned on
  2) As a group member submit a collection to the group
  3) As group admin release the collection
  4) Run the cron from command line:  sudo -u www-data php htdocs/lib/cron.php

  You should see an error similar to 
  [WAR] a2 (module/assessmentreport/lib.php:60) Trying to get property 'id' of 
non-object

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

_______________________________________________
Mailing list: https://launchpad.net/~mahara-contributors
Post to     : [email protected]
Unsubscribe : https://launchpad.net/~mahara-contributors
More help   : https://help.launchpad.net/ListHelp

Reply via email to