Opened 15 years ago
Last modified 15 years ago
#3503 closed Bug report
Display issues on win server using \ rather than /
|Reported by:||relytor||Owned by:|
|Keywords:||Cc:||relytor, Alexander Schuch, Tim Kosse|
|Component version:||Operating system type:|
|Operating system version:|
FileZilla used to display fine when I connected to this server. I haven't connected in several months, and now the display tree for the server isn't displaying correctly. FileZilla no longer seems to treat a back slash as a directory separator for display purposes. Actual functionality still seems to work correctly, so it is only a display issue. See the attached screenshot, as it shows the situation much better than words can describe. FYI, I am using FileZilla Client 18.104.22.168
Change History (7)
by , 15 years ago
comment:1 by , 15 years ago
You are using Windows Vista?
comment:2 by , 15 years ago
You have an exotic server that uses backslashes instead of slashes as separator. Almost all servers use slashes as separator and on most, backslashes can be a valid component of file and directory components.
Fixing this would require a lot of work for limited use. Please upgrade to a proper server.
comment:3 by , 15 years ago
In response to ci-dev, the client is running on Windows Vista. I don't know what the server is running, as it isn't my server, just one to which I connect to upload files to a client's hosting company. I don't know if the bug is new in the last several builds of the client, or if the server software changed in the last few months, but it used to display properly when connecting to this server. Unfortunately, I don't have access to the server information other than the address, login, and welcome message. I know it is a web server that is running IIS.
comment:4 by , 15 years ago
Thanks for reporting. This issue has been fixed in the SVN
repository and will be available with the next version.
comment:5 by , 15 years ago
Try 3.0.11-rc1, should be released in a couple of hours.
comment:6 by , 15 years ago
Confirmation that this issue is resolved as of 3.0.11-rc1. Thank you!
Screenshot of wrong server directory tree structure