Client 3.14.0 syncs Pictures/Videos/Music folders in Documents folder

[ProfPhoenix]

Hi,

yesterday I upgraded the Nextcloud client to 3.14.0. This causes some troubles:

I have a synchronization of my user folders like documents and pictures (Windows 11, German). Since the upgrade, the client detects the pictures, music and video folders additionally in the documents folder. So all three of them are synced twice.

The crazy thing about this is:

• The previous client version had no problems with this
• In the windows explorer all three folders don't show up (they are not invisible, too).
• I hardly can delete the folder in the Documents sync because it will delete the folder (because of the cloud-first directive). (I do not understand, why I cannot choose, whether I wanna delete the opt-out folders or just don't sync them anymore... :/ )

Yesterday I noticed that the client tried to sync a lot of GB after the upgrade although I wasn't changing anything this big. So I started messing around and I accidently deleted some folders, just because I used the opt-out in the client sync setting. Now I'm really careful, because all of the data in it was gone.

I could imagine that this is some windows thing or/and has something to do with changed permissions. I found some threads where synchronizations didn't work because of the permissions and maybe nextcloud got more permissions and can finally see the folders in the documents folder.

Also, if I click on the icon in the taskbar, the main window of nextcloud don't open. I can only open the settings window. I can't see any logic in this.

Nevertheless, thanks erveryone for continously coding on the Nextcloud project.

Greetings,
Joel

[philipgo]

Same problem here, which makes the client unusable :( (Nextcloud Windows 3.14.1, Win 10)

[schinddo]

I have also the same issue. I have deactivated the synch If the Documents folder, as I also accindentially deleted some files. Luckily I had a backup.

I hope the new behavior can be deactivated in newer versions.

[ProfPhoenix]

I finally found the issue #7609 and it seems that it was fixed with the new client version 3.15.1
I will install the new version after the next system reboot.

[schinddo]

I have updated and I can confirm, that it is working now as expected.

[ProfPhoenix]

Can confirm it, too :)