My Pictures inside Documents Folder

ℹ️ Support
, , , ,
1

Nextcloud version (eg, 29.0.5): 30.0.1
Operating system and version (eg, Ubuntu 24.04): Ubuntu 22.04.5
Apache or nginx version (eg, Apache 2.4.25): Apache 2.4.52
PHP version (eg, 8.3): 8.1.2

I’m going to omit the rest of the information for now, because in all honesty, I don’t even know if this is strictly Nextcloud’s fault. I’m just at my wits end with this and I don’t really know where else to turn. I’m hoping someone out there will know something - anything - about this.

Screenshot 2024-11-03 195148

I have a fairly small installation which I just reinstalled using Nextcloud AIO. (Though this has been happening even before the reinstall.) I have folders appearing in the Documents folder in Windows 11 named “My Pictures”, “My Videos”, and “My Music.” I’d read somewhere that these could be related to backwards compatibility in Windows and that they’re junctions, but Nextcloud backs them up, and they continually re-appear. Because I already have these backed up through Nextcloud separately, this causes my documents folder to grow to immense sizes, and for basically no purpose.

Has anyone out there seen anything like this and know what to do about it? I’ve been battling myself with this for weeks now without any real solution to this.

2

Update to this:

I just used the web interface to delete the My Pictures, My Videos, and My Music folders from the Documents folder, and it resulted in the desktop client wiping all of those folders on my systems. (As in, removing it from the Documents folder, as well as the files from their actual locations.)

I fortunately have a backup, but this would be disastrous otherwise.

3

Alright, nevermind. Google was on my side tonight it seems, as a bit of further digging finally brought me to this issue in the desktop client:

https://github.com/nextcloud/desktop/issues/7157

4

This needs more attention – seems like a junction issue introduced in 3.14.x and it’s causing HAVOC on my side. so much data loss of family photos due to this change not being properly documented or communicated :confused: