Problem/Motivation
The logo doesn't follow Google's Sign in Brand Guidelines. According to Google's Sign in Branding Guidelines, the sign in button should not use the dark (blue) or light version of Google 'G' and the Google icon should not be used by itself without text to indicate the user action for Google Sign in.
Proposed resolution
The logo should be updated as per the guidelines. I've created a new icon following the guidelines and provided a patch with the preview of the logo in the form of a png file.
Remaining tasks
N/A
User interface changes
The new icon will replace the wrong icon.
API changes
N/A
Data model changes
N/A
Comment | File | Size | Author |
---|---|---|---|
#13 | login_google_patch_12.png | 59.94 KB | wells |
#12 | social_auth_google-3108975-12.patch | 12.83 KB | Vishalghyv |
#2 | social_auth_google-3108975-2.patch | 12.9 KB | Mokshit06 |
Issue fork social_auth_google-3108975
Show commands
Start within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
Comments
Comment #2
Mokshit06 CreditAttribution: Mokshit06 at Google Code-In commentedComment #3
Mokshit06 CreditAttribution: Mokshit06 at Google Code-In commentedComment #4
Mokshit06 CreditAttribution: Mokshit06 at Google Code-In commentedComment #5
Rajab Natshah CreditAttribution: Rajab Natshah at Vardot commentedComment #6
Rajab Natshah CreditAttribution: Rajab Natshah at Vardot commentedNice Mokshit,
I love to have the option to switch between Light or Dark
Like what I did in #3108790: Update [Vardoc Theme] to use the latest Vartheme BS3 with (Bootstrap 3 LESS) changes and Bootstrap 3.4.1
Login in with new Google login button brand style ( Dark )
Not sure if it would be good to have an option setting, It could be in the Social Auth to use Button style + Light or Dark
Still researching.
Comment #7
Mokshit06 CreditAttribution: Mokshit06 at Google Code-In commentedYes it would be nice to have an option for that as well.
Comment #8
Mokshit06 CreditAttribution: Mokshit06 at Google Code-In commentedWe can also do it by providing two logo files in the img folder of the module named as google_logo_dark and google_logo_light and the user can rename the style of logo he/she wants to google_logo. That logo would be shown in the website.
Comment #9
Mokshit06 CreditAttribution: Mokshit06 at Google Code-In commentedComment #10
dushyant01 CreditAttribution: dushyant01 as a volunteer commentedI'm not sure how the patch is to be applied, and worried about the description of #2 -
Would it work if I just replaced the
google_logo.svg
file at/modules/social_auth_google/img/
and changed permissions to a+rw ?EDIT: Comment #2 earlier displayed some security warning, it has since gone.
Comment #11
wellsComment #12
Vishalghyv CreditAttribution: Vishalghyv at Google Summer of Code commentedThe original patch failed to apply
Comment #13
wellsThanks for the re-roll, @Vishalghyv.
Currently the base configuration of the Social Auth modules lines all available auth methods up with a restricted width. This change (patch in #12) results in a squished image like this:
I think we'll need a new issue in the Social Auth issue queue to address how these login buttons on displayed. They probably should not be so constrained. I'm going to move this issue to postponed for now. Happy if anyone here is willing to get the new issue going over at the Social Auth module. Otherwise I will do so at some point.
Comment #14
wellsComment #15
masipila CreditAttribution: masipila as a volunteer commentedReopening this from Postponed to Active. New users of this module cannot get their Google App through the Google verification process. I just received an email with the following content:
--clips--
[Action Needed]
Hi,
Thanks for your patience while we reviewed your project.
The Google sign-in button on your app’s homepage URL is not compliant with the Google sign-in branding guidelines.
Please update the Google sign-in button on your website according to the Google sign-in branding guidelines. After updating the Google sign in button, please respond directly to this email in order to proceed with the verification process.
--clips--
@wells, you mentioned in #13 that the topic should be addressed in Social Auth issue queue so that other login providers' links would look consistent. I just checked the Social Auth issue queue but couldn't find any open issues for this topic?
Cheers,
Markus
Comment #16
wellsYou're right -- I shouldn't have postponed this issue without a new one in the SA queue. I invite anyone affected by this issue to add one there (and provide an MR to address it, preferably!). This isn't something I've had to address in regular use of the module because in all my use cases we override the templates anyway with custom designs.
Not that I don't think this is an important issue (it certainly is if it's causing verification rejections) just not something I am able to prioritize with the time I have at the moment.
Comment #19
AnybodySame problem here. We had to submit the app for review.
Comment #20
AnybodyThe logo from the MR!4 can be reviewed here: https://git.drupalcode.org/project/social_auth_google/-/blob/589549224dc...
Looking at https://developers.google.com/identity/branding-guidelines?hl=de > Symbol that seems correct to me.
I guess settings might be added in a follow-up, first we should get this valid again?
Comment #21
AnybodyLGTM as reported in #20
@wells do you agree? Then I think we should try to fix and publish this asap?
Can someone create a follow-up feature request for the settings please?
Comment #22
wellsOk yeah this makes sense. Hopefully this is good enough to get folks through review. Will cut a new release now.
Comment #23
AnybodyThank you @wells! :)