- markashtonAsked on October 15, 2015 at 05:07 PM
If you could pass this on to the devs doing the Filepicker Integration at the moment ....
Up until a few hours ago ... if you added photos to the filepicker function they would be added on to the existing photos of the original submission.
This has now changed ... so that new photos added ... completely replace existing photos.
So, you may have 5 photos in one submission.
Add an extra one by editing the submission in the submission bin ... opening filepicker ... adding thje photo manually .... all the other photos .... gone.
This has changed in the last few hours.
I think the filepicker function works better by adding to existing submissions not completely replacing.
As I am in the middle of a project ... and I have lost photos from an existing submission because of this .... I would be most grateful if you would give it your attention and reverse it.
Thanks, Regards Mark
- JotForm SupportChriistianAnswered on October 16, 2015 at 01:35 AM
I created a sample File Picker form and I was able to replicate the issue. When you edit the submission of the form and uploaded a new file this will replace the existing file.
I will escalate this issue to our development team for them to further check the issue. We will inform you on this thread once this issue has been fixed.
- markashtonAnswered on October 17, 2015 at 03:58 AM
This seems to be working as it should.
Am I correct that this is your understanding too?
- BorisAnswered on October 17, 2015 at 10:49 AM
I have just tested this by editing my submissions, Mark, and I can see that new files are now correctly added to the existing files on Filepicker. Files are no longer being replaced.
This was my submission before editing:
This is after editing that submission, and uploading one more file:
It looks like the files are no longer being replaced, that might have been just a temporary issue due to active development being done on this widget. Thank you for bringing it up to our attention, I will update the report to our developers that this seems to be fixed already.