mahara-contributors team mailing list archive

[Melvin Romero <melvin.romero@xxxxxxxxxxxx>]

Public bug reported:

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. Students then come to
complain that they can't submit their collections anymore because of
this bug. A workaround would be to ask the student to make a copie of
their collections if this happens again.

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

Melvin

** Affects: mahara
     Importance: Undecided
         Status: New

** Attachment added: "In french, sorry"
   https://bugs.launchpad.net/bugs/1642389/+attachment/4778316/+files/Collection_bogue.png

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

Title:
  Deleting a group with collections submission does not really release
  them

Status in Mahara:
  New

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. Students then come to
  complain that they can't submit their collections anymore because of
  this bug. A workaround would be to ask the student to make a copie of
  their collections if this happens again.

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

  Melvin

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