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 widget: Deleting a submission does not delete the actual image that was uploaded to Filepicker

    Asked by Mark Ashton  on January 11, 2016 at 10:55 AM


    The Filepicker Integration is working very promisingly.

    In the early days ... when Ken Implemented this feature ... when one deleted a submission ... the corresponding photo was deleted from the Filepicker service ... which in turn was deleted in the Amazon S3 bucket.

    This provides a very clean workflow ... and all was working well.

    However, now ... when one deletes the submission in Jotform this is not deleting the photo in Filepicker ... so this connection is broken.

    I guess this is a consequence of the new filepicker API integration etc.

    Would you be kind enough to put this in front of Titus please to consider.

    He advised me to come back regarding my tests for the file picker widget.

    Many Thanks

    Regards Mark


  • Profile Image

    Answered by Boris on January 11, 2016 at 01:18 PM

    Thank you for letting us know of the change in the behavior, Mark. I have just forwarded this as a bug report to our developers / widgets team, so they can see about having the automatic deletion of files working seamlessly again.

    If this change in behavior was caused by a change in the upgraded Filepicker API, rather then a regression in the implementation on our end, your report will simply be considered a feature request instead.

    If or when our developers have any updates regarding this, we will let you know through this thread. Thank you.

  • Profile Image

    Answered by Mark Ashton  on January 11, 2016 at 01:34 PM

    The filepicker API is not the issue ... they wouldn't have removed the ability for developers to control the deletion of photos through to the Amazon S3 bucket. No one would be able to organise anything.

    Customers will have a graveyard of images in filepicker with no control 

    Come on .. I've put in tonnes of hours telling you about your crappy bugs that keep turning up ... i've found three today alone ... I just haven't the time to report them.

    This worked 3 years ago ... ken implemented it ... get him on it ... or advise Titus of what I've found.

    I'd be most grateful.

    Many Thanks

    Regards Mark


  • Profile Image
    JotForm Support

    Answered by BDAVID on January 11, 2016 at 03:29 PM

    I have advised Titus of what you have found. You will be notified via this thread about any updates on this report.

  • Profile Image

    Answered by markashton on January 13, 2016 at 06:42 AM


    The filepicker integration is working beautifully ... bar one thing.

    It is not a performance issue with the filepicker integration and how it works in the field.

    No ... it is a workflow issue as advised above.

    If you a jotform with 250 submissions and 250 photos ... you delete all submissions in jotform .... currently you still have to go into filepicker and delete all 250 photos manually. This is a real problem when you have three different forms ... as all photos are kept in athe same place ... so it is nearly impossible to know what photos are with what form.

    Here is the Filepicker .. now Filestack interface ...


    can you see the problem

    Many Thanks

    Regards Mark

  • Profile Image
    JotForm Support

    Answered by beril on January 13, 2016 at 10:13 AM


    Thank you for your screenshot and detailed information.

    The ticket was assigned to one of our different developers. I've updated the ticket. We will inform you when we solve the problem.

    If you have any question or issues, please do not hesitate contacting us. We will be glad to assist you.

  • Profile Image

    Answered by markashton on January 13, 2016 at 10:35 AM

    Hi Beril,

    Thanks for the update.

    Look ... don't start screwing around with the filepicker widget without giving me a heads up. Why? Last time jotform did it ... I lost a client because all the reporting was screwed etc ... images didn't show properly in Grid reports.

    Titus apologised ... but bottom line it cost me dearly. 

    You make changes and don't test things properly ... jotform does not test changes to destruction ... but for the filepicker widget ... I will do all that ... but I need to know first.

    Titus said he would advise me on any changes in the future. I have projects with clients in the field ... don't want them to break ;-)

    Who has been assigned this please?

    Also, what does Titus say as he was the guy who schedules this stuff is he not?

    Thanks Mark



  • Profile Image

    Answered by Boris on January 13, 2016 at 11:46 AM

    We completely understand your concern, Mark.

    The bug has been assigned to Ken, and we haven't heard anything back from Titus. As a side note, Titus is not necessarily the one that always assigns these tasks, even though he is the head of the Widgets Team. Sometimes, bugs get assigned to a developer by one of the other managers, though as the head of the Widgets Team, Titus still oversees these tasks that are assigned to his team.

    I'm sure Titus will let you know when there will be any modifications being done to the Filepicker widget. I am also adding an internal comment to this bug report for Ken to let you know when he is making changes to this widget, to make sure that you are informed about them. :)

  • Profile Image

    Answered by markashton on January 24, 2016 at 08:49 AM

    Come on guys ... this is an important part of the filepicker setup. Otherwise there is no image management whatsoever for all your clients.

    This was a perfectly flawless feature of the original jotform implementation. Now it's not working. it's not right to add to a function/widget and not leave what's already in place. Why? Then people like me have to utilise there valuable time to constantly bang on to you to get it fixed. Not fair. My time worth $100ph. You gonna pay me for this forum post that has the purpose of improving your product?

    What's happened here is this ... you've implemented a new Filepicker API ... and haven't tested it properly.

    In fact I'd go as far as to say that you did not test it at all ... in terms of the workflow Jotform > Filepicker > Amazon S3 ... you cannot have done this ... otherwise you would have seen it.

    So, you didn't test the filepicker upload function ...its asset stamp in filepicker and its storage in Amazon S3. And then you didn't test deleting the submission ... and observing that it was deleted across the across the aforementioned services.

    Why? All this functionality is built into the jotform interface. what were you thinking?

    Who doesn't perform rudimentary tests before a release?

    Respectfully mean't. Please advise.

    Many Thanks

    Regards Mark

  • Profile Image

    Answered by markashton on January 25, 2016 at 01:39 PM

    Bump ;-)

  • Profile Image

    Answered by markashton on January 27, 2016 at 05:02 AM

    mmmm ... got to that has it.

    Doesn't warrant an answer?

    I'll take a deep breath ... Will you fix this excellent widget so that it works properly with regard to deleting submissions across the associated services.

    Thanks Mark

  • Profile Image
    JotForm Support

    Answered by beril on January 27, 2016 at 09:13 AM

    Hi Mark,

    Unfortunately, there is no update yet. Be sure that our developers will take care of your issue as soon as possible.

    Thank you for your understanding and patience. You will be notified when our developers solve the problem.

  • Profile Image

    Answered by markashton on February 04, 2016 at 06:33 AM

    Sort this the &*^% out will you ...

    I didn't spend months of effort getting this implemented for you to break it due to incompetence and leave it broke ...

    Shame on you !

    Tell Aytekin will you please.

    Don't give me a stock answer either. Tell me some good news.

    Regards Mark

  • Profile Image

    Answered by Boris on February 04, 2016 at 07:53 AM

    Sorry about this Mark. Aytekin is aware of the issues with this widget, and has decided to remove the Filepicker/Filestack integration.

    Aytekin said:
    Sorry for the trouble this has caused for you. We have decided to get rid of this widget completely. We are not integrating with filepicker/filestack any more.

    Your existing forms that were already set up with Filepicker will continue to function in the same way they did just before the Filepicker integration was removed. Thank you for your understanding.

  • Profile Image

    Answered by markashton on February 04, 2016 at 07:55 AM

    No please don't do that ... please don't remove the widget.

    That will end my business ... just leave it as it is ... it works fine

    Please let me know ..


    Regards mark

  • Profile Image
    JotForm Support

    Answered by beril on February 04, 2016 at 09:33 AM


    I've also sent an email to Mr Aytekin. Be sure that, I really want to get back to you with good news.

    I will let you know as soon as possible.

    Thank you.

  • Profile Image
    JotForm Support

    Answered by beril on February 04, 2016 at 11:18 AM


    Mr Aytekin told me that: We only removed it from the widgets list. You can still continue using existing file picker widgets on your existing forms as long as you wish. Or when you need one on a new form, you can start on the form by cloning another old form that has file picker widget.

    I hope, that will makes you happy.=)

    Have a nice day!