REST API: Fix user connection data without owner #18363
Merged
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.
This PR fixes a PHP notice when trying to fetch user connection data while a connection owner does not exist (user-less).
Changes proposed in this Pull Request:
get_user_connection_data
method inJetpack_Core_Json_Api_Endpoints
to properly handle cases where the connection owner does not exist.Jetpack product discussion
Does this pull request change what data or activity we track or use?
No
Testing instructions:
Manual
Before applying this fix:
JETPACK_NO_USER_TEST_MODE
( inwp-config.php
or via Settings -> Jetpack Constants)jetpack/v4/connection/data
:The notice will be visible either in
debug.log
or in your browser console, Network tab -> XHR ->GET wp-json/jetpack/v4/connection/data
:PHP Notice: Trying to get property 'display_name' of non-object in /usr/local/src/jetpack-monorepo/projects/plugins/jetpack/_inc/lib/class.core-rest-api-endpoints.php on line 1598
Automated
Proposed changelog entry for your changes: