Re: [web2py] Re: OAuth2.0 and Facebook (as from the book)

2013-10-29 Thread Christian Foster Howes
Lisandro, the ratio of users without email is so low that i would just block the user telling them that they must grant email permissions to use your site. detect that there was no email returned from facebook and send a response to the browser that prompts the user to try again and add the

Re: [web2py] Re: OAuth2.0 and Facebook (as from the book)

2013-10-29 Thread Lisandro Rostagno
Thanks, you're right, Facebook documentation is very poor and is often outdated. That page says that anyone can send you an email from external mail services (gmail, yahoo, etc).. but I tried that and I receive a response from Facebook saying that there is a permission problem... I suppose that th

Re: [web2py] Re: OAuth2.0 and Facebook (as from the book)

2013-10-29 Thread Michele Comitini
this is what they say: https://www.facebook.com/help/224049364288051 facebook documentation for developers is incomplete, so to say, on many occasions... mic 2013/10/29 Lisandro Rostagno > Thanks for the answer. The problem is that I really need a valid email > address, because in my site

Re: [web2py] Re: OAuth2.0 and Facebook (as from the book)

2013-10-29 Thread Lisandro Rostagno
Thanks for the answer. The problem is that I really need a valid email address, because in my site I use that email to send important notifications to the user. I already tried with "facebook mail", that is, joining the user name with "@ facebook.com". But it didn't work. When I send an email to a

Re: [web2py] Re: OAuth2.0 and Facebook (as from the book)

2013-10-29 Thread Michele Comitini
create a fake email... something like the following (check for errors I did not test it) if user: if not user.has_key('email') or user['email'] == '' or user['email'] is None: user['email'] = user['first_name'] + '.' + user['last_name'] + '.' + user['id'] + '@facebook.email.is.not.valid'

Re: [web2py] Re: OAuth2.0 and Facebook (as from the book)

2011-06-06 Thread Sebastian E. Ovide
I do not see major pros and cons... it is a matter of precerences... 1) setting username=True in auth.define_tables(), define_tables will add a field on the table (username) and if that field is present, authentication will be done using username. Personally I prefer to use emails rather than user