What is JotForm?
JotForm is a free online form builder which helps you create online forms without writing a single line of code. No sign-up required.

At JotForm, we want to make sure that you’re getting the online form builder help that you need. Our friendly customer support team is available 24/7.

We believe that if one user has a question, there could be more users who may have the same question. This is why many of our support forum threads are public and available to be searched and viewed. If you’d like help immediately, feel free to search for a similar question, or submit your question or concern.


  • Profile Image

    Next Page not working when a skip page condition is set - IE 8

    Asked by evandillon on November 16, 2011 at 09:51 PM

    I have a 4 page form. I set a condition that looks for the value of a drop down on page 2, and skips page 3 if that condition is met. The form works as expected in Firefox and Chrome but not in IE 6 on WinXP. In this configuration, with the condition set, the user cannot get past the first page. There are no validation errors, the user clicks "next" on page 1 and nothing happens. LIke I said, works fine in Chrome and FF. Also works fine without the condition, just not with the condition. Help!

  • Profile Image
    JotForm Founder

    Answered by aytekin on November 17, 2011 at 02:46 AM

    We are not doing any further development on IE6, since it is impossible to work with. You should probably remove the conditions and pagebreaks if you have many users with IE6. 

  • Profile Image

    Answered by evandillon on November 17, 2011 at 09:12 AM

    Same problem in IE 8

    Works fine without skip page condition but user hangs on page 1 with the condition set. I have tried removing all the page breaks and the condition and re-adding them. IE 8 still has significant market share.

  • Profile Image

    Answered by fxr on November 17, 2011 at 01:40 PM

    We would want to try and debug any bugs that are IE8 specifc.

    evandillon, can you recreate an example form with that exhibits this issue? so that we can clone it and see if there is anything we can do.

    thanks.

  • Profile Image

    Answered by evandillon on November 17, 2011 at 02:44 PM

    I ended up rebuilding the form from scratch. That took care of the issue.

    Originally, I created a new form by importing an existing from and modifying it as needed. After struggling with the bug on my long form, I created a smaller 4 page form with very little data and no required fields. I found it worked if the conditional field was a radio and didn't if the conditional field was a select box. However, in this test case, I was able to move from the first page, but it wouldn't recognize the condition with a select box. I decided that there must be some corruption from the import, so I decided to re-build the form from scratch using "create new form" and the newly created form works. Chances are, I won't import any forms any time soon!

    1/ Create a new form

    2/ add a text box and a page break

    3/ add a select box with option 1 | 2 | 3 and a page break

    4/ add a text box and a page break

    5/ add a submit button (you should now have 4 pages

    6/ add condition if select box not equal to 3 then skip to page 4

    7/ save and test. You should just move from page to page not matter what is selected in select box

    8/ now delete the select and add a radio button set in its place

    9/ delete condition and create a new condition like you did in step 3

    10/ now page 3 will be skipped if radio != 3

  • Profile Image
    JotForm Support

    Answered by Mike_T on November 17, 2011 at 05:17 PM

    We are happy to hear that the problem is solved.

    If you notice any other problems, please let us know.

    Thank you for your patience and cooperation with us.

  • Profile Image

    Answered by evandillon on November 17, 2011 at 06:36 PM

    Well, not solved. Worked around.  I don't think rebuilding the form from scratch technically fixed the bug. Just sayin'

  • Profile Image

    Answered by fxr on November 17, 2011 at 06:42 PM

    yep, you're right, evandillon, the developers are aware of the bug.

    We do appreciate you taking the time to provide a detailed description and workaround for the issue. If only all our members were as diligent. :)