Such an amazong epsiode. I was reading on this full text searching for PostgreSQL before, but I didn't understand quite a lot of things, and this really cleared things up. Thank you so much :)
Thanks to Andrew Dixon, we know that in development Website > Site URL must be http://127.0.0.1:3000 instead of http://localhost:3000. Unfortunately, Facebook seems to ignore this information, so it will still send the callback using the domain from which you activated the '/auth/facebook' route. This will produce an error if your URL is http://localhost:3000, so just use the http://127.0.0.1:3000 instead when developing.
After the user typed his information, and when you're handling the callback you just check if the authentication the user typed in exists in your database. If it doesn't, then it's a register. Is this what you meant?
The ending with Capybara is like a cherry on top. Such an awesome episode :)
Such an amazong epsiode. I was reading on this full text searching for PostgreSQL before, but I didn't understand quite a lot of things, and this really cleared things up. Thank you so much :)
Nevermind, it automatically works if you use nested
fields_for
, like this (in Haml):Does anyone know how to use this custom form builder with
fields_for
? I've tried passing the:builder
option, but it doesn't work.Edit: For Facebook you will also need to give them your mobile phone number (they will offer you a link).
Just wanted to share with you some problems I had and how solved them when setting Twitter, Facebook and Google.
Twitter:
Facebook
Google
After the user typed his information, and when you're handling the callback you just check if the authentication the user typed in exists in your database. If it doesn't, then it's a register. Is this what you meant?
Take a look at the beginning of episode #304, Ryan explains which things have changed in Omniauth. Maybe it will help.