Number Field: When you add Countdown and Day Countdown widgets, max value limit is ignored and continues to submit

  • Arcsight
    Asked on May 4, 2015 at 10:48 PM

    Hey Guys,

        I have found the problem I believe. If I remove every other widget (count down, captcha, etc) it works, otherwise it will not work. Is this a bug? can you guys help me to fix it?

     

    Thank you

    Daniel

  • Charlie
    Replied on May 4, 2015 at 11:14 PM

    It seems like the problem is the "Number" field, if you set maximum value and add a widget countdown or a similar one, it ignores it the limit and continues to submit.

    I've cloned your form "Daniel Poll" and was able to replicate the problem.

    I also made a test form, here it is: http://form.jotformpro.com/form/51238920646962. The Number field has a limit of maximum of "2" in the value. You can add higher than and it will continue to submit.

    I will escalate this to our developers to have it check. We will update you as soon as we hear any news regarding this matter.

    Apologies for the inconvenience.

     

  • Arcsight
    Replied on May 6, 2015 at 2:14 PM

    Hi, do you have any update in regards to this issue?

  • Charlie
    Replied on May 6, 2015 at 2:47 PM

    Upon checking the ticket, unfortunately it is still opened and the problem still persists. But I see that one of our developers is already assigned on it and it is marked as "Important".

    We should hear from him if a fix has been implemented. Unfortunately, I'm unable to provide an expected date to when this problem will be resolved, but rest assure that they are aware of this issue.

    Thank you for your understanding.

  • Arcsight
    Replied on May 7, 2015 at 1:30 PM

    Hi is there any update?

  • Charlie
    Replied on May 7, 2015 at 2:08 PM

    Unfortunately, there's no update yet if a fix has been implemented. 

    For a temporary workaround on this, could you try making the "Points left to vote" to "required".

    Number Field: When you add Countdown and Day Countdown widgets, max value limit is ignored and continues to submit Image 1 Screenshot 20

     

    This should prevent the submitting of the form when the condition is not meant.

    Do let us know if that works.

    Thank you.

  • Arcsight
    Replied on May 7, 2015 at 5:17 PM

    Ok, that seems to work, I have been testing it.

     

    Thank you

  • Arcsight
    Replied on May 7, 2015 at 6:47 PM

    Hi Charlie,

        Thank you for your help. I hope this bug gets fixed. I have been adding more features to my form and I have come to the point where I need that feature working. This is what I have.

    I added the "form Tabs Widget" to have several forms in one window navigating through the forms using (Back-Next). However, I want users to go from one form to another one, BUT some times users will not choose options in one form which means that any form may be empty, BUT because the counter is required users will not be able to click next UNLESS they choose at least one option.

    This problem can be overcome by fixing the bug. If the bug is fixed then users will be allowed to leave any form empty and at the same time they will not be allowed to use more than 10 votes per form.

     

    I appreciate any update.

    Daniel

     

  • Arcsight
    Replied on May 8, 2015 at 4:58 PM

    Hi Charlie,

        I don't want to put my hopes up, but are you guys planning to actually fix this bug soon or not? It would be good for me to know so I can see my options.

     

    Thank you

    Daniel

  • raul
    Replied on May 8, 2015 at 5:19 PM

    Unfortunately, we cannot provide an ETA for when this issue will be fixed.

    I can confirm that the ticket created by @Charlie has been already assigned to a developer with an Important priority.

    We'll keep you updated here about any news we have on this matter.
    Thank you for your patience.

  • Arcsight
    Replied on May 8, 2015 at 5:29 PM

    Ok, thank you. I appreciate your help.

  • liyam
    Replied on July 15, 2015 at 5:31 AM

    Hello,

    As of checking, this problem appears to be fixed. 

    Please do let us know if the problem persists.

    Thanks.