Help Center: Persist the Help Center open state and clean up Odie endpoints #41126
Conversation
github-actions
bot
added
[mu wpcom Feature] Help Center
[Package] Jetpack mu wpcom
|
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 🤖 The e2e test report can be found here. Please note that it can take a few minutes after the e2e tests checks are complete for the report to be available. Follow this PR Review Process:
Still unsure? Reach out in #jetpack-developers for guidance! |
github-actions
bot
added
the
[Status] Needs Author Reply
|
Are you an Automattician? Please test your changes on all WordPress.com environments to help mitigate accidental explosions.
Interested in more tips and information?
|
| /** | ||
| * Get chat_id and last_chat_id from user preferences. | ||
| */ | ||
| public function get_last_chat_id() { | ||
| // Forward the request body to the support chat endpoint. | ||
| $body = Client::wpcom_json_api_request_as_user( | ||
| '/me/preferences', | ||
| '2', | ||
| array( 'method' => 'GET' ) | ||
| ); | ||
|
|
||
| if ( is_wp_error( $body ) ) { | ||
| return $body; | ||
| } | ||
|
|
||
| $response = json_decode( wp_remote_retrieve_body( $body ) ); | ||
|
|
||
| $projected_response = array( | ||
| 'odie_chat_id' => $response->odie_chat_id, | ||
| 'odie_last_chat_id' => $response->odie_last_chat_id ?? null, | ||
| ); | ||
|
|
||
| return rest_ensure_response( $projected_response ); | ||
| } | ||
|
|
||
| /** | ||
| * Set chat_id or last_chat_id from user preferences. | ||
| * | ||
| * @param \WP_REST_Request $request The request sent to the API. | ||
| */ | ||
| public function set_last_chat_id( \WP_REST_Request $request ) { | ||
| $chat_id = $request['odie_chat_id']; | ||
| $last_chat_id = $request['odie_last_chat_id']; | ||
|
|
||
| $data = array( | ||
| 'calypso_preferences' => array(), | ||
| ); | ||
|
|
||
| if ( $request->has_param( 'odie_chat_id' ) ) { | ||
| $data['calypso_preferences']['odie_chat_id'] = $chat_id; | ||
| } | ||
|
|
||
| if ( $request->has_param( 'odie_last_chat_id' ) ) { | ||
| $data['calypso_preferences']['odie_last_chat_id'] = $last_chat_id; | ||
| } | ||
|
|
||
| $body = Client::wpcom_json_api_request_as_user( | ||
| '/me/preferences', | ||
| '2', | ||
| array( 'method' => 'POST' ), | ||
| $data | ||
| ); | ||
|
|
||
| if ( is_wp_error( $body ) ) { | ||
| return $body; | ||
| } | ||
|
|
||
| $response = json_decode( wp_remote_retrieve_body( $body ) ); | ||
|
|
||
| $projected_response = array( | ||
| 'calypso_preferences' => array( | ||
| 'odie_chat_id' => $response->calypso_preferences->odie_chat_id, | ||
| 'odie_last_chat_id' => $response->calypso_preferences->odie_last_chat_id, | ||
| ), | ||
| ); | ||
|
|
||
| return rest_ensure_response( $projected_response ); | ||
| } | ||
|
|
There was a problem hiding this comment.
These aren't used anymore.
| public function get_state() { | ||
| // Forward the request body to the support chat endpoint. | ||
| $body = Client::wpcom_json_api_request_as_user( | ||
| '/me/preferences', | ||
| '2', | ||
| array( 'method' => 'GET' ) | ||
| ); | ||
|
|
||
| if ( is_wp_error( $body ) ) { | ||
| return $body; | ||
| } | ||
|
|
||
| $response = json_decode( wp_remote_retrieve_body( $body ) ); | ||
|
|
||
| $projected_response = array( | ||
| 'help_center_open' => (bool) $response->help_center_open, | ||
| ); | ||
|
|
||
| return rest_ensure_response( $projected_response ); | ||
| } |
There was a problem hiding this comment.
@sandymcfadden Hi! This is how you proxy a WPCOM endpoint and make it accessible to Atomic sites. Atomic sites can access this via
/wp-json/help-center/open-state
Fixes Automattic/wp-calypso#97919
Requires but can be merged before: Automattic/wp-calypso#98484
Proposed changes:
Other information:
Jetpack product discussion
Does this pull request change what data or activity we track or use?
No.
Testing instructions: