Implement new “site cannot be accessed” flow #3815855

Created on 2020-06-12, translation required by 2020-06-14 (1435 days ago.)

Translations Glossary

Original string	ar	de	es	fr	he	id	it	ja	ko	nl	pt-br	ru	sv	tr	zh-cn	zh-tw
I’d like to fix this now	☑	☑	☑	☑	☑	☑	☑	☑	☑	☑	☑	☑	☑	☑	☑	☑
Your site, {{strong}}%(siteName)s{{/strong}}, cannot be accessed	☑	☑	☑	☑	☑	☑	☑	☑	☑	☑	☑	☑	☑	☑	☑	☑
Jetpack wasn’t able to connect to {{strong}}%(siteSlug)s{{/strong}}.{{br/}}Let’s figure out why — there are a few things to try.	☑	☑	☑	☑	☑	☑	☑	☑	☑	☑	☑	☑	☑	☑	☑	☑
Confirm that your site loads	☑	☑	☑	☑	☑	☑	☑	☑	☑	☑	☑	☑	☑	☑	☑	☑
Visit your site to make sure it loads properly. If there’s an issue, fix your site before worrying about Jetpack! That may resolve this error.	☑	☑	☑	☑	☑	☑	☑	☑	☑	☑	☑	☑	☑	☑	☑	☑
Troubleshoot Jetpack	☑	☑	☑	☑	☑	☑	☑	☑	☑	☑	☑	☑	☑	☑	☑	☑
If you’re no longer using Jetpack and/or WordPress for your site, or you’ve taken your site down, it’s time to disconnect Jetpack.	☑	☑	☑	☑	☑	☑	☑	☑	☑	☑	☑	☑	☑	☑	☑	☑
Note: You may be seeing this error because you don’t have admin permissions for this site.{{br/}}If you think you should, contact your site administrator.	☑	☑	☑	☑	☑	☑	☑	☑	☑	☑	☑	☑	☑	☑	☑	☑
If your site is loading but you’re still seeing this error, this guide will help you troubleshoot the Jetpack connection.	☑	☑	☑	☑	☑	☑	☑	☑	☑	☑	☑	☑	☑	☑	☑	☑

Description

Changes proposed

This pull request implements the new call-to-action and flow for the “site cannot be accessed” indicator on non-Atomic sites (as described in this internal post).

On such sites, the CTA changes to “I’d like to fix this now”, and it points to a new page that replaces the disconnect survey with some options that are more helpful for the situation. The indicator on Atomic sites and the disconnect button on the Manage Connection page remain unchanged.

There are some differences between these changes and the design, as well as some known problems, so I’ve added comments for them below. Let me know if these changes need any automated tests.

Testing instructions

1. Site indicator

Open this branch on calypso.live, click My Sites, then click Switch Site if necessary
If you have any Atomic Jetpack sites with the red exclamation mark, click that icon, verify that the call-to-action reads Remove Site, click that link, then go to step 2.3
If you have any non-Atomic Jetpack sites with the red exclamation mark, click that icon, verify that the call-to-action reads I’d like to fix this now, click that link, then go to step 3.3

2. Old page

Open this branch on calypso.live, click My Sites, then click Switch Site if necessary
Click any Jetpack site, go to Manage > Settings > Manage your connection, then click Disconnect from WordPress.com
Verify that you see the old disconnect survey, then click Skip for now
Verify that you see the Confirm Disconnection page, then click Back
Verify that you see the old disconnect survey

3. New page

Open this branch on calypso.live, click My Sites, then click Switch Site if necessary
Click any Jetpack site, go to Manage > Settings > Manage your connection > Disconnect from WordPress.com, then append ?type=down to the end of your URL
Verify that you see the new page, then click Confirm your site is loading
Verify that the site opens in a new tab or window, close it, then click Troubleshoot Jetpack
Verify that the Fixing Jetpack Connection Issues page opens in the same tab or window, go back, then click Disconnect Jetpack
Verify that you see the Confirm Disconnection page, then click Back
Verify that you see the new page

Screenshots

Unfortunately, no screenshots were provided by the developer.

Show less Show more | Github Pull request