xml-rpc

XML-RPC aplication blocked by the hosting

Doh, I forgot to tack on /xmlrpc.php to the url. Should have been obvious because it was spitting back the home page.

OK, doesn’t look like there is a way to do this. I see now there is an orderby and offset property which can be used by the client to make repeated calls to get all the posts.

It looks like custom taxonomies aren’t supported by metaWeblog.newPost. For self-hosted WordPress installs, one could try to use this hook, to adjust the tagging of posts added with metaWeblog.newPost: /** * Fires after a new post has been successfully created via the XML-RPC MovableType API. * * @since 3.4.0 * * @param int $post_ID ID … Read more

I figured out the issue. Actually it is my mistake. I am using XML-RPC metaWeblog.newPost but I was applying solution which is for XML-RPC wp.newPost So correct solution in case of xml-rpc metaWeblog.newPost is – $content[‘categories’] = array(‘Featured’); //Works. And in case of xml-rpc wp.newPost, it is – $content[‘terms’] = array(‘category’ => array( 10 ) … Read more

“XML-RPC server accepts POST requests only” error message

the filter xmlrpc_default_post_fields can modify the defult fields sent in rpc, but the defults array( ‘post’, ‘terms’, ‘custom_fields’ ) alredy include custom_fields you also have the filter xmlrpc_prepare_post, where you can add extra stuff to the rpc:s post

yes it is a security risk. Should it be disabled? most likely. Is it a OMG BBQ type of emergency? no. If you have strong passwords for your accounts, it is not more of a security risk than the login form. It is a pointless security risk in the sense that it provides an additional … Read more

I’m pretty sure it’s because there isn’t a method – you’ll have to add your own!