A few lecturers (including me) have had problems where strange things have happened when setting up or testing quizzes. These all seem to occur when they have two or more active logins to the same account. (For example, one lecturer had multiple tabs open - one to look through an old quiz, and one to write questions for a new quiz.) Other people have been logged in across two devices.
Common symptoms include an empty dashboard with "Oops, something went wrong in...", failure to save new quizzes, creation of duplicate quizzes.
Longer term, we should review how we handle multiple concurrent logins to a single account. Either by closing all other session when a login occurs (not sure how that would work across multiple tabs in a single browser), or by making the system robust to potential issues and conflicts. Or even just changing the 'Oops...' text to something that looks nicer and says 'An error occurred. Please log out and back in again.'
Just for discussion re best approach for now. Telling people to log out and back in again solves all problems, so it's not critical.
A few lecturers (including me) have had problems where strange things have happened when setting up or testing quizzes. These all seem to occur when they have two or more active logins to the same account. (For example, one lecturer had multiple tabs open - one to look through an old quiz, and one to write questions for a new quiz.) Other people have been logged in across two devices.
Common symptoms include an empty dashboard with "Oops, something went wrong in...", failure to save new quizzes, creation of duplicate quizzes.
Longer term, we should review how we handle multiple concurrent logins to a single account. Either by closing all other session when a login occurs (not sure how that would work across multiple tabs in a single browser), or by making the system robust to potential issues and conflicts. Or even just changing the 'Oops...' text to something that looks nicer and says 'An error occurred. Please log out and back in again.'
Just for discussion re best approach for now. Telling people to log out and back in again solves all problems, so it's not critical.