Where to place "?NOJUMP" in iFrame code

  • rwaldenjr
    Asked on September 19, 2017 at 3:10 PM

    I tried using the "?nojump" command inside my IMBED codes and it worked perfectly. However, I've been instructed by your staff to use IFRAMES instead of IMBED to post forms to my webpages. And, I've had no success figuring out where to place the "?nojump" command inside the lengthy IFRAME statements.

    I tried placing it within the quotation marks for the Jotform ID. And, that hasn't worked (ex., my "Home Buyer Registration Form", and my "Property Seller's Inquiry" form). In fact, it truncates the forms, both in the site editor as well as when published.

    Does the command work in any other publishing context than IMBED? If so, please provide specific examples as to where I should place the "?nojump" command.

    Thanks!

  • Kevin Support Team Lead
    Replied on September 19, 2017 at 3:28 PM

    The "?nojump" parameter needs to be added at the end of the form's link, example: 

     <iframe

            id="JotFormIFrame"

            onDISABLEDload="window.parent.scrollTo(0,0)"

            allowtransparency="true"

            src="https://form.jotform.com/123456789?nojump"

            frameborder="0"

            style="width:100%;

            height: 8815px;

            border:none;"

            scrolling="yes">

          </iframe>

    If this still does not work, please provide us the link where you have embedded your form, we will be glad to inspect it. 


  • rwaldenjr
    Replied on September 19, 2017 at 4:23 PM

    That's perfect Kevin! There are at least a couple references to JotForm ID in the IFRAME statement. And, I'd attached the "?nojump" code to the first one, instead of the "SRC=" link. (You might wanna have your documentation team stipulate that a bit more clearly, like you did, in the User Manual.)

    Thanks for your assistance!

  • Kevin Support Team Lead
    Replied on September 19, 2017 at 4:51 PM

    You're most welcome @rwaldenjr. 

    Thank you for your suggestion too, we will take this into account.