You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Saving Umbraco Forms records programatically, when the form has a property of type File Upload, if an incorrect value is stored, when deleting a record causes deleting the entire media folder.
This bug was discovered when fixing this issue: #930
If no upload is selected what is coming is an empty object of FileList in javascript from the client.
As no upload is found, it is storing the string "[object FileList]" in the FileUpload field, i have fixed it storing null instead.
The bug is that if storing "[object FileList]" in the fileupload field, if you view the record in Umbraco Forms entries, the field is blank and if you delete the record, i dont know why the entire "media" folder is deleted.
So i guess the bug is that if an incorrect value is stored in the FileUpload field, deleting the record, may cause delete the entire media folder.
The text was updated successfully, but these errors were encountered:
Saving Umbraco Forms records programatically, when the form has a property of type File Upload, if an incorrect value is stored, when deleting a record causes deleting the entire media folder.
This bug was discovered when fixing this issue:
#930
If no upload is selected what is coming is an empty object of FileList in javascript from the client.
As no upload is found, it is storing the string "[object FileList]" in the FileUpload field, i have fixed it storing null instead.
The bug is that if storing "[object FileList]" in the fileupload field, if you view the record in Umbraco Forms entries, the field is blank and if you delete the record, i dont know why the entire "media" folder is deleted.
So i guess the bug is that if an incorrect value is stored in the FileUpload field, deleting the record, may cause delete the entire media folder.
The text was updated successfully, but these errors were encountered: