Test Results Submission Difference in Version 11
April 13, 2013 12:00 AM
I've done 2 tests in Lectora (I'm kinda new).
The test created in Lectora Inspire - when I get to the last page - under the Done button is a variable that OnMClkProcTestSurv, Target is not selected and under the Test Results is Custom Results, Custom Script, Settings (processresults.aspx) - Post.
When I upgraded to Lectora Version 11 - under the Done button - same variable and Test Results options.
However - the variable in Ver 11 does not have the option to not selected - it defaults to the name of the test.
The Inspire version works. Ver 11 does not. I need it to be not selected. Is this a bug or is there a workaround?
I'm stressing because my customer is stressing.
Discussion (6)
TX Lady,
I had the same problem in building an eLearning I'm working on. All I did to make it not selected, was to find that action in an old eLearning I did and cut an pasted it into the new one. It took it. Sounds simplistic....but it worked!
Would you mind sending a screenshot of this in Lectora 11 to support@trivantis.com? I'd like to make sure we research and address this.
Thanks for your help.
- Laura
I did yesterday and someone got back with me. He remoted in. The fix was to publish as SCORM. But now I have API error issues.
I'd prefer to publish as HTML as we have our own server and LMS system that tracks students cradle to grave so to speak. It makes no sense that the DONE button won't submit the results to processresults.aspx when the file is sitting in the same folder as the test. I think the option to have not selected is the issue.
I'm really frustrated here and I have an unhappy customer.
I went back and copied the variable from the original test that works right into the new test and re-published as HTML. Same error. I've double checked the .aspx file and they are the same in both instances. Gosh dang. What am I doing wrong - if anything?
We solved our problem. My programmer forgot to add cookies to capture all the information. Additionally, in case someone else does their own LMS, ASP.NET doesn't like double quotes. It's a security thing. One of my questions had quotes. Take them out - find another way to emphasize the text. I believe in regular ASP, double quotes can allow SQL Injection. So we fixed that issue as well.
And I do need to add - the Forum has been wonderful for a beginner like myself and I do love the product. Just finding out what goes where when you're under a tight deadline can be daunting! So thanks to everyone and their help!!
I'm glad you were able to find the cause of your issue, and I'm sorry it was such a frustrating process! I checked in with the Support team and they let me know they had been working on it with you - thanks for letting us know on the forum as well.
Discussions have been disabled for this post