New plugin available: Cloud (access to Box, Dropbox, etc).

[CharlesB]

Are there known issues with how the plugin handles folder names containing special characters, when using Google Drive? I noticed two problems:

• When a folder contains a colon character (eg. "2010:2011"), the copy of a folder to the local disk does not work.

• There are weird behaviours with the slash character (eg "2018/2019"). I can't create a folder from the plugin if the name contains a slash. Also, on an existing folder with a slash in the name, there is an infinite loop with a subfolder taking the name of a parent folder... which prevents me from copying the folder at all.

Thanks

[petermad]

2CharlesB

Those two example are typical Windows file system restrictions - colons and slashes are not allowed in file names - see for example: https://learn.microsoft.com/en-us/windows/win32/fileio/naming-a-file

[CharlesB]

Yes but shouldn't the plugin handle these restrictions gracefully?
For instance, when I click on the folder below:
Image: https://ibb.co/fF83fYr
it shows the content of the parent folder (Sou) instead of the selected folder (Sou\ARCHIVES\2020/2021).

[petermad]

For instance, when I click on the folder below:
Image: https://ibb.co/fF83fYr
it shows the content of the parent folder (Sou) instead of the selected folder

You are right - it is not smart, that you cannot even go into 2020/2021 - it is understandable that you cannot copy the folder to local disk though, but the plugin should give a warning instead of going into and endless loop as it does now.

[ghisler(Author)]

The problem is that many file systems use forward slashes as path separators, so they are needed for sftp, webdav and other plugins. There is no way for TC to handle forward slashes or backslashes in file or folder names.