One of the big problems we faced with Photon was platform support: simply stated, there are too few that support the MetaWeblog API wholly enough for us to use. Sure it might look a little sappy to support Six Apart products exclusively, but when you’re trying to call
metaWeblog.newMediaObject and you’re getting precisely dick from the competition it doesn’t leave you with too many options. The downer goes double when one of the platforms you just can’t support is also the second most popular platform of the day (according to Adriaan’s latest poll, at least), whose popularity has skyrocketed in the wake of the Movable Type 3.0 licensing scandal.
Yes, for WordPress —as Colin pointed out— it’s a 1.3 waiting game. The appropriate fixes to WP’s XML–RPC server will be released with WordPress 1.3, and Photon 1.1 should follow soon after with a few new features for everyone to play with, too. But in the mean time, if you’re fond of a little hackery, Johann Richard has released a patch for WP1.2’s
xmlrpc.php file that fixes a whole assload of things… some of which meaning that Photon can do the nasty with WordPress.
Like most things that are any fun, the patch is officially unsupported by both WordPress and Daikini… but if you’re an “open ‘er up and fiddle with ‘er guts” kinda guy it might just be the thing for you. There are a few caveats that come with this process, of course:
- You need to tell Photon that it’s dealing with Movable Type, since WordPress isn’t available in Photon’s “Platform” menu just yet.
- You can’t create new categories, nor should you try.
- Export will fail if there’s a full moon out, or if you’ve eaten Caramel Fudge lately.
- There is no fourth caveat… yet.
I’d be very interested to hear how things turn out for people who try it this way, but remember: the words to keep in the back of your mind are “at your own risk”.