Wp-calypso: Jetpack Connect: No insight into errors during autoconfig process

[chaselivingston]

@keoshi came across this in testing and noted that there's no real indication as to what's going on, the spinners just seem to get stuck in this state with no option to retry, skip, or cancel. Of note, all of the "stuck" items are related to VaultPress specifically.

This happened when purchasing a Professional plan for a poopy.life test site.

cc @rickybanister

[rickybanister]

There was some discussion previously about this issue. I think we are seeing this screen in a transitional state before some api-side work is finished, but perhaps luna folks can comment as to whether we have an unaddressed bug or not.

[tyxla]

I was unable to reproduce that one with a poopy.life purchasing a Professional plan. But let's consider I can force it to happen again for the sake of solving any future similar cases that occur.

I think it could be useful if we display a warning/error notice somewhere if that happens. Can we get a quick draft of where we could drop an error message in this screen @rickybanister? Thanks in advance.

[rickybanister]

What would the error be, what would it say?

In the past I saw us showing a global notice error on the page when something extra strange happened.

Ideally though, we wouldn't show an error, but rather the 'you're almost there' text and a link to chat with support. These 'errors' are most often just anomalies with configuration settings and are surmountable with the right instructions. An 'error' might be kind of overdoing it.

[tyxla]

The 'you're almost there' solution with the chat button sounds good to me. Could you please share a quick mockup of how that would look?

[rickybanister]

@tyxla that should be already implemented.

Here's the original mockup:

Further reading: p6TEKc-1rT-p2

[tyxla]

That's already implemented indeed, and simulating an error brings up that screen properly.

Can anyone help me reproduce the bug, described in this issue? I'm not able to reproduce it when purchasing a Professional plan for a poopy.life site - perhaps I'm missing something?

[keoshi]

@tyxla These are the steps that got me in that view:

• Create site on poopy.life.
• Install Jetpack.
• Connect Jetpack to WordPress.com.
• Purchase the Professional plan.
• Wait for the setup to be finished.
• View hung up in that state you see above.

[tyxla]

That's exactly what I tried @keoshi, but with no luck 😞
Care to record a gif or something? Thanks so much!

[keoshi]

@tyxla Went through the flow again and couldn't replicate.

I did notice paradoxal interstitial states that kept refreshing, confused me about the real status and didn't surface important info long enough:

We can't automatically configure the Akismet and VaultPress plugins

You will have to set up your plan manually.
[Get help setting up]

You are powered up, it's time to see your site.
[Visit your site] [Ask a question]

https://www.youtube.com/watch?v=h4PoqRHI-mU

I can confirm Akismet and VaultPress were both installed and active at the end of the process.

[tyxla]

Thanks @keoshi, we'll be looking into that within @Automattic/luna

[oskosk]

I think the issue reported here in the description by @chaselivingston is already solved. Although the last comment by @keoshi does reflect something currently happenning and indeed needs to be addressed.

[stale[bot]]

This issue has been marked as stale and will be closed in seven days. This happened because:

• It has been inactive in the past 9 months.
• It isn't a project or a milestone, and hasn’t been labeled `[Pri] Blocker`, `[Pri] High`, `[Status] Keep Open`, or `OSS Citizen`.

You can keep the issue open by adding a comment. If you do, please provide additional context and explain why you’d like it to remain open. You can also close the issue yourself — if you do, please add a brief explanation.

[tyxla]

This is still an issue, but will be ready to be closed as soon as we the checklist for Jetpack sites is ready and open to public.

[stale[bot]]

This issue has been marked as stale and will be closed in seven days. This happened because:

• It has been inactive in the past 9 months.
• It isn't a project or a milestone, and hasn’t been labeled `[Pri] Blocker`, `[Pri] High`, `[Status] Keep Open`, or `OSS Citizen`.

You can keep the issue open by adding a comment. If you do, please provide additional context and explain why you’d like it to remain open. You can also close the issue yourself — if you do, please add a brief explanation.

[tyxla]

Let's keep that open, it might be useful now that we're planning to roll out a new way to autoconfig the plugins.

[keoshi]

We're not showing this anymore, closing the issue.