Richard Vencu

<p>This plugin extends the default XML-RPC server API with one new method for specifying author and parent post of remotely uploaded attachment files.</p>
<ol>
<li>preserved backward compatibility with the basic method wp.uploadFile</li>
<li>simple usage, just replace with wp_extended.uploadFile and add 2 OPTIONAL parameters to the data struct: author (string, user_id of author) and parent (string, post_id of parent post)</li>
<li>without the optional parameters the new method is identical in behaviour with the basic method found in WordPress API of XML-RPC</li>
</ol>


XML-RPC Extended Media Upload

This plugin extends the default XML-RPC server API with one new method for specifying author and parent post of remotely uploaded attachment files.

brainvireinfo

<p>You can now disable XML-RPC to avoid Brute force attack for given IPs or can even enable access for some IPs. XML-RPC on WordPress is actually an API that gives developers who build mobile apps, desktop apps and other services, the ability to talk to a WordPress site. The XML-RPC API that WordPress provides gives developers, a way to write applications (for you) that can do many of the things that you can do when logged into WordPress via the web interface.</p>
<h4>Features</h4>
<p>Block XML-RPC by following way.</p>
<ul>
<li>Disable pingback.ping, pingback.extensions.getPingbacks and Unset X-Pingback from HTTP headers, that will block bots to access specified method.</li>
<li>Disable/Block XML-RPC for all users.</li>
</ul>


Manage XML-RPC

Enable/Disable XML-RPC for all or based on IP list, also you can control pingback and Unset X-Pingback from HTTP headers.

XML-RPC Extended Media Upload vs Manage XML-RPC