-
-
Notifications
You must be signed in to change notification settings - Fork 4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug]: delete action failed - cannot delete or move a file #44631
Comments
cannot move either (could not move )... |
Thanks for reporting, adjusted title! |
hmmm, I am noticing that after a refresh, the action is taken into account. EDIT: another different behavior: when clicking delete the file, nothing happens. Nothing. Upon refresh, an error pop up shortly before page reloads Once page reloaded, files are still present. |
Does not reproduce locally but does on c.nc 🤔 MOVE returns a Maybe you'd have a better idea here @juliushaertl ? Edit: After waiting for a few minutes it seems the files are eventually deleted so something seems to be slowing down the process on the server |
I have same problem in Android app. I think it's a backend bug. How to Reproduce
|
I remember @come-nc having a similar issue in Cypress, the issue was that the file was locked during the preview generation, so deleting it failed if the request was made right after its creation. Maybe waiting for the preview request to be done would help. |
Seems fixed on c.nc, closing |
Bug description
I cannot delete a file I recently created on c.nc.c
Steps to reproduce
Expected behavior
File should get deleted
Installation method
None
Nextcloud Server version
29
Operating system
None
PHP engine version
None
Web server
None
Database engine version
None
Is this bug present after an update or on a fresh install?
None
Are you using the Nextcloud Server Encryption module?
None
What user-backends are you using?
Configuration report
No response
List of activated Apps
No response
Nextcloud Signing status
No response
Nextcloud Logs
No response
Additional info
No response
The text was updated successfully, but these errors were encountered: