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: That appears to be it

Thanks for your feedback.
I have fixed the problem:
https://winscp.net/tracker/1759
If you want to keep using the recycle bin and want to test the fix, please let me know.
heyesr

That appears to be it

Hi,

That appears to be it - I unchecked that box and it appears to be editing files and symlinks as expected.

Thanks.

Richard
martin

Re: Log file

heyesr wrote:

I've found that it doesn't seem to be a protocol thing - I have two connections setup - one with a private key and one with a password - and it's only the private key connection that doesn't work properly.

It actually seems to be related to "remote recycle bin", isn't it?
https://winscp.net/eng/docs/ui_login_recycle_bin
heyesr

Log file

Hi,

I've found that it doesn't seem to be a protocol thing - I have two connections setup - one with a private key and one with a password - and it's only the private key connection that doesn't work properly.

Log file is attached.
martin

Re: Editing symlinks

heyesr wrote:

That was it thank you - the protocol was set to SFTP instead of SCP. So I changed to SCPP and it works fine. Thank you.

OK, but can you post a log file for SFTP anyway?
heyesr

Re: Editing symlinks

martin wrote:

What protocol are you using? Please attach a full session log file showing the problem (using the latest version of WinSCP).


That was it thank you - the protocol was set to SFTP instead of SCP. So I changed to SCPP and it works fine. Thank you.

Richard
martin

Re: Editing symlinks

What protocol are you using? Please attach a full session log file showing the problem (using the latest version of WinSCP).

To generate the session log file, enable logging, log in to your server and do the operation and only the operation that causes the error. Submit the log with your post as an attachment. Note that passwords and passphrases not stored in the log. You may want to remove other data you consider sensitive though, such as host names, IP addresses, account names or file names (unless they are relevant to the problem). If you do not want to post the log publicly, you can mark the attachment as private.
heyesr

Editing symlinks

Hi,

When I have a symlink to a text file and I edit the symlink and save it - the link is overwritten with a new file - ie the link is not preserved.

Is there some configuration that I must do to make winscp preserve the link? This happens even with the WinSCP internal editor.

Thanks

Richard