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
Note that WordPress ships with WP_HTTP_IXR_CLIENT that extends the IXR_Client. So replace require_once ABSPATH . WPINC . ‘/class-IXR.php’; $rpc = new IXR_Client( ‘http://localhost/wordpress/wordpress/xmlrpc.php’ ); with: require_once ABSPATH . WPINC . ‘/class-IXR.php’; require_once ABSPATH . WPINC . ‘/class-wp-http-ixr-client.php’; $rpc = new WP_HTTP_IXR_CLIENT( ‘http://localhost/wordpress/wordpress/xmlrpc.php’ ); Then try replacing: $result = $rpc->query( ‘pingback.extensions.getPingbacks’, ‘http://localhost/wordpress/wordpress/2018/01/17/hallo-welt/&post_type=something’ ); with $result = … 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
I was able to greatly reduce the severity of the problem by installing/activating the PHP extension file-info, which was flagged by WordPress as a configuration issue. While it didn’t eliminate the issue completely, the lockup only happened once more during my post migration and the unavailability was much shorter than previous occurrences. Now that the … Read more
I was experiencing a similar problem and nothing was working for me, so I posted my solution here: How to validate XML-RPC post creation and cancel when needed? Maybe you want to check it. I hope it helps!
Azure WordPress deny access to xmlrpc
Can I disable xml-rpc by setting it to false?
the update post function actually calls the insert function so it should work, now I’m not sure but try changing: if(!strlen($photo_url)){ to: if(empty($photo_url)){ since php strlen() returns 0 on an empty string.
I wouldn’t recommend it but… If you are not going to use multisite, then WordPress has a Post via e-mail feature setup under Settings > Writing. See http://codex.wordpress.org/Post_to_your_blog_using_email An alternative might be to get them to use Windows Live Writer, which would give the users a familiar mircrosoft interface. See: http://explore.live.com/windows-live-essentials-help-center?T1=t7