Opened 19 years ago

Last modified 18 years ago

#624 closed Bug report

Drag and Drop files and non-empty subfolders misplaces folde

Reported by: youbastrd Owned by:
Priority: high Component: Other
Keywords: Cc: youbastrd, Eirik, Tim Kosse
Component version: Operating system type:
Operating system version:


The bug is that when dragging and dropping files and
directories from the right pane (remote server) to the
left pane (local), the target directory is correct for any
files, but incorrect for any subdirectories. If you drop
onto empty space in the left pane everything is fine, as
your intended target was the directory being listed.
However, if you instead drop on a directory name in the
left pane, any files you have selected go into that
subdirectory, but, the folders you had selected go to the
directory listed, and not the subdirectory that was
dropped on.

Confused? Here's an example.

The left pane has a view of "c:\local" . There exists a
directory "c:\local\local-images\" . We see:

The right pane has a view of a remote server. In this
view, we see:

We know that there's some files in the directory

The user selects everything in the right pane. The user
then drags one of the filenames to the left pane, over
"local-images", and releases the mouse button. Filezilla
does its thing, transferring files into local-images.
However, "remote-images" and all the files under it get
put into C:\local, and not C:\local\local-images\ like it
should. That's the bug, subfolders don't get placed
properly when dragged onto target folders.

Possible repeat of bug # 928152 , sorry in advance if
that's the case.

Thanks for making such great software. It's quite
inspiring to see something so well done in the
open-source community. :)

Change History (2)

comment:1 by Eirik, 19 years ago

Paul: You are right, this is a duplicate, but I'll rather
close that one and keep yours as it's much better explained.
Also moving to bug tracker.

comment:2 by Tim Kosse, 18 years ago

This bug report has been closed due to inactivity and has possibly
already been solved.

You can reopen this report if the issue still exists in the
latest version of FileZilla (Server).

Note: See TracTickets for help on using tickets.