-
Notifications
You must be signed in to change notification settings - Fork 797
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
Enables Jetpack without the need of an authorized user #19637
Conversation
Thank you for your PR! When contributing to Jetpack, we have a few suggestions that can help us test and review your patch:
This comment will be updated as you work on your PR and make changes. If you think that some of those checks are not needed for your PR, please explain why you think so. Thanks for cooperation 🤖 Once your PR is ready for review, check one last time that all required checks (other than "Required review") appearing at the bottom of this PR are passing or skipped. Jetpack plugin:
|
I still need to update the tests |
* @param bool $is_connection_ready Is the connection ready? | ||
* @param Automattic\Jetpack\Connection\Manager $connection_manager Instance of the Manager class, can be used to check the connection status. | ||
*/ | ||
return apply_filters( 'jetpack_is_connection_ready', self::connection()->is_connected(), self::connection() ); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice, thanks for adding this filter here!
Do you think we should handle Atomic here explicitly or depend on the filter? I'm leaning towards the second.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I agree we should let them filter this if needed via wpcomsh
Co-authored-by: Foteini Giannaropoulou <giannaropoulou.foteini@gmail.com>
Caution: This PR has changes that must be merged to WordPress.com |
Did a good bit of testing on this one and everything seemed to work fine! Also tried making a purchase, disconnecting, then reconnecting at site level and Search continued to work. Since I'm not entirely familiar with the code, it'd be great if some other folks took a look as well before merging! |
Great news! One last step: head over to your WordPress.com diff, D60623-code, and commit it. Thank you! |
r224792-wpcom |
This PR makes Jetpack active as soon as there is a site level connection, not requiring a user connection in order to work. (aka what we have been calling User-Less).
Changes proposed in this Pull Request:
userless
GET-parameter to WP.comJetpack product discussion
p1HpG7-aJm-p2
Does this pull request change what data or activity we track or use?
No
Testing instructions:
Test the connection flow in every possible way:
define( 'JETPACK_SHOULD_NOT_USE_CONNECTION_IFRAME', true );
Also