Closed marcotrevisan closed 1 week ago
Hi @claucambra sorry if I use a comment to this ticket to ask this. I'd like to contribute to the FileProvider enabled client (not a Swift expert but I'd like to learn and fix/improve stuff). Is there any pointer on how to setup a dev environment for the client?
Thanks in advance and regards!
This seems to be a Finder visualization issue, which I was able to solve in Finder settings, by enabling the Show file extensions option.
Sorry I haven't figured it out before.
Practically, a dot followed by any word without spaces is viewed as the "extension" for a file/folder name in Finder. If there's a space anywhere after the dot, then Finder treats it as part of the name. I didn't know this was also true for folders.
Ah, happy to hear! :)
We've checked that other FileProvider implementations (i.e. G Drive) seem to handle this case correctly without having to force the "show all file extensions" in Finder. Seems like there's some way to tell Finder not to process the extensions on folder names under the "mount point" in CloudStorage....
Tested on 3.14.0-rc1, the issue does not show up. Unchecked the Finder configuration flag "Show all file extensione". Closing the issue.
⚠️ Before submitting, please verify the following: ⚠️
Bug description
This issue is a spin-off of #1337 @claucambra I found a small file naming glitch and was able to reproduce it. Folders containing "._" in their name get their name truncated once synced (unless there are also spaces in the name, in which case the folder will show up correctly). For example, "5._TEST" will show up in Finder as "5".
To reproduce it I created the following folders:
What happened at first is:
But after a while, those folders in Finder were showing up as follows:
Fortunately, their contents are OK. Updates to their content works as if nothing strange has happened.
on the NC server filesystem side they show up as follows:
and here is the difference: the one with spaces is deliminted by ' characters which seems to stop the harmful name processing.
More info on the above.
Steps to reproduce
To reproduce it I created the following folders:
Expected behavior
No file and folder name patterns are processed.
Which files are affected by this bug
FIles and folders matching particular patterns in their name
Operating system
Mac OS
Which version of the operating system you are running.
12.6.5 "Monterey"
Package
Other
Nextcloud Server version
25
Nextcloud Desktop Client version
MacOS VFS Beta (1 and 2)
Is this bug present after an update or on a fresh install?
Updated from a minor version (ex. 3.4.2 to 3.4.4)
Are you using the Nextcloud Server Encryption module?
Encryption is Disabled
Are you using an external user-backend?
Nextcloud Server logs
No response
Additional info
No response