Deleting a group with collections submission does not really release them

Bug #1642389 reported by Melvin Romero on 2016-11-16
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Cecilia Vela Gurovic
Mahara user manual

Bug Description

I've tested this in Mahara 15.04, in 16.04 and the latest one (Nightly).

Here is a description of the bug and how to reproduce it:

1. I have a group with collections that have been submitted for assessment.
2. I delete that group without releasing the collections.
3. When I go back and check with each users that had submitted a collection, I can see that my collection is still considered submitted... in a deleted group (cannot access that group anymore, normal, but the link remains indefinitely).
4.As the same user, I can still modify the pages of my collection without problems. The BIG problem comes when I wish to submit that collection again in another group. I can't because the system still thinks that it has been submitted in the deleted group. it gives an error message (access denied type of error).

This is a big problem for our institution because we ask our teachers to delete their groups when they don't use them anymore. Some of them still have collections submitted for evaluation and the teachers sometimes don't bother checking before. Note that this problem only affects collections and not pages.

I don't if anyone else came across this behavior... Thanks for you help as always :)


Melvin Romero (melrom49) wrote :
Melvin Romero (melrom49) on 2016-11-16
description: updated
Robert Lyon (robertl-9) on 2016-11-16
Changed in mahara:
assignee: nobody → Cecilia Vela Gurovic (ceciliavg)
milestone: none → 17.04.0
status: New → Confirmed
importance: Undecided → High
Robert Lyon (robertl-9) wrote :

Hi Melvin,

I can replicate this issue so will assign Cecilia to fix it. We should have a fix soon.

I note when a user submits a collection to a group, their portfolio 'Pages' list as well as their portfolio 'Collections' list show the pages/collection as submitted.

On deletion of the group the pages are shown as not submitted but the collection itself is still submitted. So the way we record how a collection is submitted is not removed on deletion of the group.



Changed in mahara:
status: Confirmed → In Progress

Hi Melvin,

It would be great if you applied the patch from and tested it so we know that it works for you.


Submitter: Robert Lyon (<email address hidden>)
Branch: master

commit fd3b307d9b84f9857038c3ff90c5d6c6c0169b23
Author: Cecilia Vela Gurovic <email address hidden>
Date: Tue Nov 22 12:33:07 2016 +1300

Bug 1642389: Release collection when deleting group

When a collection is submitted to a group and then
the group is deleted, then the collections are


Change-Id: I7e242e5992d8abdafd5aa7b989fba65aa3928b37

Robert Lyon (robertl-9) on 2016-12-13
Changed in mahara:
status: In Progress → Fix Committed
tags: added: usermanualupdate
Changed in mahara-manual:
status: New → Confirmed
milestone: none → 17.04.1
importance: Undecided → Medium
Changed in mahara-manual:
status: Confirmed → Fix Released
Robert Lyon (robertl-9) on 2017-04-27
Changed in mahara:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers