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.
Conditions seem to have stopped working in cloned formAsked by BAX on July 18, 2013 at 03:44 PM
I have created 3 forms recently bvy cloning a past form (now disabled). It seems none of my conditions from the past form are working. However, they still show up on the saved conditions list. Ideally, I would love to not have to recreate all the conditional formatting. Please let me know if there is a way to get these conditionals workign again.
Cloned Form stopped working saved love 3
First off, the URL links you provided for your forms were not working because they were alll mixed up.
These are the correct URL for each forms.
Can you please guide us which conditions specifically you are referring to. There are a lot of conditions on each form, and it is best if we try to fix it one form at a time.
In my initial checking of the Artists Information form, I already tested which condition does not work, even the the very 1st condition does not work.
AND I think the culprit is the slash(/) character in your form field label/question
It is known that some text characters tend to break the form's logic condition because they mixed up with the condition code. Known characters are /,\,@,# and even when using number as the first character in the field question i.e "1 Contact Person/Director"
I suggest first you try to correct this text characters in your form's field questions. Try removing the the slash(/) character and refresh the condition. And then, test again.
I am sure this should fix the issue already, but nonetheless please inform us if further issue persist.