File already exists error even after the slide is deleted.
See original GitHub issueDescribe the bug
File with name 'sample.svs' already exists
error is shown even if the file was previously deleted from the slide table
To Reproduce Steps to reproduce the behavior:
- Upload a slide
- Delete the same slide from slides table
- Now try to re upload the same file without changing file name.
Screenshots
Desktop :
- OS: Ubuntu
- Browser: Chrome
Issue Analytics
- State:
- Created 3 years ago
- Comments:7 (7 by maintainers)
Top Results From Across the Web
File already exists - TechNet - Microsoft
Sharepoint throws up an error telling him that "The specified name is already ... There is a record for the original file that...
Read more >Destination file already exists and could not be deleted when ...
Destination file already exists and could not be deleted when upload · 1. Stop doing file.delete() when it doesn't exist. · I added...
Read more >SOLIDWORKS PDM Destroy Deleted Files to Avoid Duplicate ...
When checking in a SOLIDWORKS PDM file and a message "this name already exists in the vault" is displayed you need to destroy...
Read more >A zone cannot be created if a zone file of the same name ...
Therefore, attempts to create a zone using the same zone name as the deleted zone will fail because the associated zone file still...
Read more >Teams: A File with the Same Name Already Exists
Cancel. You can simply cancel the upload and rename your file. Change the file name, and the error should be gone. Keep both....
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@birm Should this be closed?
I think #23 is a better fix, as it takes care that when the slide is deleted from the DB, then only the file is deleted locally, and keeps the route secure as earlier. #25 has some major problems with the route security, which I have commented on the PR. These should be looked carefully, before performing any merge.