Millisecond Forums

You use a custom launch page, and you probably generated and downloaded that page *before* you made further changes / specified a custom finish page.

Open https://www.millisecond.com/myaccount/scripts/amb2139/CosmosBattery/LaunchPage.htm in your browser and view its source. You'll find that specifies to direct to the default finish page:

        // Specify the web page to browse to if the experiment is completed successfully (specify null to stay on this page)
         var FinishPage = "http://www.millisecond.com/web/finish5.aspx";

Edit var Finishpage to point to your custom finish HTML and re-upload the modified file.

Thanks! That solved the problem.

Two other questions:
1. On some of our "openended" elements, sometimes the typing cursor appears in the text box (allowing text input), but other times it doesn't. Nothing I seem to do code-wise seems to affect when this happens; indeed opening the same study multiple times on the same computer (to try to figure out why it's happening) showed that it happened somewhat randomly across different openended elements. Is there anything I can do to circumvent this problem?

2. One of my participants reported getting the pop-up saying: "Inquisit was unable to contact the server to verify that this script is licensed. The script will not run." I had previously hit this bug when I had cloned a launch page, and it still pointed to the wrong study, but I've checked and that's not the case here. What else might be causing this?

Many thanks for all your (past, present and future) assistance!

No idea about the <openended> elements unfortunately. It's not something I have either seen or heard previously. If you have some example code that illustrates the problem (reliably), that might be helpful.

The error message your participant received means that -- for some reason -- the Inquisit application on her/his computer was unable to make contact with the server to verify that the web script is properly registered. That could be due to a number of reasons, most likely on the client-side of things, such as a firewall (locally or on the network perimeter), a network timeout or packet loss due to an unreliable internet connection.

EDITED TO ADD: The license verification failure could theoretically also be due to the client having TLS disabled. That should usually not be the case under anything above Windows XP (which isn't supported by Inquisit 5 anymore anyway), but may be worthwhile checking nonetheless. https://www.millisecond.com/forums/FindPost17155.aspx

I've added in the mouse to the openended trials, so that should serve as a work around for the erratic error that I can't pin down.

If I might ask, are there specific requirements to run the Inquisit 5 Web Player? We're planning to test older adults (some of whom may not have great computer skills), without technical assistance, and it would be helpful to know about any technical limitations up-front...

No, there are no specific requirements for the web player. It should work on any compatible system that satisfies the general system requirements, under all major browsers.

https://www.millisecond.com/products/inquisit5/requirements.aspx