No one ever told me porting Manila to WordPress was going to be this much fun!
I hit a limit on my method of fetching Manila Gems (Files in later versions of Manila) and posting them proper into a WordPress site at around three megs. The script hit a file of 8 megs and I discovered that Manila would not parse the xml-rpc request for a file that size.
I elected to have the WordPress site try to fetch the gem, and then post it into the WordPress site directly.
My script calls the WordPress site via xml-rpc, and gives it the URL of the gem. Wordpress processes this command and then returns the new URL – which my Manila script will store along side the original url so we might be able to forward traffic to the new address of the gem. This is all via a custom api I have put together specifically to assist the site conversion, in case your wondering how I get WordPress to do these unnatural things.
As simple as all that sounds, it’s less than attractive hack (it does work however) – so I think I’ll call this one a tie and move on.