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
This is the expected functionality when an assignment doesn't exist to the user: either it doesn't actually exist or they don't have access to it. (lines 5-20 in publishes.js determines what each user can see.)
The interesting thing is that this doesn't happen when you refresh a /edit subpage that only admins can access. The difference between the assignment route handler and the edit handler seems to be that the edit handler checks that the user is an admin first before trying to get the assignment.
I have a feeling this is a problem with publishes.js. This StackOverflow question seems to apply, but I might ask one that's more specific to our circumstance to get a more applicable answer.
The text was updated successfully, but these errors were encountered:
This is the expected functionality when an assignment doesn't exist to the user: either it doesn't actually exist or they don't have access to it. (lines 5-20 in
publishes.js
determines what each user can see.)The interesting thing is that this doesn't happen when you refresh a
/edit
subpage that only admins can access. The difference between theassignment
route handler and theedit
handler seems to be that theedit
handler checks that the user is an admin first before trying to get the assignment.I have a feeling this is a problem with
publishes.js
. This StackOverflow question seems to apply, but I might ask one that's more specific to our circumstance to get a more applicable answer.The text was updated successfully, but these errors were encountered: