Access Denied Error for Admin account on Test Results

I'm also having the same issue with my administration account not being able to see the userresult data... "access denied." Please help.

subscribing!

#3 is correct. Changing line 2279 of the module from...

'!url' => url('user/quiz/' . $rid . '/userresults', array('absolute' => TRUE)),

to...

'!url' => url('node/' . $quiz->nid . '/results/' . $rid, array('absolute' => TRUE)),

fixes the problem.

I had the same problem and changing line 2279 from the quiz.module fixed the problem.

I also had the problem when you go on "My account -> My results" and click on the results. In order to fix the problem, you can also change line 307 from the quiz.pages.inc file from :

'title' => l($result['title'], 'user/quiz/'. $result['result_id'] .'/userresults'),

to

'title' => l($result['title'], 'node/' . $result['nid'] . '/results/'. $result['result_id']),

It's great to notice that this overcomes the problem. Is this going to be implemented in the core of quiz6.x-4?

IMO this is a bug that has a major priority, since seeing the individual results (answers to questions in a quiz) is a very important issue for this module. If there is any help needed about reproducing the bug, let me know :)

Can anyone provide me some directions how to apply these changes without hacking the core module?

Thanks in advance :)

I have the same issue in D7 in a live site, is #3 the same in D7 case?
Thanks!

@Rosamunda - Yes but it's line 2538 in 7.x-4.0-beta1. Just search for the line:
'!url' => url('user/quiz/' . $rid . '/userresults', array('absolute' => TRUE)),

RE #8 -- and do what to that line? It's completely unclear how to modify that line to get rid of the Access Denied error when administrative users navigate to /user/quiz/xx/userresults.

Drupal 7, Quiz 7.x-4.0-beta2.

The error discussed in #3 is addressed by the code change shown in #4. In earlier versions of the module it appeared on line 2279. In version 4.0-beta-1 it appears on line 2538, but the same code change applies. I don't know about beta-2, but try searching for the string.

Thank you As If, that is exactly what I needed to know. Thanks for the help.

Moving to 7.x-4.0-beta2.

Let's try to get the underlying problem fixed before 7.x-4.0 leaves beta.

I don't think changing the url is the solution, but just a workaround that bypasses the underlying problem.