Topic-icon Final Tweaks

Active Subscriptions:

None
8 years 9 months ago #54208 by WhatNoWebsite
Replied by WhatNoWebsite on topic Final Tweaks
This is now getting REALLY strange

I just tried updating the scope as I got the following error when using a Tor browser (right hand side) but Waterfox and Chrome still give the error you see on the left:

The topic has been locked.
Support Specialist
8 years 9 months ago #54211 by alzander
Replied by alzander on topic Final Tweaks
For the invalid redirect_uri, we'd need to see how your Google+ app is actually configured. Can you take a picture of your app configuration showing the Redirect URIs you've set?

The scope image is very strange. One of the permissions being requested is "www.googleapis.com/auth/plus.profile.emails.read" That's not a permission that JFBConnect would ever request, so I'm not sure where that's coming from. Do you have any clues as to what may be setting that permission?

Thanks,
Alex
The topic has been locked.
Support Specialist
8 years 9 months ago #54213 by alzander
Replied by alzander on topic Final Tweaks
Actually, I apologize. On further research, the plus.profile.emails.read permission *is* correct. That's necessary to get the user's email address.

I just tried to register on your site and got the redirect_uri mismatch error, but did not get the scope error. Can you tell me when you encounter the scope error message you posted?

Thanks,
Alex
The topic has been locked.
Support Specialist
8 years 9 months ago #54214 by mel
Replied by mel on topic Final Tweaks
I showed Alex the screenshot of the app configuration and it looks correct. The only other thing that we can find (through searching on google) for the invalid_scope is that it might relate to the type of application. Please make sure that you created a web application and not a service application.
The topic has been locked.
Active Subscriptions:

None
8 years 9 months ago #54215 by WhatNoWebsite
Replied by WhatNoWebsite on topic Final Tweaks
Morning Alex


Part of the message is hidden for the guests. Please log in or register to see it.


I wouldn't be too concerned about that second image either as I tested in various browsers and that error ONLY showed up in the Tor Browser so it must be something idiosyncratic of that browser.

The API in use is Google+. Now herin lies the rub: I use the exact same API on a number of sites with another component, "SLOGIN" and it works just fine.

It's a real head scratcher this one. Perhaps I need to add an API...?
The topic has been locked.
Active Subscriptions:

None
8 years 9 months ago #54216 by WhatNoWebsite
Replied by WhatNoWebsite on topic Final Tweaks
Testing on live site now and still get the same error:
The topic has been locked.
Active Subscriptions:

None
8 years 9 months ago #54217 by WhatNoWebsite
Replied by WhatNoWebsite on topic Final Tweaks
Tested and working:

I had to put all the variants of the FQDN.
The topic has been locked.
Active Subscriptions:

None
8 years 9 months ago #54218 by WhatNoWebsite
Replied by WhatNoWebsite on topic Final Tweaks
is this your module/plugin by any chance and if so how can I find it...?

The topic has been locked.
Support Specialist
8 years 9 months ago #54222 by alzander
Replied by alzander on topic Final Tweaks
I'm glad to hear you go the FQDN issue resolved. We try to make that clear, but I'll try to see if we can do better in our documentation.

As for your last question about those buttons, yup, those are from JFBConnect. They are the social toolbar which helps to diagnose social sharing issues on your page and to push the current page to any social network's you've configured "Channels" for.

By default, the toolbar will only display to Super Admins when they are logged in. You can also show it to other user groups as well, if you want. To completely disable it, use the "Show Social Toolbar" setting in the JFBConnect -> Configuration area to get rid of it.

Thanks,
Alex
The topic has been locked.