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
Social Auth: Update TOS message to remove mention of creating an account on social login #67057
Conversation
Here is how your PR affects size of JS and CSS bundles shipped to the user's browser: App Entrypoints (~167 bytes removed 📉 [gzipped])
Common code that is always downloaded and parsed every time the app is loaded, no matter which route is used. Sections (~222 bytes removed 📉 [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 (~231 bytes removed 📉 [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. |
Working with a representative in p2y3YZ-5Oq-p2#comment-13724. |
cacefb6
to
ce0d7ff
Compare
ce0d7ff
to
e5a5250
Compare
e5a5250
to
daf4c27
Compare
client/blocks/login/social.jsx
Outdated
renderSocialTos = () => { | ||
const { redirectTo, translate } = this.props; | ||
|
||
const isJetpackMagicLinkSignUpFlow = | ||
redirectTo && | ||
redirectTo.includes( 'jetpack/connect' ) && | ||
config.isEnabled( 'jetpack/magic-link-signup' ); | ||
|
||
const tosLink = ( | ||
<a | ||
href={ localizeUrl( 'https://wordpress.com/tos/' ) } | ||
target="_blank" | ||
rel="noopener noreferrer" | ||
/> | ||
); | ||
const privacyLink = ( | ||
<a | ||
href={ localizeUrl( 'https://automattic.com/privacy/' ) } | ||
target="_blank" | ||
rel="noopener noreferrer" | ||
/> | ||
); | ||
|
||
if ( isJetpackMagicLinkSignUpFlow ) { | ||
return ( | ||
<> | ||
<p className="login__social-tos"> | ||
{ translate( | ||
'By continuing, you agree to our {{tosLink}}Terms of' + | ||
' Service{{/tosLink}} and acknowledge that you have read our' + | ||
' {{privacyLink}}Privacy Policy{{/privacyLink}}.', | ||
{ | ||
components: { | ||
tosLink, | ||
privacyLink, | ||
}, | ||
} | ||
) } | ||
</p> | ||
<p className="login__social-tos"> | ||
{ translate( | ||
'If you continue with Google, Apple, or an email that isn’t registered yet,' + | ||
' you are creating a new WordPress.com account.' | ||
) } | ||
</p> | ||
</> | ||
); | ||
} | ||
return ( | ||
<p className="login__social-tos"> | ||
{ translate( | ||
'If you continue with Google or Apple,' + | ||
' you agree to our' + | ||
' {{tosLink}}Terms of Service{{/tosLink}}, and have' + | ||
' read our {{privacyLink}}Privacy Policy{{/privacyLink}}.', | ||
{ | ||
components: { | ||
tosLink, | ||
privacyLink, | ||
}, | ||
} | ||
) } | ||
</p> | ||
); | ||
}; | ||
|
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.
Now that we're showing a single ToS on the login page above the "Continue" button, there's no point in having this in the component as well.
It doesn't affect the sign-up page, which has its own social component called SocialSignupForm
.
Added the |
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.
Works great 👍
Nice work tracking down all of the login variations!
This Pull Request is now available for translation here: https://translate.wordpress.com/deliverables/7507490 Thank you @zaguiini for including a screenshot in the description! This is really helpful for our translators. |
Nice work with the changes @zaguiini. I found one more login case You get to it from woocommerace.com. Which looks correct. from woocommerce-onboarding to be quite broken but I am not sure how it is used. |
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.
Nice work!
Thanks, @enejb! Asked this in the Woo channel on Slack: p1662149049437139-slack-C07418EA0 |
Translation for this Pull Request has now been finished. |
Proposed Changes
On the login page, we warn the user that we're creating them an account if it doesn't exist when they try to socially sign in:
But that's not true: we don't try to, and warn them that they should sign up instead (notice on top). This is misleading, so we need to update the TOS. Also, a legal representative asked to differentiate the link color from the text: p2y3YZ-5Oq-p2#comment-13737.
Testing Instructions
Check that the login and sign-up pages do not suggest that we're creating a new account in case social login fails. It also puts the ToS copy at the beginning and covers all three authentication methods.
Don't forget to run Calypso locally. Copy the link and open it in incognito mode.
/log-in
/log-in/new
/log-in/jetpack
/log-in?from=woocommerce-onboarding
/log-in?from=p2
/start/user