You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For instance, in Active Members list of All Platforms activity in dashboard, a user kojistudent has been deleted from the CLA toolkit, but it is listed in it. When the name is clicked, an error page is shown.
Not sure users are likely to be deleted in usual operation...
Anyway, either deleted users should not be listed in the list or back-end process should check the existence of users so an error won't occur.
The text was updated successfully, but these errors were encountered:
It looks like a lot of the models refer to users using their username instead of allowing the Django ORM to take care of relations. I think that all code where the username is being used should be refactored to use the ORM as it would automatically take care of this and make for much more maintainable code
For instance, in Active Members list of All Platforms activity in dashboard, a user kojistudent has been deleted from the CLA toolkit, but it is listed in it. When the name is clicked, an error page is shown.
Not sure users are likely to be deleted in usual operation...
Anyway, either deleted users should not be listed in the list or back-end process should check the existence of users so an error won't occur.
The text was updated successfully, but these errors were encountered: