Connection: Move remote file upload handlers back to Jetpack class #13253
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In #12699 we didn't port the remote media upload functionality to the connection package, but we moved a call to the responsible method in the connection manager 😱 You can see that there's a reference to
$this->add_remote_request_handlersin the connection manager, but that method doesn't exist 😕This PR puts the remote media upload initialization back to the Jetpack class where it belongs, as the method we're using still lives there. This is similar to what #13235 did for the JSON API auth.
Kudos to @brbrr for reporting that.
Changes proposed in this Pull Request:
Is this a new feature or does it add/remove features to an existing part of Jetpack?
Testing instructions:
Proposed changelog entry for your changes: