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
After #48 is complete, a user should be able to leave a collection in much the same way (update to use our new modified REST stuff). There might also be some sort of authorization issues here, because the user who is trying to modify the "Collection" object is not the admin. For now just hack this together.
The text was updated successfully, but these errors were encountered:
So just to elaborate on this, for the sake of my own organization:
The basic problem is that collections model instances can only be edited by administrators of said collection instance.
A user leaving a collection (on the model layer) is semantically equivalent to editing the collection's 'users' field attribute, which is thus disallowed by the above rule.
A fix should involve some sort of conditional check to allow non-administrators to edit only the user's field of a collection.
After #48 is complete, a user should be able to leave a collection in much the same way (update to use our new modified REST stuff). There might also be some sort of authorization issues here, because the user who is trying to modify the "Collection" object is not the admin. For now just hack this together.
The text was updated successfully, but these errors were encountered: