Quiz problem after upgrade from 2.0.4 ->2.1.1

Quiz problem after upgrade from 2.0.4 ->2.1.1

by Stephen Hooley -
Number of replies: 2

Hi

I have recently upgraded a Moodle system to 2.1.1 and am having problems when testing the quiz module on some but not all of my quizzes.

The problem occurs when a user completes a quiz and presses 'next' or 'Finish attempt ...'.

The user is then directed to log in and then presented with the following error:

A required parameter (attempt) was missing

More information about this error

 
Clicking continue just takes the user back to the quiz with none of the answers selected and the user is then caught in a persistent loop of logging back in, error, quiz.
 
The attempt creates an attempt instance on the quiz_attempts table and if the user returns to the course page and tries the quiz again the quiz is listed as in progress but the problems occur again if the attempt is continued.
 
Any ideas appreciated? Like I said this only occurs on some quizzes
 
Steve
 
 
Average of ratings: -
In reply to Stephen Hooley

Re: Quiz problem after upgrade from 2.0.4 ->2.1.1

by Stephen Hooley -

Further to above

When I turn on debugging and try and reattempt the quiz the following error is highlighted:

Error: Could not insert a new entry to the Moodle log

  • line 1693 of /lib/datalib.php: call to debugging()
  • line 87 of /mod/quiz/attempt.php: call to add_to_log()

 

...and when when forced to log back in:

A required parameter (attempt) was missing

More information about this error

Stack trace:
  • line 429 of /lib/setuplib.php: moodle_exception thrown
  • line 468 of /lib/moodlelib.php: call to print_error()
  • line 40 of /mod/quiz/processattempt.php: call to required_param()

 

 

Average of ratings: -
In reply to Stephen Hooley

Re: Quiz problem after upgrade from 2.0.4 ->2.1.1

by Stephen Hooley -

I think what is happening is when the quiz attempt is completed the fact that the user is being forced to log in again is loosing the attemptid parameter which then caused the error above.

Can anyone think why when pressing 'next' or 'finish attempt...' the user is being forced to log in?

Average of ratings: -