Removing a roster by Site Info's Edit Class Roster does not remove the section from Sections tool.
Description
Attachments
relates to
Activity
Mathieu Plourde November 5, 2010 at 2:42 PM
We have experienced some mismatch between Site Info/Section Info/Roster at Delaware on 2.6.1. This patch might help.
UD Jira reference: UDSAKAI-152
Zhen Qian July 19, 2010 at 10:40 AM
r79645.
Michael, could you please test whether this fixes the problem you reported?
Seth Theriault July 15, 2010 at 7:42 AM
Guessing at some real affects version.
Zhen, can you take another look at this? It is under consideration for 2.7.1 and 2.6.3
Michael Wenk February 8, 2010 at 1:16 PM
patch attached was made on current trunk. It is not exactly what I tested locally in our sakai instance, but it should be close enough.
Michael Wenk February 2, 2010 at 9:58 AM
Zhen:
The problem is if the group is a CM created group. If you delete the authz group w/o deleting the site group, you get the ghost problem. Also the original code was deleting all authz groups for the site. This was causing a ghost group for every section remaining(not just the group that was deleted)
I don't think we want to delete every authz/site group whenever a change is done(there could be info such as TA assignments that would be lost)
So the answer to the question is no, adding realm.del doesn't fix the problem, it actually causes the issue. Unfortunately we have realm.del on !site.helper for Instructor, so its not going to fly.
My solution is two fold, fix the if statement to only delete the authz group if the group has been requested to be deleted, and delete the site group at the same time that the authz group is deleted.
What do you think of that?
Mike
if a user drops a roster in site info the realm gets removed but not the corresponding data in SAKAI_GROUP. If the roster gets re-added then a second row gets added to sakai_group. This data is revealed to the user in section info and results in duplicate sections being displayed....one of which is useless.