Allowing '.' as a valid folder and OneDrive issues
Posted: 25 Nov 2024, 22:29
I tried to use CloudSync to sync my OneDrive folder to my F8 NAS.
I must have at least 30 folders in my OneDrive root.
Creating n+ links to keep the whole thing in sync is not reasonable.
What happens when a new folder is created?
You really need to support '.' as a selection folder for both the source and destination with the meaning that is syncs everything under the sharename or into the destination base folder. That's how a mapped drive works in Windows - you map the entire sharename, not just a single folder. It's how mounting a Remote Folder should work as well.
In addition, CloudSync doesn't properly handle external shared links in OneDrive.
What I mean is, if someone shares a folder with me, I'm given the option to incorporate it directly into my OneDrive structure.
CloudSync sees it in the folder selector, but doesn't link properly. I'm not sure what it sees it as, but it doesn't create a functioning folder.
I don't know if the same is true for a single file.
Thank you,
David
I must have at least 30 folders in my OneDrive root.
Creating n+ links to keep the whole thing in sync is not reasonable.
What happens when a new folder is created?
You really need to support '.' as a selection folder for both the source and destination with the meaning that is syncs everything under the sharename or into the destination base folder. That's how a mapped drive works in Windows - you map the entire sharename, not just a single folder. It's how mounting a Remote Folder should work as well.
In addition, CloudSync doesn't properly handle external shared links in OneDrive.
What I mean is, if someone shares a folder with me, I'm given the option to incorporate it directly into my OneDrive structure.
CloudSync sees it in the folder selector, but doesn't link properly. I'm not sure what it sees it as, but it doesn't create a functioning folder.
I don't know if the same is true for a single file.
Thank you,
David
