MarsEdit 2.1 Problems
February 3rd, 2008Update: I have figured out the reason for these mysterious XML-RPC failures. It has to do with a conflict between MarsEdit 2.1 and certain loadable bundles that implement a method with the same name as MarsEdit. In particular, if you are using WriteRoom and installed the “Edit in WriteRoom” bundle, you are likely to see the bug in MarsEdit. Also, older versions of a similar bundle for editing in TextMate would exhibit the same problem.
I’ll be updating MarsEdit ASAP to use a more unique method name to avoid the clash. In the meantime you can work around the problem by disabling this Input Manager.
Original post below:
I released MarsEdit 2.1 last Thursday, and on the whole, reaction has been positive, and people are enjoying the new features!
However, there have been a few hiccups, and I’m working hard on fixing a few issues that people have spotted and reported to me.
The worst of these issues is a mysterious “XML-RPC Response Parsing Failed” error which is provably new to 2.1. If you updated and are suddenly getting these errors, I have to recommend downgrading to 2.0.5 until I can work out the details and fix it. I have received several reports but I’m still hoping this problem is relatively rare. If you need to downgrade:
If you are experiencing problems with MarsEdit’s new tags feature on 10.4, I believe you’ll find the issue fixed in this beta release of MarsEdit 2.1.1:
Needless to say, this is not exactly a dream scenario for me. I hate to think of customers updating and encountering errors or bugs. But once the cat is out of the bag, I think the only thing I can do is work as hard I can to get the problems fixed quickly.
February 3rd, 2008 at 3:53 pm
Were the reports from wordpress.com users?
If so we have a problem with xmlrpc so Marsedit will not have been at fault.
The problem is resolved there though now.
February 3rd, 2008 at 6:20 pm
I had the problem with the update and I turned off the “Edit in WriteRoom” plugin and the new version now works. Thanks for the great (and fast) detective work, Daniel!
February 3rd, 2008 at 6:35 pm
Mark – thanks for your concern, but it turns out there really was a weird XML parsing bug affecting MarsEdit, just so happened to be on the same day as the WordPress outages :) Glad to hear yours is resolved now.
February 3rd, 2008 at 11:53 pm
Of interest, what was the method called? I think it should be these ‘informal’ plugins that should use a unique naming scheme (like a prefix), not you.
February 3rd, 2008 at 11:56 pm
Qwerty – it was “stringByTrimmingWhitespace” … I agree with you that the burden of uniqueness should fall heavier on the plugins than on the apps. But I have to admit my naming was pretty vulnerable to clashing.
In the end, it’s not worth arguing about who should have chosen a more unique name. I’ll be choosing a more unique name and using it for 2.1.1.