Say I have a remote folder called 'aaa'. I want to replace its content the difficult way:
- I delete folder 'aaa' at the remote side
- I upload a folder 'bbb' from local to remote
- I rename folder 'bbb' to 'aaa'
I expect the new content to be available at the 'old' location. However I receive the following message:
Successfully transferred at 2608,72 KB/s
The server doesn't support SITE CHMOD
Loading directory listing from server (LC_TIME=en_US.UTF-8)
EPSV
229 Entering Extended Passive Mode (|||35134|)
MLSD
150 Opening BINARY mode data connection for MLSD
226 Transfer complete
Operation canceled...a file with the new name already exists
So it looks like gFTP thinks the old folder is still there. Renaming the folder 'bbb' to 'aaa' from the command line at the remote side (mv bbb aaa) works fine.
Say I have a remote folder called 'aaa'. I want to replace its content the difficult way:
I expect the new content to be available at the 'old' location. However I receive the following message:
Successfully transferred at 2608,72 KB/s
The server doesn't support SITE CHMOD
Loading directory listing from server (LC_TIME=en_US.UTF-8)
EPSV
229 Entering Extended Passive Mode (|||35134|)
MLSD
150 Opening BINARY mode data connection for MLSD
226 Transfer complete
Operation canceled...a file with the new name already exists
So it looks like gFTP thinks the old folder is still there. Renaming the folder 'bbb' to 'aaa' from the command line at the remote side (mv bbb aaa) works fine.