ATutor

Learning Management Tools







Pages:1 2 3 4 5 6 7 8 9 10 11 12 13 14 15


Tests fail to submit after long inactivity


  • 2012-03-09 13:51:37

    Tests fail to submit after long inactivity

    Hi. I have 2.0 installed and one thing I've observed an issue with tests. If a student begins a test, then steps away for it for a long period, then comes back and submits it, the result isn't logged.

    Most likely this happens due to being logged out due to inactivity. However, for the unaware student, they feel like they've completed it.

    Any thoughts here?

    Thanks.

  • 2012-03-09 14:39:29

    Re: Tests fail to submit after long inactivity

    There have been a few reports of this problem. We do need a popup warning of some sort to warn users that a session is about to expire, and give them the opportunity to extend the session. It would be a nice feature for community based project. Hint ;-)

    This time length is generally set as a security feature, so if a student walks away while still logged in, at a public workstation in particular, someone is less likely to be able to sit down and access that student's information. The timeout however, is problematic at other times, like test, and when writing long forum messages, or writing content etc.

    For now you can reset the timeout to a longer period than the 15 minutes its currently set at. See the value for the $expiry variable in the include/vitals.inc.php file.

  • 2012-03-16 00:22:49

    Re: Tests fail to submit after long inactivity

    Thanks for the reply Greg. What about a message that pops up when a user clicks to take a test saying something like, "You will be logged out after [time in the $expiry variable]. Please complete this test before then."

    That might be a short term fix. Although, if a user is entering answers, does that reset the timeout?

  • 2012-03-19 09:55:35

    Re: Tests fail to submit after long inactivity

    That might work for now, and would be fairly easy to add for your purpose. We'd hold off until a proper warning utility is created to add such a feature to the core code.


    Perhaps another approach for now could be to present questions one at a time. It would be less likely then that a test taking would be perceived as inactive.