-
Notifications
You must be signed in to change notification settings - Fork 806
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
Updating to 3.0.2 selects all folders to sync #2492
Comments
Hm... I was pretty sure we had a duplicate for that one but can't find it now, let's tag. |
Ah right thanks. Juggling too many balls at the same time. :-) |
Also affected, I think the client was updated from 2.6.5 as 3.0.1 had some other issues (on this machine it was like 2.6.5->3.0.1->2.6.5->3.0.2). It seems that also the default 500MB limit isn't honored - I've added few gigabytes on other machine and 3.0.2 stared syncing those without asking (server @19.0.3). |
Not sure if this is connected, but it seems to me: I had the same issue of all folders selected for syncing flooding my internal HD with all the photos from the past. So I deselected all but the previous year folders and everything was fine |
This bug report did not receive an update in the last 4 weeks. Please take a look again and update the issue with new details, otherwise the issue will be automatically closed in 2 weeks. Thank you! |
How to use GitHub
Expected behaviour
Updating from 2.6.x to 3.0.2 should keep the folders which are selected to sync configured as them
Actual behaviour
ALL folders are selected to sync.
Steps to reproduce
Client configuration
Client version: 3.0.2
Operating system: Windows 10
OS language: German
Installation path of client: default
Server configuration
Nextcloud version: 19.0.3
More Information
Actually happened to three different employees. But the first two updated to 3.0.1 more then one week ago. Today I've updated to 3.0.2 on another machine. Same behavior. Then i tried it on MacOS - everything worked as expected, so it seems to be an Windows related topic?
The text was updated successfully, but these errors were encountered: