Core Plugin: XML-RPC

[viktorix]

Move XML-RPC to core plugin (orginal petition).

[ClassyBot]

This issue has been mentioned on ClassicPress Forums. There might be relevant details there:

https://forums.classicpress.net/t/remove-xml-rpc-specification/2798/5

[bahiirwa]

The goal of core plugins is to:

• to increase performance and security for sites that do not require certain features.
• to make breaking changes easier (a default core plugin will maintain the site intact, while a variation of core plugins will allow other features with breaking changes)

@mattyrob has spent some time on this.

PR can leverage

• https://github.com/ClassicPress/ClassicPress/commit/27dc4c077fedc0080abbb0698a58d3e8f2381494
• https://github.com/ClassicPress/ClassicPress/commit/9b110e692deccf757b6a8deb0cbca5fee07ab0fd

[iljester]

What happened to the idea of ​​moving XMLRPC into a main plugin? I personally turned it off and highly recommended doing so. It presents too many risks to keep it activated on your CP installation.

[mattyrob]

@iljester - the idea is still here, but it has not gained traction at this time. It is something that can be considered in the future but for now the core code base is being modernised after the refork.

[mattyrob]

Closing this issue, this can be consider again later but this set of features can be left in core and disabled by a plugin if required:

https://wordpress.org/plugins/disable-xml-rpc-api/