Don't kill the translator. Toru Marumoto

MT4.1 beta2 and AtomPub support

I've been waiting for a long time for this. First of all, congrats to the developers at SixApart. Now MT 4.1 supports AtomPub.

Unfortunately, I can't see MT4.1 beta2 in action due to some mysterious errors during its installation. I'm very interested in how they implemented AtomPub in MT because, so far, WordPress's AtomPub support is practically unusable. Aside from a few bugs, WordPress's AtomPub support offers very little features compared to those of XML-RPC API. There is no reason to choose AtomPub over XML-RPC API at this point.

Yes, it is a good thing we have a choice. But I don't think current status of AtomPub support in WordPress reflects true potential of AtomPub. Also, now that MT has the custom fields, MT could take advantage of the extensibility of Atom. The same thing can be said with Vox. Vox support only one API which is an old (pre draft version of) Atom API. That is a shame because there are not only blog posts but also "photos", "audio", "video", "books", "collections" that can be used via web service interface. The old version of Atom API can't handle all that great, but AtomPub can.

So, developer teams at WP and Movable Type, keep up the great work and I'm hoping the two tools will be much much better.

By the way, what I got during the installation was bellow (which I already reported to the dev team).

Got an error: Can't call method "execute" on an undefined value at /somedirectory/mt4/extlib/Data/ObjectDriver/Driver/DBI.pm line 118.

(I heard this was a bug in MT4.1 beta2 and will be fixed)

and

Got an error: Statement has no result columns to bind (perhaps you need to successfully call execute first) at /somedirectory/mt/extlib/Data/ObjectDriver/Driver/DBI.pm
line 119.

 (Seems like MySQL version is old...)