Post a reply

Before posting, please read how to report bug or request support effectively.

Bug reports without an attached log file are usually useless.

Options
Add an Attachment

If you do not want to add an Attachment to your Post, please leave the Fields blank.

(maximum 10 MB; please compress large files; only common media, archive, text and programming file formats are allowed)

Options

Topic review

martin

Re: Error report (Location profiles entry stores a wrong path to a remote directory)

Thanks for your bug report. The problem is obviously caused by some bug in "directory changes cache" function. You may turn it off on Directory tab of login dialog.
Wlodek

Error report (Location profiles entry stores a wrong path to a remote directory)

Hi Martin,

(Sorry for posting the report as a guest).

I am using the latest available version of WinSCP (3.6.1, Build 221). Here is a problem that looks like a bug to me:

1. Connect to a remote server. You are in your home directory.
1. Click the "Open directory/bookmark" button on a right-side panel.
2. Type in or paste any valid path (that differs from your home) into the "Remote directory" field.
3. Click the "Add..." button.
4. Click "OK". You are in that directory now (the target directory).
5. Click the "Home directory" button. You are in your home directory.
6. Click the "Open directory/bookmark" button on a right-side panel.
7. Double-click the entry you have just added. You are not in the target directory as you would expect. You are still in your home directory.
8. Try to switch to that directory manually by double-clicking the folder icons (representing the directories).
9. When you are one level up from the target directory, double-clicking the target icon does not open the target directory. Surprisingly, it opens your home directory.

I found the workaround for the above problem: When you are one level up from the target directory, click the "Refresh" button.

This is the second time I am sending you an error report. First time I sent another report under another user ID (probably Vladimir Anisimov), but it was so long ago that I forgot my password. You were able to reproduce the first error I reported and fixed it soon after (thank you!).

Best regards,
Vladimir Anisimov