Skip to content
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

deleting a folder should send one delete request for the whole folder to the server if possible #612

Closed
schiessle opened this issue May 10, 2013 · 6 comments

Comments

@schiessle
Copy link

This issue was reported in the core repository but I think we have to fix this on the client side: owncloud/core#3192

The problem: If you delete a folder "foo" on the desktop the sync client will send a delete request to the server for every single file in the folder. For the server this looks like independent delete operations. This means that the files will appear in the trash bin one by one together with a empty folder "foo" so that the user has no option to restore the folder together with the files.

Would it be possible for the client to send only one delete request for the folder if all files within the folder and the folder itself are deleted on the desktop?

@guruz
Copy link
Contributor

guruz commented May 10, 2013

Right now, mirall/csync is operating on a "per file" basis. There is no concept of folders that could be deleted instead of the file. I think @ogoffart was working on changing that, but I'm not sure.

(There is some possible things to think about, like concurrent modifications where we would not want any data loss)..

@schiessle
Copy link
Author

@guruz I'm not into mirall/csync so maybe this is a dump idea. But shouldn't it be possible for the sync client to detect that also the parent of a file is gone and than ignore the single files and only send one delete request for the top-level folder to the server.

@schiessle
Copy link
Author

@danimo @dragotin Is is really not possible to detect folder delete on the client and send a single delete request to the server? We are getting regular bug reports because of this behaviour.

@guruz
Copy link
Contributor

guruz commented Aug 8, 2013

@ogoffart has some code to do this ("new propagator").

Need to discuss with @dragotin etc at the dev meeting next week on when to start using that..

@etiess
Copy link

etiess commented Sep 11, 2013

Hello,
This issue is still there in 1.4.0. And the problem is big if I want to restore the folder: I have to restore all individual files!
Is there a project to solve that?
Thank you!
Etienne

@ogoffart
Copy link
Contributor

Should be fixed with 1.5

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants