Custom Query (8105 matches)
Results (265 - 267 of 8105)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #10479 | fixed | User can not see the contents after login to the FTP server. | ||
| Description |
My FTP server is pure-ftpd(v1.0.31). I can see the contents of the FTP Server by using FileZilla 3.10.3, But I can not see any contents of the FTP server by using FileZilla 3.11.0.1. In addition, if the FTP server is vsftpd(v3.0.2), FileZilla 3.11.0.1 can display the contents of the server normally. |
|||
| #6515 | outdated | "open"/"edit" commands on local file does not launch the right application | ||
| Description |
When I double-click (or choose "open") on a ".doc" file in Windows explorer, it opens in MS Word. In Filezilla, if I choose "open" or "edit" on the same (local) file it opens Wordpad. Wordpad it the second application in my "open with..." menu. The same happens with other extentions: source code which opens with notepad, etc. FileZilla should use the default/first application associated with the "open" action. |
|||
| #1315 | v3 hangs or won't load | |||
| Description |
Bear with me, since I have to give a good context for the problem. I work for a small company that maintains a working copy of it's website on the network (set up as network drive G:), then sends the changes to the live site via FTP. (I recently installed Filezilla 3.0.2.1 and love it.) This company is very closely associated with a university, and we use their network since they have such vast resources, though that means I have no control over the quality/performance of their network. So, here's the goods: I came in, tried to connect filezilla through the site manager to the ftp, which is configured to bring up the network drive (g:\) on and the public_html on the live site, and it hung. I killed it, figuring the program was just being bitchy, but then when I restarted it, nothing came up except for a running filezilla process. In any case, I found the source of the problem: the office has been having problems accessing the network drive, and it was being entirely non-responsive, and since filezilla goes right back to where I was, it was trying to bring up G:, but stalling (without even loading the interface). My thinking is, this might be easily fixed by adding a timeout function where it just gives up trying to bring up the local directory and defaults to something safe, say "My Computer". Just my thinking, someone else might have a better solution? |
|||
