- gallerymediaAsked on September 18, 2011 at 05:49 PM
I created a condition on the form, that was like i'm having an uploader to upload files directly to my FTP. i need people not to click submit form button until or unless the uploading is completed. is there any way that upon completion of the uploading it automatically submits the files to my FTP, without pressing SUBMIT button? or is there any other way around that people don't see the button "SUBMIT FORM" until or unless they have completed uploading the files, because the files sizes will be bigger, and therefore i need to know if there is any way around to do this.
I'm really in a bad condition because i need to get this done asap!
I created a condition that once a upload is filled users should see the submit form, other wise they don't but it seems not to work with it. i don't know why . can you please clear my queries or come up with any solution to the problem please ??
I'm anticipating your kind response.
- JotForm FounderaytekinAnswered on September 20, 2011 at 05:14 AM
Make the upload field required and they should not be able to submit it.
Please do not ask the same question on multiple threads. Thanks.
- gallerymediaAnswered on September 20, 2011 at 06:48 AM
I tried making the upload field required, but what i see here is that once the file is selected, if we clicks on Submit then it never waits for the file first to be uploaded, it let the submit work.
I mean to say is that it allows the form to submit weather the file is fully uploaded or not. what is the way around to only be submit able once the file is fully completed, is there any way around or trick? like you gave a trick of making it as a required field, which once the file is selected it allows the users to submit, without looking at wheather the file was completed or not?
Please let me know, i'm stucked in badly with this problem.
I love using jotform, but sometime i get limited access to what i'm trying to do.
- JotForm FounderaytekinAnswered on September 20, 2011 at 07:26 AM
OK, I see. One of our developers are working on a fix for this now. We will update this thread when it is ready.