-
Notifications
You must be signed in to change notification settings - Fork 808
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Connection: XMLRPC_Connector can never work #13136
Comments
Related #13084 |
zinigor
pushed a commit
that referenced
this issue
Jul 30, 2019
…Methods (#13139) * Connection: Instantiate the XML-RPC Connector after adding Bootstrap Methods The bootstrap filter clears out all existing XML-RPC methods, so adding the connector methods first does not work. With this new order, the connector's methods are appended to the bootstrap methods. Fixes #13136, #13084. * Adds tests. Refactor required. * Fixed expectations to make tests pass. * Require some XML-RPC methods, allow others, forbid the rest.
mdawaffe
added a commit
to Automattic/jetpack-addons
that referenced
this issue
Jul 30, 2019
Because of the XML-RPC Registration bug in Jetpack 7.5.x, all Jetpack 7.5.x sites register via REST Registration. If a site has a problem with the REST API, the site can't register. This plugin ensures that XML-RPC Registration is available. Automattic/jetpack#13136
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
b52fa91 introduced Connection Connectors.
When the site is not yet active, the XML-RPC Connector is instantiated at
jetpack/class.jetpack.php
Line 624 in 9762312
This adds an XML-RPC method:
jetpack.verifyRegistration
:jetpack/packages/connection/src/XMLRPC_Connector.php
Lines 32 to 45 in 9762312
However, the next line in
class.jetpack.php
clears all existing XML-RPC methods sinceJetpack_XMLRPC_Server::bootstrap_xmlrpc_methods
does not filter its input but instead outputs only its own methods:jetpack/class.jetpack-xmlrpc-server.php
Lines 86 to 94 in 9762312
Thus, when WordPress.com tries to use the
jetpack.verifyRegistration
method, it always fail, and WordPress.com always falls back to the REST Connector.The text was updated successfully, but these errors were encountered: