FileZilla Forums

Hi

First post. Firstly, thanks for a great app.

I have come across a bug (I think). When in Kiosk mode:

fzdefaults.xml: Drag and drop functionality breaks. The error message received is:

Drag&drop between different servers has not been implemented yet.

Platforms I have tested this on: Windows XP, Windows Vista, Windows Server 2003, Windows Server 2008

Any help would be appreciated. Perhaps I can do something with the config values (nothing stood out) ?

I cannot reproduce this, drag&drop continues to work even if I enable Kiosk mode.

Where are you dragging from? Where are you dragging to?

Thanks for replying botg. I should have been more specific with the drag and drop.

What I CAN do:
- Drag from Windows Explorer into the Remote Site (within FZ).
- Drag from the Local Site (within FZ) to the Remote Site (within FZ)

What I CAN NOT do:
- Drag from the Remote Site (within FZ) to the Local Site (within FZ). But in the Remote Site (within FZ) I can double click to download AND I can add to queue. Not really a big deal.
- Drag from the Remote Site (within FZ) to another folder within Remote Site (within FZ). This one really affects workflow.

@botg: I run in kiosk mode 1, too, and I can confirm this. I have not yet reported it because I don't use D&D often. Will retest it based on the post from nocelery.

Edit: right now I cannot reproduce it... damn.

Some very obscure bug it seems.

Hi botg

Are you saying you do not get this bug at all ? I have replicated it on multiple OSes (XP, Vista, Server 2003, Server 2008), multiple PCs and multiple installs (exe install, winzip download, portable app). Same behavior everytime.

Some info that is not relevant to the bug:

The reason we use Kiosk mode is because we place the Filezilla config file on the server and then all use Kiosk mode in combination with a remote Config Location ("<Setting name="Config Location">\\server\FileZilla$\settings\</Setting>") so that we have access to the same FTP sites rather than all having to maintain it individually. I can confirm though that the bug is present regardless of whether the the remote Config Location is used or not.

The reason we use remote D&D is that we often backup the remote file before overwriting it by dragging it into a backup folder.

For now we have reverted to FileZilla2 as it works across the LAN in read only mode, albeit without the filters and synchronized folders .

Are you saying you do not get this bug at all ?

Yes.

I have replicated it on multiple OSes (XP, Vista, Server 2003, Server 2008), multiple PCs and multiple installs (exe install, winzip download, portable app). Same behavior everytime.

Perfect. Then you should be able to describe the exact steps necessary to reproduce this problem. Fastest and easiest way would probably be a screencast with audio commentary.

You can use http://camstudio.org/ for the screencast.

OK, here it is:
(broken url removed)

Duration 2 minutes.

Installed on a clean virtual machine running XP SP3.

The missing piece of the puzzle, you're using a saved site with password that was created before kiosk mode was enabled.

What happens if you open the site manager, select that site and hit OK?

Under those specific conditions the 'bug' disappears. Is this by design ?

So does that mean when FileZilla is in Kiosk mode, one must have access to all the passwords in order to use Drag and Drop ? or is there perhaps some other config variable I can set to get around this ?

Do you know of any other way to share a read only config file on a network (other than Kiosk mode). I would appreciate any assistance.

What about adding some sites to fzdefaults.xml, but not enabling kiosk mode?

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:

Is it a read-only share?

Also, try creating the shared sites using the ASK logon type.

Thanks, it is a read-only share as I do not want users to mess with the site list and want everyone to have a standardised FTP list.

I realise that the ASK password will work, but this would mean all the users have to know and type in the password everytime they FTP or I update the FTP list. While this is a technical solution it does not achieve a better workflow than FileZilla2.

Seems like there is not a work around or solution for this. I appreciate all the assistance but will revert users back to FileZilla2 for now and will check back again in a few months to see if there is a mode/config I can adapt to my needs.

Thanks again for your assistance,.