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

    Filepicker - Add folders to Amazon S3 bucket uploads

    Asked by markashton on July 09, 2013 at 02:19 PM

    FAO Kenneth & Filepicker Engineers

    To use Jotform's Filepicker service ... one needs a Filepicker account ... and if you have one of these you have to have an Amazon S3 account to host the images and videos.

    So, I realize on setting all this up that the Amazon S3 thing is just a massive bucket. Every jotform, and every submission all end up in the top directory of the bucket - hopeless.

    I ask Filepicker the following ...

    Am I correct to assume that all my image and video files, from many different jotforms and clients, are to reside in the top level directory of the bucket?

    Filepicker replies as follows ...

    S3 supports the notion of folders and we support uploading to folders on our api. Folders are part of the path name, so my_folder/my_image.jpg is valid.

    So, as it stands all the images are just chucked in a massive bucket which is totally unworkable - you have no way of seeing or deleting the images/videos for a particular form submission.

    The recent Filepicker integration requires jotform submissions to create logical folders per form otherwise everyone's in a world of s**t.

    Can you advise me please - bit of a dealbreaker I'm afraid.

    Very glad to help on this as soon as done

    Thansk Mark

    filepicker form filepicker amazon s3 form
  • Profile Image
    JotForm Support

    Answered by Mike_T on July 09, 2013 at 04:52 PM

    Hello Mark. I have forwarded a feature request to add the folder option to our Filepicker integration.

    We will update this thread when we have any updates.

    As a workaround, you may consider using different Amazon S3 buckets for different forms.

    Thank you.

  • Profile Image

    Answered by markashton on July 09, 2013 at 05:13 PM

    Hi Mike,

    Thanks for the update.

    That workaround is not possible if you look at the filepicker setup. The S3 configuration only allows one S3 bucket from within the filepicker interface

    Unfortunately, due to the complete inability of a jotform user to differentiate between submissions and the forms they have come from, I'd have to say that the filepicker inetgration is not fit for purpose.

    You see it is misleading that there is a coherent solution here ... it requires someone to spend hours of config and testing only to find at the end that well ... you've got no way of managing it at the other end.

    Seriously needs fixing with the new API ... can you pass on to Kenneth if he's the dude dealing with this.

    Thanks Mark

  • Profile Image
    JotForm Support

    Answered by Mike_T on July 09, 2013 at 07:22 PM

    Our filepicker integration is supposed to be easy to use, one does not need either to manually create a filepicker account or have an Amazon S3 account. However, if you want to have more control over your data you can integrate the filepicker app with your Amazon S3 account.

    Form owner can also check upload links via emails, submission pages and filepicker account. Files can be deleted from Console.

    To use different buckets, you will need to use different filepicker applications. Our integration is ready to accept API keys of filepicker Applications.

    As a quick example, create new App and integrate it to different bucket.

    Integrate it with your filepicker tool on the form.

    Thank you.

  • Profile Image

    Answered by markashton on July 10, 2013 at 05:44 AM

    Hi Mike,

    Thanks for that. There is a workflow I can use ... so I'm chuffed.

    However, you state above ... "Our filepicker integration is supposed to be easy to use, one does not need either to manually create a filepicker account or have an Amazon S3 account."

    How does one use the filepicker function without having to manually create a filepicker account?  ... the first thing the wizard asks for is "please enter your Filepicker.io email information" ... how can this be avoided ... I see no way.

    If you don't have to have an Amazon S3 account ... wher are the uploaded filepicker files stored?

    I'd be very grateful for clarity ... thanks for your time and good help

    Regards Mark

  • Profile Image

    Answered by markashton on July 10, 2013 at 06:47 AM

    Hi Mike, (please relate to above post)

    I've investigated this further and if I could challenge an assumption or two ....

    To use the filepicker function in Jotform ....

    - One does need to manually create a filepicker account

    - One does need an Amazon S3 account - it is a condition of using the filepicker service

    - The method you propose is limited to 100 buckets - see here: http://aws.amazon.com/articles/1109#09

    and here interesting: https://forums.aws.amazon.com/thread.jspa?threadID=85760

    - The method you propose, although workable, will not be adopted by the avaerage jotfrom user as it is far too complex. It involves interacting on all levels i.e. jotform, filepicker and amazon S3

    (However, I'll use it - so thanks ;-)

    - The folder inclusion via the new filepicker API integration is critical.

    Filepicker state ...

    S3 supports the notion of folders and we support uploading to folders on our api. Folders are part of the path name, so my_folder/my_image.jpg is valid.

    Thanks 

  • Profile Image
    JotForm Support

    Answered by Welvin on July 10, 2013 at 11:33 AM

    Hi Mark,

    Thanks for your input about our FilePicker Integration. We appreciated your time digging deep into this. Our developer Kenneth told me that he's already working on this. 

    I will also create a separate thread with regards on setting up FilePicker without having to create an account, this is a possible bug since I am able to add filepicker using any email address.

    Thanks for letting us know.

  • Profile Image

    Answered by markashton on July 10, 2013 at 11:53 AM

    Hi Welvin,

    Can you post the threadurl for me to have a look 

    Thanks Mark

  • Profile Image
    JotForm Support

    Answered by Welvin on July 10, 2013 at 12:03 PM

    Hi Mark,

    Here's the thread: http://www.jotform.com/answers/241926-.

     

    Thanks

  • Profile Image
    JotForm Support

    Answered by kenneth on July 10, 2013 at 12:35 PM

    Hi again mark, seems both of us were being active lately :)

    Anyway, I just implemented S3 bucket as per Filepicker second option on where to upload your files.
    Look at the image below. You need to navigate to the new tab 'advance settings' to configure your s3 connection with jotform+filepicker.
     

    In the end, you will have two links of your file. One from InkFilePicker server and One from S3 Bucket. 

    Please check this out and confirm if it works from your end. Let me hear some feedbacks.

    Thanks,
    Kenneth

  • Profile Image

    Answered by markashton on July 10, 2013 at 12:36 PM

    @Welvin
    That isn't working? can you check it?

    @Kenneth
    Great stuff mate - let me test and check ;-)

    Thanks mark

  • Profile Image
    JotForm Support

    Answered by Welvin on July 10, 2013 at 12:49 PM
  • Profile Image

    Answered by markashton on July 10, 2013 at 12:51 PM

    @kenneth

    you've been working amazingly hard mate - I'm well impressed.

    Let's lose the filepicker folder - just adds extra depth.

    Personally, I think this is much better - no one's going to want the filepicker folder - it's just in the way - they will have to keep changing the default path

    What do you reckon ... I'm sure about it as a user of the service ... 

    Amazon S3 Upload Path - Now: 

    JotForm/filepicker/{formID}

    Amazon S3 Upload Path - Consider:

    JotForm/{formID}

    Thanks Mark

  • Profile Image
    JotForm Support

    Answered by kenneth on July 10, 2013 at 01:00 PM

    All set, please wait all the servers to propagate the changes to be able to get the latest update.
    If you havem more concerns please let us know. We appreciate every report you're going to make :)

    Thanks,
    Kenneth 

  • Profile Image

    Answered by markashton on July 10, 2013 at 04:33 PM

    Ken,

    Have tried a test.

    The filepicker is failing on upload ... it states in the interface ..

    This site only allows you to upload files under 1000KB 

    However, the jotform max file size upload I set as 20480000 which i believe 20Mb

    I can upload anything under 1Mb ... but no more - not much use for photos and stuff

    Is there something via the API that is set at 1Mb that needs changing

    I'd send a screenshot buit having a smartphone to desktop transfer problem

    Thanks mark

  • Profile Image

    Answered by markashton on July 10, 2013 at 05:35 PM

    Ken,

    From a uniqueness point of view ... /{formID}  is a good option

    But I want to either use the form title or append it to {formID} like this:

    demos/{formID}-{form_title}

    I note that form title doesn't work... it just comes in as a folder named {form_title}

    Am I using the wrong name for the field or do you have to tweak something.

    I think this is important so people have a vague clue what form relates to what folder in Amazon S3

    Thanks Mark

  • Profile Image

    Answered by markashton on July 10, 2013 at 05:41 PM

    Ken,

    You need to update filepicker.io to InkFilepicker in the Jotform application under power tools

    Regards mark

  • Profile Image
    JotForm Support

    Answered by kenneth on July 10, 2013 at 11:35 PM

    Hi mark, made some few changes again. I agree with some of the recommendations.

    Well, update includes the new keyword {form-title} and Filepicker.io renamed now to Ink-Filepicker.

    About the max file size, I cannot replicate the error. It works from my end. Just make sure that you have input a valid (number) filze size, or you may want to check your Ink developer portal if you set a max file size under "Global Limits".

    Thanks,
    Kenneth 

  • Profile Image

    Answered by markashton on July 11, 2013 at 05:08 AM

    Hi Ken,

    I have tested the new keyword {form-title} and it works a dream.

    Thought - It occurred to me though ... if you change the title of your form at anytime ... then a new folder would be created ... which is not ideal. Also, jotform allows the same name for multiple forms ... which would goof things up I'm sure.

    So, by default I'd leave it with the {formID} in the form builder - as the upload path - as nothing can go wrong.

    If anyone queries the fact that they can't deal with folders as big numbers then you can always offer the {form-title} as a solution in the forum ... but with the warning of cock-up potential.

    I will be using the {form-title} in the path ... much more logical

    -----------------------------------

    You were right about the max file size ... I had only set it in jotform ... not in Filepicker ... I had created a new bucket and there was no max file size in global limits for that bucket.

    Thanks

    Let me do some more testing and I'll come back with more

    Regards Mark

  • Profile Image

    Answered by markashton on July 11, 2013 at 06:19 AM

    KEN IMPORTANT .....

    There is a bug that needs addressing with the filepicker integration ... and a request when you are fixing it ....

    Please see thread here: 

    http://www.jotform.com/answers/242401-Filepicker-New-Integration-Has-Created-HTML-Report-Bug#0

    Regards Mark

  • Profile Image
    JotForm Support

    Answered by KadeJM on July 11, 2013 at 10:27 AM

    Hey Mark, As far as I know Ken is pretty busy at the moment but thank you for pointing out the issue on this. I will go ahead and pass along your provided details.

    I think I understand what you mean about the {formID} vs the {form-title}. I believe that Ken chose to go the {form-title} route simply because of the issues and complaints we've amassed in the past from users complaining constantly about the long string of numbers being used as the foldername value when a submission is generated. But it's also clear about the issue with this since you are right that Forms can be named the same thing so that would create conflict if the {form-title} is used. I imagine in this case something new would need to be implemented for both to create preference options to choose or better yet control them but it will have to be looked into more though.

  • Profile Image

    Answered by markashton on July 11, 2013 at 10:50 AM

    @kadeJM

     As far as I know Ken is pretty busy at the moment but thank you for pointing out the issue on this:

    Yeah! What's he doing then? I'm pretty busy too! Ken makes it clear in his post of 1.00pm yesterday that he appreciates every post I'm going to make. If he's jumped ship ... then I won't bother to test this any more ... as I have been doing all this morning .... but I can tell you what .... it is totally broken from a reporting point-of-view ... not fit for market ... and you should remove it so as not to waste people's time.... if it is the case that it is not going to be addessed today. Or at least change it back to the way it was - no good doing half a job - that's worse than not starting. And there's me waiting to test it some more.... jeez

    I believe that Ken chose to go the {form-title} route simply because of the issues ... blah blah

    Nonsense ... he chose that route because I advised him that it was better from a user point of view ... through testing.

    -------------------------------------

    What I want to know is ... Has the filepicker integration been ditched in this state? Because if it has I'm going to be well annoyed as it was working perfectly well the other day ... you decide to tinker with until it is not working and the reports a spewing out garbage  ... and then leave it.

    Thanks Mark



  • Profile Image
    JotForm Support

    Answered by kenneth on July 11, 2013 at 11:29 AM

    Mark, we sincerely apologize for the late response. You see I'm still working on the feature, I'm fixing the bugs you mentioned and yeah we really do appreciate for that matter. We are trying our best to scalate and then give solution to the problem.

    Anyway, I cant give you ETA for that, I will update you as soon as I fixed it just like the other feature you request and bugs you reported. So just keep eye on this one, to the other thread not here.

    Thanks for your patience,
    Kenneth 

  • Profile Image

    Answered by markashton on August 01, 2013 at 01:03 PM

    This isn't working properly ...

    Amazon S3 bucket takes the {form-title} when using the form directly.

    Embed the form in any way ... the Amazon S3 bucket then takes the Page Title not the {form-title} as the bucket name.

    Needs addressing. 

    Thanks mark

  • Profile Image
    JotForm Support

    Answered by Mike_T on August 01, 2013 at 02:23 PM

    Mark, please create a new thread about that issue. This thread has a feature request ticket attached, so we need a new thread to create a bug report ticket.

  • Profile Image

    Answered by markashton on August 01, 2013 at 03:48 PM

    Why Mike .. it's the same thing.

    The folders have been added .. but they areb not behaving as they should.

    This is not a bug. It is a direct result of the integration.

    Thanks Mark

  • Profile Image
    JotForm Support

    Answered by Mike_T on August 01, 2013 at 05:35 PM

    I was able to reproduce this with the source code embedding option. I am going to left a note for Kenneth.

  • Profile Image

    Answered by markashton on August 01, 2013 at 05:44 PM

    Nice one Mike. Thanks

  • Profile Image

    Answered by markashton on August 05, 2013 at 06:15 AM

    Ken,

    I'm ready to test any API tweaks "in the moment" ...

    To let you know ....

    1) An image in Filepicker that is deleted ... deletes the file in Amazon S3 ... so the missing link is Jotform deleting the referenced file in Filepicker

    Thanks Mark 

  • Profile Image

    Answered by markashton on August 13, 2013 at 03:25 PM

    Hi .. Mike's right ...

    Let's close this thread as there is a seperate thread for:

    Filepicker Integration Unfinished - No File Deletion through Filepicker to S3 Bucket
    http://www.jotform.com/answers/247357-Filepicker-Integration-Unfinished-No-File-Deletion-through-Filepicker-to-S3-Bucket

    and ..

    Amazon S3 bucket takes the Page Title not the {form-title} as the bucket name if embedded
    http://www.jotform.com/answers/255841-Amazon-S3-bucket-takes-the-Page-Title-not-the-form-title-as-the-bucket-name-if-embedded#0

    Thanks

  • Profile Image
    JotForm Support

    Answered by EltonCris on August 13, 2013 at 03:49 PM

    Thanks a lot for your cooperation, Mark. The provided threads are now escalated to our dev team.

    Regards!

  • Profile Image

    Answered by firstfoundation on August 15, 2013 at 01:37 PM

    Mark just wanted to say thanks for pushing Jotform to tighten this integration up and implement the S3 buckets properly..it was the one missing piece for us to integrate it fully and, now that we can, it'll greatly help our business.

     

    Many thanks to Jotform for putting the work in to get this done - it has greatly enhanced the product.


    Gord

  • Profile Image

    Answered by markashton on August 15, 2013 at 01:43 PM

    No prob Gord,

    From what I can see the whole thing is working as it should with a workflow that "works".

    Result: The best photo upload solution currently possible for smartphone web-apps/ forms. 

    Thanks Mark

  • Profile Image
    JotForm Support

    Answered by Mike_T on August 15, 2013 at 03:50 PM

    Thank you guys for being loyal customers :) your feedback helps us to put things right.