New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Step-by-step credentials: full verification screen #48106
Conversation
84a087c
to
de46d6e
Compare
@@ -252,7 +253,7 @@ const AdvancedCredentials: FunctionComponent< Props > = ( { action, host, role } | |||
const renderConnectedButtons = () => ( | |||
<> | |||
<Button scary disabled={ disableForm } onClick={ handleDeleteCredentials }> | |||
{ translate( 'Delete Credentials' ) } | |||
{ translate( 'Delete credentials' ) } |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🆗 This change will be queued for retranslation. We'll use the existing translations in the meantime.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This works fantastic. I love how much better is this new UX.
Thanks for working on this!
Here is how your PR affects size of JS and CSS bundles shipped to the user's browser: Sections (~840 bytes added 📈 [gzipped])
Sections contain code specific for a given set of routes. Is downloaded and parsed only when a particular route is navigated to. Async-loaded Components (~998 bytes added 📈 [gzipped])
React components that are loaded lazily, when a certain part of UI is displayed for the first time. Legend What is parsed and gzip size?Parsed Size: Uncompressed size of the JS and CSS files. This much code needs to be parsed and stored in memory. Generated by performance advisor bot at iscalypsofastyet.com. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Tested and works great! Tested with correct server info and also with combination of incorrect creds and server info. Progress indicators all looked correct and all error messages looked correct. LGTM! 👍
This Pull Request is now available for translation here: https://translate.wordpress.com/deliverables/5401533 Thank you @delan for including a screenshot in the description! This is really helpful for our translators. |
Translation for this Pull Request has now been finished. |
Changes proposed
This patch builds on #47614 + #47898 by replacing the success and failure notices with the full i4 verification screen (Finish up on success, Review credentials and more details on failure). These changes affect the “advanced credentials” flow, which is currently green only, so blue should be unaffected.
Testing instructions
Please set up your environment as described in #47614 before testing.
Open green and choose a Rewind-enabled site, then click Settings.
Verify that you can save working credentials successfully, with progress displayed similarly to the screen recording below.
Now try to save the same credentials, first with an incorrect password or private key, and then with the port number changed to 99999. Verify that progress is displayed similarly to the screen recording below, followed by the usual localised error message (first) or an appropriate error message under More details (second).
Screen recording (click to play)
This recording also illustrates a bug where Calypso would submit both a password and a private key if they were ever provided, which should be fixed in a subsequent patch.