Blank Symbolic Linked sitemanager.xml File

[Micah Zak]

Our company uses FileZilla to all our FTP accounts with all our employees on Windows 7. Up to 3.8.1, we have been running our accounts off a soft symbolically linked sitemanager.xml ( via mklink in cmd )file that is backed up offsite, and thus available to all our employees as they work on their specific version of FileZilla. When we updated to 3.9.1, FileZilla is now unable to see the mklink'd file's contents, and returns 0 bytes. As this has happened across all our computers, and we've re-linked the files numerous times with no success, we've reverted back to 3.8.1 so our business can continue to operate.

As a clarification, the file itself is not located on an internal server, as some of our employees do not work in the office. It has been setup on each pc's with a soft symbolic link that references a file in a local folder that is backed up offsite and each of our pc's have that cloned folder ( Dropbox ).

We'd love to provide any additional information to assist in this bug's resolution, as it is and has been an intricate part of our development model for many years.

Thank you for all that you do. FileZilla is the best solution out there for what we do, paid or free.

[Tim Kosse]

Symbolic links to redirect settings files are not supported in any released version of FileZilla, past or present.

[Tim Kosse]

Turning this into a feature request.

[Tim Kosse]

Symbolic link support has been added to the repository and will be available in the next version.