Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Hi all,
I had a 3.4 instance of quiz, which had this problem: I'd go to a quiz, which had, say 4 questions. For some users (not all), the quiz would start with question 2 (no message explaining why), then go question 4, then back to 2, then to 1, and so on, randomly.
I successfully upgraded to 4.4 according to the instructions on the home page of the quiz module, ran the upgrade script, cleared caches, but the exact same problem persists.
I'm assuming that my database is somehow corrupted, and would appreciate any help in solving this issue.
Thanks,
Albert
Comments
Comment #1
alberto56 CreditAttribution: alberto56 commentedFor user 1, I can take the quiz several times and it always works.
For some other users, the problem always occurs.
There are users I have used for testing, where it is possible that two people using the same account have been taking the quiz at the same time. Could this have corrupted the db?
For other users, I am certain that two people were not using the same account at the same time, yet the problem occurs, even the very first time this person takes the quiz after the upgrade.
is there any way I can tell quiz module to complety erase all information related to quizzes in progress? Might that help?
I am now going to put debugging trace code to understand exactly how the quiz_take_quiz() function determines which question to display.
Comment #2
alberto56 CreditAttribution: alberto56 commentedHmm, this is interesting. This seems to have solved the problem for me (for now?):
- go to a quiz and confirm the problem exists
- go to admin/settings/performance, disable page compression
- go to the same quiz, the problem no longer exists
- and this is the interesting part: go back to admin/settings/performace, and re-enable page compression, now it works.
Comment #3
djdevinThis issue is being closed because it is filed against a version that is no longer supported.
Comment #4
djdevinThis issue is being closed because it is filed against a version that is no longer supported.