I also will get redirected to the post-login page (without going to Facebook) –
http://lifegroups.newlifechurch.local/?loginFacebook=1&redirect=http://lifegroups.newlifechurch.local/leadership
Could it be that I’m trying to use App Test Users?
Hi!
Thanks for reporting this problem. So you wrote two independent error as I see. Am I right?
Your first problem is that the user with Facebook account unable to register.
And the second that you have a registered user through Facebook, who de-auth the app. Then he’s trying to login again and the system log him in as admin.
Actually, I think I found the major problem with at hand ::
Facebook’s Developer Backend lets you create test users for applications. These are non-public users that still have full Facebook functionality (profile images, they can ‘like’ things, authorize apps, etc).
The users I was trying to authorize using your plugin were the test users created by Facebook.
Is there a way to allow these test users to work with Nextend Facebook Connect?
I tested it in the last 10 minutes.
I followed this steps:
- Created a test user for the app
- Logged in with the test user on my site
- The application asked for authorization, I allowed it.
- The registration were successful, I were logged in
- I logged out from the site
- In Facebook I removed the app from the allowed applications
- Then I tried to log back
- I have to authorize the app again
- Then I were logged in wothout problems
What am I doing different than you?
The problem I was having – is that I was getting errors when trying to authorize the app after being redirected from my site (with the Nextend link).
If I wasn’t getting errors – I was getting redirected incorrectly –
EX: http://lifegroups.newlifechurch.local/?loginFacebook=1&redirect=http://lifegroups.newlifechurch.local/leadership
instead of being redirected to Facebook or Logged in.
Just a heads up – latest update broke FB Connect Functionality.
Just a heads up – latest update broke FB Connect Functionality.
## update –
Facebook was getting blocked.
Please contact me by email and we will find the solution faster π
roland[@@@]nexendweb[.]com
We were able to fix this in the latest patch π