Social Login Common Issues
The Social Login extension uses 1-step and 2-step processes for the first time registrations. When a user clicks on a social network button to register they will be redirected to the social network site to confirm permissions and then returned to your website's previous page URL as Redirect URI of your apps where a social overlay should show which includes the social registration form( for 2-step process ) so users can complete the registration.
1. If you do not see the overlay or fields on it when you are returned to your site and instead just see a white overlay page, please go to your registration form WP-admin > Ultimate Member > Forms > Your registration form and turn ON "Use this form in the overlay" this will show your form in the overlay.
2. If you're getting an SDK/API error or Mismatch Redirect URI errors, please read the common issues and solutions below:
a .Your hosting provider has a `register_globals` that's turned on. Please ask your hosting provider to turn it off. Once the hosting provider has confirmed this is off, please check the issue again.
b. API callback and site URL settings doesn't match the current site domain and its protocol ( http or https ). Also, check if your site URL returns www or non-www that could cause mismatch Redirect URIs set in your Apps.
c. You entered Invalid API credentials in the Ultimate Member social connects settings.
e. There's a caching plugin or varnish/memcache installed on your host. We recommend to exclude those pages where Social Login buttons are added. Also, try clearing the cache/memcache after your install the Social Login extension and pages.
f. Check for broken links or images that causing a 404 page. It duplicates the authentication request that causes 'state' doesn't match.
g. Your theme/plugin has incompatibility issues with Social Login's Sessions. We recommend that you do a theme/plugin conflict test.
3. If users are getting the message "We were unable to request application access permissions." on app authentication, there's a possible cache issue with your site/server. If you have a Varnish Cache or Cache plugin installed on your site/server, please try excluding the following cookie from the cache: PHPSESSID