Coreftp was working fine until a few days ago. Then, all of a sudden, I could no longer double click on a directory and have it navigate into the directory at the left (local side). Now when I double click on a directory, nothing happens.
When I drag the whole directory to the remote location (right hand side), it now shows all these error messages: 550: Can't create directory: not a directory" and then it displays the path that it is trying to create to (It is a file that it is trying to create, but shows it as a directory).
I therefore seem to be having some type of file/directory mixup issue. Any ideas? Thanks. Up until this time, everthing was pretty smooth sailing.
coreftp has gone bezerk (double clicking on files fails...)
I found the problems. There are two, actually. Both should be fixed in CoreFTP.
1. In the Site Manager, for any particular site, you have the "Advanced" option (right next to Host/IP/URL). If you click on that, you have another option called "Directory/Folder". The first problem I had was that the "Local Start Folder" was set incorrectly because I changed the path on my local hard drive. CoreFTP seems inept at being able to handle this. If the path is not found, instead of indicating that it cannot find that path, it jumbles and confuses the existing directories and makes them completely unclickable (a double click achieves nothing). This ought to be fixed.
2. Second, sometimes CoreFTP messes up completely and will lump a file instead of a directory when a transfer is being done. This is what actually happened. I wanted to transfer the directory contents, and proceeded to do so. But a file was created instead in the destination folder. Then when I attempted to do it again, it would not create the folder because a file with the same name already existed. The problem here was that instead of simply stopping and indicating "A FILE BY THAT NAME ALREADY EXISTS", it came up with this error message, "550: Can't create directory: not a directory". CoreFTP should stop right there and indicate the name of the directory that cannot be created. Instead, it kept on going, through endless other files and directories, trying to create them (about 100). It could not create a single one of them, because it was unable to create the root directory, because it had already (mistakenly, earlier) created it as a file. It took me hours to find out that a file by that name had already been created by CoreFTP -- using another FTP client which clearly showed the problem on the first time around.
This is a good FTP client. It needs a little brushing up, however.
1. In the Site Manager, for any particular site, you have the "Advanced" option (right next to Host/IP/URL). If you click on that, you have another option called "Directory/Folder". The first problem I had was that the "Local Start Folder" was set incorrectly because I changed the path on my local hard drive. CoreFTP seems inept at being able to handle this. If the path is not found, instead of indicating that it cannot find that path, it jumbles and confuses the existing directories and makes them completely unclickable (a double click achieves nothing). This ought to be fixed.
2. Second, sometimes CoreFTP messes up completely and will lump a file instead of a directory when a transfer is being done. This is what actually happened. I wanted to transfer the directory contents, and proceeded to do so. But a file was created instead in the destination folder. Then when I attempted to do it again, it would not create the folder because a file with the same name already existed. The problem here was that instead of simply stopping and indicating "A FILE BY THAT NAME ALREADY EXISTS", it came up with this error message, "550: Can't create directory: not a directory". CoreFTP should stop right there and indicate the name of the directory that cannot be created. Instead, it kept on going, through endless other files and directories, trying to create them (about 100). It could not create a single one of them, because it was unable to create the root directory, because it had already (mistakenly, earlier) created it as a file. It took me hours to find out that a file by that name had already been created by CoreFTP -- using another FTP client which clearly showed the problem on the first time around.
This is a good FTP client. It needs a little brushing up, however.