Deleting a group with collections submission does not really release them
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Mahara |
Fix Released
|
High
|
Cecilia Vela Gurovic | ||
Mahara manual |
Fix Released
|
Medium
|
Unassigned |
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
description: | updated |
Changed in mahara: | |
assignee: | nobody → Cecilia Vela Gurovic (ceciliavg) |
milestone: | none → 17.04.0 |
status: | New → Confirmed |
importance: | Undecided → High |
Changed in mahara: | |
status: | Confirmed → In Progress |
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 |
Changed in mahara: | |
status: | Fix Committed → Fix Released |
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.
Cheers
Robert