Source code embed: Captcha loading image keeps spinning

  • aricurn
    Asked on May 23, 2016 at 8:39 AM

    I added a jotform to a mobile view section of the website using the source code. £10 voucher form works fine on desktop view.

    On mobile view, the wheel just turns for the submit button and enter code, so the form cannot be completed - help please - thank you so much

  • Boris
    Replied on May 23, 2016 at 10:52 AM

    On the link you have provided, I see that the captcha field is spinning and the image cannot be loaded:

    http://newquayvets.co.uk.mobileview.website/10voucher.php

    Source code embed: Captcha loading image keeps spinning Image 1 Screenshot 30

    However, the form is working fine when it is accessed directly, even on mobile devices:

    https://form.jotformpro.com/form/50545229792966

    The linked "mobileview.website" site shows some PHP errors in the browser console, and is also preventing the scripts of the form to run correctly. The site converted all the form's scripts into encoded text, so the scripts of the form cannot execute properly:

    Source code embed: Captcha loading image keeps spinning Image 2 Screenshot 41

    In order for the form to function correctly, please either (1) use the Iframe embed method, or (2) use direct link to your form. This guide will help you with embedding the form:

    https://www.jotform.com/help/148-How-to-get-your-Form-s-Iframe-Code

    Please let us know how it goes.

  • aricurn
    Replied on May 24, 2016 at 11:21 AM

    Thank you. It works, although back to problem I had of being unable to input my e-mail address on mobile view when the form is added in as an i-frame. It shows red sign saying please enter valid e-mail address on my windows phone. Tried using Chrome, but still get this error?

  • Charlie
    Replied on May 24, 2016 at 12:46 PM

    I see you already have another thread with the concern about the email address field, here's the link to it: https://www.jotform.com/answers/844962  It would be best to update or reply on that thread instead because there's already an ongoing discussion of it, and to avoid confusion.

    Thank you.