Opened 20 years ago

Last modified 20 years ago

#576 closed Bug report

Client: Default remote directory not working

Reported by: Scott M. Sanders Owned by:
Priority: normal Component: Other
Keywords: Cc: Scott M. Sanders, Tim Kosse
Component version: Operating system type:
Operating system version:

Description

As of 2.2.4, the FileZilla client is not connecting to
the specified default remote directory of any site
entered in the Site Manager. It was working fine with
the last version.

I have two completely different sites, and neither will
connect to the specified default remote directory.

Note that it will still successfully look up the
specified default local directory.

I attached a log that shows what happens, or rather
what doesn't: It should connect to the default
directory (/www/) that I specified in the site's entry
in Site Manager.

Thanks.

Attachments (1)

log.rtf​ (6.3 KB ) - added by Scott M. Sanders 20 years ago.
Client: Default remote directory not working

Download all attachments as: .zip

Change History (5)

by Scott M. Sanders, 20 years ago

Attachment: log.rtf​ added

Client: Default remote directory not working

comment:1 by Scott M. Sanders, 20 years ago

OK, I had no idea 2.2.4b was released, but it's still an
issue in 2.2.4b. Thanks.

comment:2 by Tim Kosse, 20 years ago

Works perfectly in 2.2.4b

comment:3 by Scott M. Sanders, 20 years ago

Yes, I suppose it does...

AFTER IT WIPED OUT THE OLD DEFAULT REMOTE DIRECTORY SETTINGS.

Thanks.

comment:4 by Scott M. Sanders, 20 years ago

Apparently, it just erased that setting for the one I was
testing it the most on; the other site's setting was
retained. Hmm.

Thanks.

Note: See TracTickets for help on using tickets.