I've got a problem trying to sign in via Twitter. Here is the screenshot of the error report: https://dl.dropboxusercontent.com/u/92424056/screenshot-twitter.png Though, the user was created, I see a new record with email address xxx@dev.null at /backend/rainlab/user/users.

Another problem with FB: by clicking the FB link I'm getting an empty page (https://www.facebook.com/dialog/oauth?client_id=XXXXXXXXXXXXXXX&redirect_uri=http%3A....) Did you ever noticed such behaviour?

Any advice?

Hey Sergey, looking into it now. Give me a few minutes.

Thank you very much, email me at sergey at pozhilov.com if the link to my test site is required.

User registration is fixed - it seems Auth::register() now takes model validation into account which includes a password confirmation field.

In regards to Twitter creating an @dev.null email address, this is by design. Twitter doesn't return an email address like other social providers, so my plugin has no way of knowing which user to attach itself to - so it creates one and attaches to that. The @dev.null are special email addresses that won't have emails sent to them and a few other custom tidbits according to SamuelGeorges - though he may not have implemented that stuff yet.

I can replicate your Facebook issue and am looking into it now. I'll release an update as soon as it's fixed that includes the above changes.

Last updated 10 years ago

thanks!

I'm not sure what's up with Facebook - hopefully it's an issue on their end and they'll fix it soon. If not I'll have to find another solution. But in the meantime I've released version 1.0.4 to the marketplace which fixes the user registration issue. It should be ready as soon as the buildbot finishes doing its thing.

Thanks for the fix for Twitter, the updated code seems to be working correctly, I did get one more exception, but I guess that was a cache issue or something like that. Will give another test to FB tomorrow. P.S. nice to see that user can change his email and still access his account via twitter without an issue :)

Getting back to the FB issue: The fact is, I'm getting 500 error for the oauth request, and googling for "facebook dialog/oauth 500 error" (without quotes of course), got this discussion in the first 10 links: http://stackoverflow.com/questions/15651469/error-500-on-dialog-oauth-api-after-todays-push-at-821 Maybe you'll find it useful.

If you're getting a 500 error could you please tell me what the actual error is? Your apache error or rewrite log should say something.

I'm getting 500 error code from the FB servers, so can't show more than the extended server reply info: http://prntscr.com/4f8our I see nothing special there... There is a chance the application is sandboxed (I can't check that at the moment because fb settings are managed by my client himself), I'll find that out today and let you know... that'll be a good reason to extend a bit the plugin's documentation )

Aha! I figured it out. You need to set the Valid OAuth redirect URIs value in Advanced tab of your Facebook app correctly. Mine was also set incorrectly and as a result I got the same error as you. Once I updated it to the value specified in step 4 of my plugins settings page the plugin started working properly again.

Last updated 10 years ago

That's a good news! ) I'll try that too, once the app's owner add me as a secondary admin on facebook's app page. Will drop you a line here about the result as soon as I got one.

Hi! I've got the same problem with Google login. Login throws me an error "The password confirmation does not match." User is created.

The password confirmation does not match.
/var/www/vendor/october/rain/src/Database/Traits/Validation.php line 156
TYPE
undefined
EXCEPTION
October\Rain\Database\ModelException

error is in line 156 - throw new ModelException($this);
$this->fireModelEvent('validated', false);
if (!$success && $throwOnValidation)
throw new ModelException($this);
return $success;

Last updated 10 years ago

Hey Egi,

I'm fairly sure this is a bug in October but I've worked around it in my plugin. I've released the update and it should be good to go.

Hi Flynsarmy! Register through Google account is working now. Thanks for this quick patch!