Jump to content

Recommended Posts

@frankl

Thanks Frank, I hid my prior comment before seeing your reply. I appreciate the help.

I cannot seem to get past the this error - see screenshot below.

The thing is that I followed the instructions in the PDF but they did not work for me. So I Googled how to do this and found this set of instructions:

https://auth0.com/docs/connections/social/facebook

I had to register with https://auth0.com

The http://your_site/your_folder/login_with_facebook.php for the callback URI does not work. So, according to autho.com instructions I tried their version of

http://[MY AUTH0 USER NAME].auth0.com/login/callback and that does not work either.

Has anyone run into this issue before and found a solution? No matter what I do, I get the same error when testing the login authentication.

error-message.png.5fbb4da69ec2631c4a964454db55f224.png

fb-app-settings-1.thumb.png.89a4a18333aeb01c2b49c7a45e35df13.png


osCommerce: made for programmers, ...because store owners do not want to be programmers.

https://trends.google.com/trends/explore?date=all&geo=US&q=oscommerce

Share this post


Link to post
Share on other sites

These are the settings I have.

image.png.04431b02cf03f61da7bf30c58557b37f.png

which works fine.

My OAuth Redirect URI is https, not sure if that's relevant.

Alternatively, are you trying to collect any of the following:

  • user_link
  • user_gender
  • user_age_range
  • user_friends
     
    as these are no longer allowed to be accessed without an App review.

Let's make things easier for new osCommerce users http://forums.oscommerce.com/topic/402638-discussion-about-hard-coded-database-tables/?p=1718900  Getting there with osCommerce 2.4! :thumbsup:

Share this post


Link to post
Share on other sites

@frankl

I tried replicating everything you have and unchecked all permissions, but not attributes,.. and I'm still getting the same error.

The https may be the cause of it. or it may be that this is on a subdomain. I tried it with https setting, but my subdomain is not https. And it did not work in changing that callback URI to https.

So, I don't know,.. maybe it's just not meant to be.

 


osCommerce: made for programmers, ...because store owners do not want to be programmers.

https://trends.google.com/trends/explore?date=all&geo=US&q=oscommerce

Share this post


Link to post
Share on other sites

my lowest version for Upgrade All Calls is 2.7 and the other one is now only 3.1

I tried that 2.7, but no improvement, ..still getting the same error. I tested the validity of the redirect URI and that came back good.

I don't know, ..I think I have to put it down and perhaps try it again when I have the site in production (off the sub-domain).


osCommerce: made for programmers, ...because store owners do not want to be programmers.

https://trends.google.com/trends/explore?date=all&geo=US&q=oscommerce

Share this post


Link to post
Share on other sites

Hello,

 

With the imminent Google+API shutdown  will be "Social Login  - Google Login" functionality working anymore ?

Thanks,

 

Robert

 

 

Share this post


Link to post
Share on other sites

I have a smiliar problem same problem here with the OAuth not passing - I tried EVERYTHING - complete new app, changed everything, but no luck at all! It keeps saying the same error:
weadress not included in this apps domain - but it doesn't matter, even I change everything to something "wrong" it gives me the same error :(

I googled and I find that this error is pretty common for a variety of problems and typically linked to OAuth redirect URI... but tried it all :(

Edited by gummipingvin

Share this post


Link to post
Share on other sites

Since Google+ has mostly gone away, should we be thinking about removing it from stores? I never used it, but my understanding is that it's only available for "G Suite", whatever that is. Do the Google+ functions on osC still do anything, or are they just an embarrassment that osC hasn't been updated in ages? If it should go away, I can add that to my Frozen patch set. It will be up to others to fix Edge and the official product.


If you are running the "official" osC 2.3.4 or 2.3.4.1 download, your installation is obsolete! Get (stable) Frozenpatches or (unstable) Edge. See also the naming convention and the latest community-supported responsive "Edge" release

Share this post


Link to post
Share on other sites

"While we’re sunsetting Google+ for consumers, we’re investing in Google+ for enterprise organizations. They can expect a new look and new features -- more information is available in our blog post. "

Still alive and kicking for B2B


 

Share this post


Link to post
Share on other sites

Are the interface and logo unchanged, or is osC's implementation going to have to be completely redone, anyway? It sounds like the latter to me, but I guess it hasn't settled down yet.


If you are running the "official" osC 2.3.4 or 2.3.4.1 download, your installation is obsolete! Get (stable) Frozenpatches or (unstable) Edge. See also the naming convention and the latest community-supported responsive "Edge" release

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×