some users on Windows 10 1903 have installed a Seafile Client and they have synchronized a library on local machine that contain a long named folder tree: the absolute path is longer than 260 characters.
The users notice some problem using the “synchronized local folder”:
- when the user will try to move a file into the leaf of this tree, windows deny the operation with an error message of long path file name, so no new file can’t move on this folders.
- when the user attach a file into a e-mail using Thunderbird the mail client insert the file using a “tilde” shorter name. This behavior happen also opening the file in Word, and if the file contain link to others file, word detect an error.
I will try to use the Seafile drive mapping a remote drive. The problem 2 in fixed the number 1 no.
The same behaviors happen also with the windows 10 “long path” registry feature enabled.
If I create a new folder or a new file into the library from another client (or via web interface) Windows synchronize the folder correctly.
The workaround is using shorter file names but for the user is important using this kind of naming.
Someone detected the same problem. There are some solution.
Thanks a lot for any suggestion.