HomeBreadcrumb ArrowModulesBreadcrumb ArrowOpenCartBreadcrumb ArrowSocial Media BundleBreadcrumb ArrowGoogle and Twitter login error
New Discussion

Google and Twitter login error

User Image
Clyde member
#1 posted on 29/4/14

Hi guys,

I was informed that google login was giving an error (see below). I updated to the latest files, and the error is still there and now twitter is giving an error too...slightly different to the other guys twitter error.

Google Error:

400. That’s an error.

Error: redirect_uri_mismatch

The redirect URI in the request: http://www.aerosphereclothing.com/store/index.php?route=account/googlelogin did not match a registered redirect URI

scope=https://www.googleapis.com/auth/userinfo.profile https://www.googleapis.com/auth/userinfo.email

response_type=code access_type=offline redirect_uri=http://www.aerosphereclothing.com/store/index.php?route=account/googlelogin approval_prompt=auto client_id=500220533850.apps.googleusercontent.com

Twitter Error:

Notice: Undefined offset: 0 in /webspace/aerosphere.co.za/www/html/store/catalog/controller/module/twitterlogin.php on line 17

Thanks for your assistance.

0
User Image
Alexander Minchev member
#2 posted on 7/5/14

Hi Clyde,

The error that the GoogleLogin returns means that the Google App used for the Google Login is not configured properly. The requested URI from the GoogleLogin Button is http://www.aerosphereclothing.com/store/index.php?route=account/googlelogin while the Authorized redirect URIs configired in the Google App are https://www.googleapis.com/auth/userinfo.profile, https://www.googleapis.com/auth/userinfo.email.

Try adding this as Authorized redirect URIs in your Google App configuration:

http://www.aerosphereclothing.com/store/index.php?route=account/googlelogin https://www.aerosphereclothing.com/store/index.php?route=account/googlelogin

Regarding the error that is caused by the TwitterLogin Button I cannot say for sure what causes it as I have to take a closer look at the problem. Please open a new support ticket at our Support System about this error so that we can further investigate this issue. 

0