You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Adding this for visibility and discussion in the open. The Jetpack Connection Task Force kickoff meeting has prompted some discussion about this: p1572023063121300-slack-wcpay
In a future where WCPay is connected to wp.com using the Jetpack connection package, how do we handle the merchant disconnecting said connection?
If WCPay is uninstalled or deactivated, that shouldn't affect the Jetpack connection or other Jetpack-connection-powered plugins, I think we can all agree on that.
If both WCPay and Jetpack are installed, and the merchant explicitly disconnects Jetpack, should the WCPay connection also be severed?
If yes, we should add a filter to this modal so we can present the merchant with more reasons why he shouldn't disconnect.
If no, then that means that disconnecting Jetpack won't affect the rest of the Jetpack-connection-based plugins. So, the site will only be truly disconnected from Jetpack when the last Jetpack-connection-powered plugin is uninstalled/deactivated?
The text was updated successfully, but these errors were encountered:
DanReyLop
added this to the
V0.7 - Settings, On-Boarding / Account Creation milestone
Oct 25, 2019
Adding this for visibility and discussion in the open. The Jetpack Connection Task Force kickoff meeting has prompted some discussion about this: p1572023063121300-slack-wcpay
In a future where WCPay is connected to wp.com using the Jetpack connection package, how do we handle the merchant disconnecting said connection?
The text was updated successfully, but these errors were encountered: