yeah unfortunately the issue with long path names in Windows still exists under the hood - there are OS config + code workarounds, but as we have to work on all setups we can't use them in the uSync package (not easily with net framework anyway).
but there are things you can do in uSync config to mitigate this.
The principle one is to switch to using Guid file names (see config), as this will make the filenames the GUID values so not dependent on the length of the item. (you would need to do a clean export for this as you need to clean the existing items to avoid duplicates)
Length of path when exporting ?
Hi Kevin,
When exporting a rather large site, with a rather big media archive, I get the error Could not find a part of the path.
Could this be path-length problem ? The path is 270 charaters long.
I remember from old days that the windows OS could have issues with paths above 255 charaters. But I thought that was fixed ages ago.
I know I can set the FlatFolders property to true, but that makes it a bit hard to delete the files that you don't need.
Hi Sebastian
yeah unfortunately the issue with long path names in Windows still exists under the hood - there are OS config + code workarounds, but as we have to work on all setups we can't use them in the uSync package (not easily with net framework anyway).
but there are things you can do in uSync config to mitigate this.
The principle one is to switch to using Guid file names (see config), as this will make the filenames the GUID values so not dependent on the length of the item. (you would need to do a clean export for this as you need to clean the existing items to avoid duplicates)
is working on a reply...