You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When the synchronize function looks in subfolders, it erronously includes local files that reside in a completely different folder that simply happens to have the same name and being the target of a symbolic link. An example makes it easier to understand:
Let's call the folders to be synchronized for 'MainFolder', same name in the local and remote domains.
Both the local and remote 'MainFolder' have a subfolder called 'pics'.
Both the local and remote 'MainFolder' also have a symbolic link named 'picsCommon' that points to a folder named 'pics' that resides above 'MainFolder'.
When Synchronize compares and lists files in the the subfolder 'MainFolder/pics', it will ALSO include all files in the local 'picsCommon'!! That's very wrong! Thus, it lists the union of all files in 'MainFolder/pics' plus the files in the folder 'pics' that reside above 'MainFolder', as if they were all in 'MainFolder/pics'!
If I do a synchronize ONLY of 'MainFolder/pics', then it behaves as it should because that does not contain any subfolders.
The text was updated successfully, but these errors were encountered:
When the synchronize function looks in subfolders, it erronously includes local files that reside in a completely different folder that simply happens to have the same name and being the target of a symbolic link. An example makes it easier to understand:
If I do a synchronize ONLY of 'MainFolder/pics', then it behaves as it should because that does not contain any subfolders.
The text was updated successfully, but these errors were encountered: