A4A Client: defer connection check to plugins_loaded hook #46062
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.
Fixes #
Proposed changes:
Problem
The A4A Client plugin experiences fatal errors on Atomic sites because
$manager->is_connected()runs too early ininit(), before WordPress core functions likeget_user_by()are available. This was introduced in PR #37337.Solution
Move the connection check from
init()to theplugins_loadedhook (priority 20) so:Other information:
Jetpack product discussion
Does this pull request change what data or activity we track or use?
Testing instructions:
/wp-admin/admin.php?page=jetpack-beta&plugin=automattic-for-agencies-client)