No way to not automatically sync new items (files and folders) added to root

[sduensin]

This is kind of a special case and I understand the logic behind the current behavior. However, as is, selecting anything to selectively sync partially selects the root folder. Anything new added to the root folder is automatically selected and synchronized to the clients. For newly added files this makes perfect sense. For folders, however, it can be dangerous. Being able to ignore external storage is great but it's highly annoying to have the sync client add things on it's own and then try to run around and stop all the clients before it fills their disk.

[nshobe]

This apparently has been a known issue in the community for some time. Forum mentions go back a bit further even.

nextcloud/server#3661

[Maxattax97]

My brother who uses my Nextcloud server was hotspotting with data, when a new (very large) folder began downloading in the background. This folder was inside the root directory, and was enabled by default in the client. I think this is a somewhat dangerous default, perhaps an setting in the UI would be best?

There are several issues related to this, and it's clear that this is a feature highly sought after.
#27 #39 #110 #30

[AndrewBucklin]

This could be resolved with Files on demand #17. Newly added folders would show up locally as a "ghost" folder, but would only begin syncing content after the user enters the folder / subfolder (and optionally, only files up to a specified size limit).

[Apromixately]

I just ran into a similar issue. I wanted to synchronize only a subfolder which I had reduced to 1.4 MB but then Nextcloud reported it needed to download 600 MB. From what I can tell, the reason is that Nextcloud also wants to synchronize plain files in the parent folders. This sort of makes sense since there is no file-level selection of what to synchronize. Still, it's not really the behavior that I wanted. I think the root folder is a special case of this.

[Apromixately]

I think the problem mentioned by @Maxattax97 is also totally valid but a different issue. Here the problem is that new folders are automatically selected to be synchronized. Maybe the default should be "if the parent folder is selected it should be added otherwise not".

[maxxer]

Additional feedback: new folders should be automatically synced only if parent is (fully?) selected. Given this situation on the client:

* [ ] Folder1
* [x] Folder2 
 \ *  [x] Folder3
* [ ] Folder5
 \ *  [x] Folder6

IMHO:

1. if I create a new folder in Folder2 it's synced automatically;
2. if I create a new folder in the root (or below Folder5) it's not synced automatically.

[redRolf]

I too would expect the behaviour described by @maxxer
In general, I would really like to see this feature. We have several use cases for this at our company. This feature request has been opened for 3 years, what would be needed to move this closer to being implemented?

[claell]

I'll reopen this, as duplicates of this issue (like #30) were still unsolved when closing them as duplicates.

[Joshuasony]

Same issue here and I agree with this thread and the request of being able on client side to decide if newly added folders are being synced automatically or not. Our Company with 150 people uses Nextcloud and users have no option the deactivate the automatic sync of new folders.

And on macos I have even another, very annoying issue: deselecting those automatically checked folders is not removing them from my harddrive. I have only found one other person that experienced this issue, but it was resolved for him when moving to a new server. #2468

[Ossur]

This is also a privacy issue. Many users sync selected folders to their work computers - which often are hooked up to all sorts of surveillance and running on proprietary operating systems. Any new folders popping up there is not good enough

[tomdereub]

Any news about this issue ? What do you think about the solution proposed here #10 (comment) ?

[albert-a]

@tomdereub, you are thinking in the right direction. The decision to sync subfolders should be made per each folder explicitly, rather than by trying to guess what user meant by unchecking some of the subfolders.

Although, I think cluttering folders selection dialog can be confusing for users. The majority of users probably don't need it. I think that's why "Edit Ignored Files" (aka .sync-exclude.lst) is implemented separately. Not everybody needs it.

IMHO, this flag should be called "Manual Sync", and should be set on specific folder by creating empty file .sync-manual in the folder. Optionally it could be implemented as a checkbox in the context menu when right-clicking on the folder in the desktop client:

If the flag set for the folder, then

• its subfolders should be automatically deselected for each new desktop client installation/connection.
• if the flag appears on the existing installation, it does not trigger deselecting subfolders, but simply prevents new subfolders from being automatically selected.

PS: Though not all users need this feature, it can be extremely useful for the others. My use case is that we have a large Libraries folder, each subfolder of which is a library. Each user needs a small subset of the libraries, and selects what is needed. But when the new libraries become available, they are automatically synced to all users, which is of cause not desired. I would really benefit from this feature.

[albert-a]

Alternatively:
This feature could be implemented with .sync-manual.lst file which could be empty, or contain the list of subfolders that are selected by default on the new desktop client installation/connection.

[tomdereub]

@albert-a : We are now starting to use VFS sync (even if we still have performance issues at the moment, especially first sync that's very long). With VFS we don't meet this issue any more.