Last night, my Movable Type installation decided it wanted to keep me from further posting on any of my blogs. This wasn’t simply an authentication error with my login and password. Something in MT’s lib directory wasn’t playing nice, and I kept getting this error:
MT/App/CMS.pm did not return a true value at /www/retrophisch/public/movabletype/mt.cgi line 21.
Now I had been considering upgrading to Transmit 3, since as a registered user of version 2.x, I could do so for $17.95. Or I could, as a registered user of version 4.x, upgrade to Interarchy 7 for $19.
This really wasn’t a fair contest, as I was using Interarchy 7.3.1 and the last 2.x version of Transmit, 2.6.2, not the new version 3. For whatever reason, whenever I SFTPed in to my domain with Transmit, the transfer mode always turned to Auto, with no way to turn this off so I could transfer in ASCII, or Text, mode. Interarchy saved the day. It reuploaded MT’s lib directory from the local installation copy I had, preserving permissions, etc. And while they’re so similiar, I’m not sure there’s much of a differece, but I like Interarchy’s “Edit in BBEdit” implementation better than Transmit 2’s.
Transmit’s a great app, don’t get me wrong, but this time around, my money went to Interarchy.
I wondered about this for a while myself. Then the topic came up on the BBEdit-Talk list and Peter Lewis himself explained why this is so.
SFTP has no concept of Text Mode Transfers (Interarchy supports this by allowing you to specify the remote line endings and doing the conversion itself).The normal solution for this, especially with BBEdit, is simply to use Unix line endings on the local file. BBEdit doesn't care, and most modern Mac apps can cope with CR or LF line endings.
Personally, I haven't updated to Transmit 3 yet. Just been too busy. Interarchy looks impressive (and almost always has), but I don't know if it's worth $40 for the amount of FTPing I do.
Posted by: Eric Blair
at February 25, 2005 02:53 PM