search

Automattic / wp-calypso

The JavaScript and API powered WordPress.com
https://developer.wordpress.com
GNU General Public License v2.0
12.43k stars 1.99k forks source link

WPCOM Atomic Jetpack Connections: Provide users an autofixer button when sites are not connected, or autofix for them #67003

Open JoshuaGoode opened 2 years ago

JoshuaGoode commented 2 years ago

What

Related to the following

Why

Reconnecting a broken site Jetpack connection for WPCOM Atomic sites is not easy and typically requires support intervention.

P9HQHe-1ie-p2

When a site is disconnected, a user cannot manage their domain, hosting configuration, or purchases.

WPCOM has the Atomic API and SSH — so we should be able to take some steps to ensure folks have a connection or at least access to domain and hosting configuration features.

Ideally, we’d have a user-facing autofixer button that would ensure they have a proper local user account on the site and establishes a working connection or offer to change their domain if it’s not working.

How

Have a fixer that creates a proper local user account, with required email, and establishes a new connection.

Or, autofix it for users when it is detected. We currently have an autofixer that attempts to heal connections but it often fails due to local user issues.

Or, if domain related, guide the user through fixing/changing domain.

A more complex case would be to guide the user through troubleshooting plugins/themes that may be breaking the connection.

JoshuaGoode commented 2 years ago

cc @jmdodd @hideandgeek404 as this is inline with some of what ya'll have recently discussed as well.

@Automattic/reactor

cuemarie commented 2 years ago

📌 ACTIONS

kriskorn commented 1 year ago

Incorrectly closed this issue instead of https://github.com/Automattic/wp-calypso/issues/57602. Reopened.

jartes commented 2 weeks ago

I was triaging this one, as it was added to TOB, and it could be a great feature request to implement.

@jeherve, I saw that the Kernel team implemented the BRC button to fix JP connections. Can any team take a look at this one? Or, at least, have it under your radar? Many thanks!

This could also be an issue driving support requests. @nerdysandy, can you check on this one when you have a moment? Thank you!

github-actions[bot] commented 2 weeks ago

Support References

This comment is automatically generated. Please do not edit it.

jeherve commented 2 weeks ago

@Automattic/jetpack-vulcan This may be a good connection-related issue to tackle in a future sprint, I think!

fgiannar commented 2 weeks ago

Thanks @jeherve ! Right on time, since @bindlegirl is currently scoping a project for improving the Jetpack Connection health on WoA sites: pf5801-1d5-p2

That said, since this is an old issue, lets make sure that this task is not already covered by the following projects (already implemented):

bindlegirl commented 2 weeks ago

Happy to help with this one as much as possible. Since a lot of these links point to old discussions, I would love to talk to HEs about the current issues and priorities for solving Jetpack connection problems on Atomic. @jartes or @nerdysandy maybe you can help me with this?

jartes commented 2 weeks ago

@bindlegirl Sure! For this, the best HEs to talk with are the ones from the Fusion teams (@Automattic/reactor), who are the ones helping and supporting WoA in Dotcom.

👋🏻 @edequalsawesome @serabi! @bindlegirl is currently shaping a project for Jetpack Connection health on WoA, and I think it would be great to have input from Fusion teams to help @bindlegirl scope this project. Many thanks in advance!

RafaelFunchal commented 1 week ago

Thanks for pinging us, @jartes :)

@bindlegirl will join the Fusion (Reactor + Fission) meeting next week to discuss the project.