Thanks botg but this would be the same as propagating the "sitemanager.xml" file across the network.
I really appreciate the help.
Ideally what I am after is to have the ability to have a centrally managed "sitemanager.xml" so that individual users do not have to maintain individual site lists.
Kiosk mode has allowed me to do this (with the exception of Drag and Drop functionality). It sort of works if I disable Kiosk mode, but then we get error messages on start up about not being able to write to certain files:
Error writing xml file
---------------------------
Could not write "\\server\FileZilla$\settings\layout.xml": Failed to create backup copy of xml file
Failed to create backup copy of xml file
Error writing xml file
---------------------------
Could not write "\\server\FileZilla$\settings\queue.xml", the queue could not be saved.
Failed to create backup copy of xml file
Probably not relevant, but Filezilla2 runs from a network share without issue. We are not running Filezilla3 from a network share, we just use fzdefaults.xml to point back to a network config folder:
Code: Select all
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<FileZilla3>
<Settings>
<Setting name="Kiosk mode">2</Setting>
<Setting name="Config Location">\\server\FileZilla$\settings\</Setting>
</Settings>
</FileZilla3>