-
-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
Share still exists after source file gets deleted #7238
Comments
Still happens |
A cron based check as well as on delete would be good, e.g. if users have shared something on external storage and the shared folder gets deleted or moved outside of Nextcloud |
just ran into that issue and got some ideas I want to point out: if trashbin is active only delete share when the file gets finally removed In that step it would be great to validate possible errors from remnants. I had the idea to move the filecache, storage and shares from the oc-tables to oc_xxx_remnants. That way the stability of the system's services like fulltextsearch could be better, even without removing remnants. |
When is this going to be fixed? |
cc @skjnldsv I removed the milestone. Please reschedule ;) |
I think this bug has been fixed for normal files (could not reproduce), but files within group folders still have this problem when using trashbin/deleted files app. See nextcloud/groupfolders#1699 |
Hi, please update to 24.0.8 or better 25.0.2 and report back if it fixes the issue. Thank you! |
This still/again (?) happens on 29.0.3 for both files and folders. At least orphaned links can be deleted on the command line now: |
Hi, please open a new issue for this. Thanks! |
Steps to reproduce
Expected behaviour
Share should be deleted from DB
Actual behaviour
Share still exists in DB table oc_share
Server configuration
Operating system:Ubuntu 16.04
Web server:Apache2
Database:PostgreSQL
PHP version:php 7.0
Nextcloud version: 12.0.3
Updated from an older Nextcloud/ownCloud or fresh install:updated from older nextcloud
Where did you install Nextcloud from:https://nextcloud.com/install/
Are you using an external user-backend, if yes which one: LDAP
This lead to one user having a broken share in "Shared with others" folder:
![errant_folder](https://user-images.githubusercontent.com/11816318/33074701-d7c21cd0-cecf-11e7-88b4-4108de3c9984.jpg)
I managed to get rid of it by manually deleting the share from DB table oc_share.
I would recommend for nextcloud to check when deleting a file, if it is shared. If yes then delete the share from DB too.
The text was updated successfully, but these errors were encountered: