·
Those of you paying close attention probably noticed that I neglected to list a couple of the MetaWeblog API calls last week. That’s because they’re duplicated by calls in the “wp” namespace, and I want to keep everything you can call with a “native” WordPress method in one group. Luckily, none of the MovableType API
·
As odd as it may sound, WordPress’ XML-RPC system is built on others. This makes sense from a development standpoint – why reinvent the wheel when others have done such a great job? But it can be incredibly confusing and downright frustrating when you start working with the WordPress API and have to turn to
·
The most important thing to know about WordPress’ XML-RPC interface is how to send and receive data through it. The interface is turned off by default for security purposes, so when you’re ready to start using it, you’ll have to manually turn it on. Go to Settings » Writing and look for the XML-RPC option
·
I’ve seen a lot of conversations over the past two months regarding WordPress’ built-in XML-RPC functionality. What most of you might not know is that you can write to, read, and administer a WordPress site from anywhere. There are iPhone applications for creating and revising content. There are desktop applications for moderating comments. There are
·
Just to forewarn you, this might come across as a more technical post than I normally throw at you. Still, I did something exciting last night that I wanted to share and perhaps educate you about. I built a custom XML-RPC server. And with that statement I know I’ve already lost most of you. Rather