Error on image file size - after image in size restriction choosen does not resolve

  • Profile Image
    acregistration
    Asked on December 24, 2016 at 01:33 PM

    Testing the file upload feature for a large event coming up. Set at 1MB min and 3MB max.

    I have 3 images uploads in the form. https://form.jotform.com/63564193460155

    In the test I chose an image within the limits above, second image too large and lastly one too small.

    Of course I received two errors. I then chose an image in the scale I set for both errors. The image title appears correct, but the error does not resolve without resetting the form and losing all of the other data entered. Is there any way this could be avoided?

    - A friend of Goldilocks

  • Profile Image
    jonathan
    Answered on December 24, 2016 at 06:48 PM

    If I understand correctly, you are saying that the upload field validation error did not go away even after you have corrected the uploaded file with the correct file that was within the filesize range limits of your form https://form.jotform.com/63564193460155

    Example, I test uploaded a file that is below the minimum file size. So it has validation error.

    But when I correct the error by uploading instead a filesize within the range limits, the upload field validated properly and the validation error was removed.

     

    There is no need for me to refresh or reset the form to get rid of the validation error from the previous file I was trying to upload.

    Can you please confirm that this was the issue. Please let us know if its a different thing and we will check it further.

    Thanks.

     

  • Profile Image
    Musa 
    Answered on December 27, 2016 at 09:42 PM

    Yes you are correct. The upload field validation error did not go away even after I corrected the uploaded file with the correct file that was within the filesize range limits of our form https://form.jotform.com/63564193460155

    The problem has mysteriously resolved.

     

    Thank you.

  • Profile Image
    Charlie
    Answered on December 28, 2016 at 01:15 AM

    Based from your last response, it seems like the problem has been resolved already. It might have been a temporary issue. 

    If you encounter this problem again, please do let us know.

    Thank you.