When we moved over to the new servers, Shayne decided not to open up the port for FTP. Fair enough (a good security move). However, I was left with having to find another way to get in and easily edit files on the system. He recommended that I get an SCP client. I downloaded a few of ’em, not being all that impressed – then I stumbled across WinSCP. It handles SSH / SCP / SFTP sessions, and has direct hooks into PuTTY. I have a long history with FTP programs. Starting with the amazingly old and incredibly unintuitive WS_FTP, I moved to FTP Explorer. When the developer abandoned the project, I flipped to FTP Voyager – and found it to be completely overpriced for my needs. Then, it was off to SmartFTP, until the desktop flashing started to annoy me. I had veen on FileZilla up until recently (living with its shortcomings, too). WinSCP surprised me.
It doesn’t do everything I want it to do, but I discovered that you can locally edit remote files by double-clicking them! This feature alone has saved me so much time and energy. I had been relying on PSPad for the longest time to do all my server-based file editing through FTP (slow, clunky). While the WinSCP edit window leaves much to be desired, it’s quick and painless – and I can hook directly into PSPad for advanced functionality and seamless integration with the file transfer. Wow. Awesome. Cool. You need this. Forget the other FTP clients out there – if you don’t have this “edit locally, save remotely” feature in your FTP program, dump it. And FTP access through a plain ol’ file editor is just painful to navigate! WinSCP is wicked.