Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Delete Validation Needed For Learner Groups #829

Closed
dartajax opened this issue Jun 10, 2015 · 4 comments
Closed

Delete Validation Needed For Learner Groups #829

dartajax opened this issue Jun 10, 2015 · 4 comments

Comments

@dartajax
Copy link
Member

Currently, any learner group can be deleted after clicking Yes as shown below ...

delete

Once Yes is clicked, any associations with curricular events for that learner group are removed resulting in session offerings being removed from student calendars. I saved the code @thecoolestguy and I worked on last week when this happened and can make a stored procedure to bring this data back once one or more students groups are deleted by accident; but I figured it is better to put the wheels in motion to prevent this from occurring ever in the future by using one of the two methods listed below ....

a. Allowing the Delete to take place but only after validating that nothing is attached to this student group anywhere in the database (published or not)

or ...

b. Disallowing all delete functionality of student groups. Just lock them down and make it a special request for us to handle.

@jrjohnson
Copy link
Member

@dartajax - this seems like a frontened issue non? I think the UI should provide that confirmation (and may already do so). Please create there, or reopen here if I'm wrong.

@dartajax
Copy link
Member Author

dartajax commented Aug 5, 2015

The interface provides a message and the message contains more information than before (the number of sessions offerings etc.); but I just thought we should never allow a learner group to be deleted if it is attached to published courses and sessions. I still believe that. Can we address this someday?

@dartajax
Copy link
Member Author

dartajax commented Aug 5, 2015

I will close this ticket and recreate it in frontend.

@dartajax
Copy link
Member Author

dartajax commented Aug 5, 2015

... except that it's already closed = oops.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants