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
It appears that sometimes when new students login and enroll in a course, but then the course would disappear from the dropdown in the main navigation menu (there would be no courses in their dropdown nav list). This does not affect all users, and apparently logging out and back in clears the problem. It may be load-related (if many people are signing up at the same time)?
The text was updated successfully, but these errors were encountered:
Clarification: this behavior was caused by (a) students logging in, then (b) an instructor enrolling the student in a course offering. However, the home page did not show the student's new enrollment information--it appeared to the student that they were not enrolled in any course. Logging out and back in fixed the issue, which was apparently due to stale relationship info fetched into the student's session (i.e., the student's enrollment relationship wasn't refetched when visiting the home page).
Perhaps forcing a refetch of the user's enrollment relationship on page load on the home page would fix the problem? If proposed changes to the main menu are implemented, this would be the primary place where users would select different course offerings, and so is the main place where this refetch would be needed.
I was unable to replicate this since I can't find a way to be logged in as a student and an instructor at the same time in development.
Is this still an issue with the current state of the drop-down menu?
It appears that sometimes when new students login and enroll in a course, but then the course would disappear from the dropdown in the main navigation menu (there would be no courses in their dropdown nav list). This does not affect all users, and apparently logging out and back in clears the problem. It may be load-related (if many people are signing up at the same time)?
The text was updated successfully, but these errors were encountered: